Mod - 6 - FGA - CML - VLAB - v1.15 With LV65 PDF

vLAB Pilot – Addendum D
Pilot – Compellent
Document Version 1.15
Date: Sept 2013 Internal Use Only
Author: Mark Miley & Angelo Rivano Dell Confidential

Dell | Global Commercial Sales Training &
Development
Table of Contents
Table of Contents................................................................................................................... 2
Addendum D: Compellent Demonstration Labs.............................................................. 4
5.0 - Introduction and Preparation........................................................................................................................... 4
5.0.0 - Introduction ..................................................................................................................................................... 4
5.0.1 - Demo Environment Diagram ................................................................................................................... 5
5.0.2 - Preparing the Demo Environment......................................................................................................... 6
5.0.3 - Navigation - Set the Scene ........................................................................................................................ 9
5.1 - Demo Session 1 - Compellent ease of use and volume management ........................................ 11
5.1.0 - Introduction.................................................................................................................................................... 11
5.1.1 - Signing into the Compellent Storage Center GUI ..........................................................................14
5.1.2 - Creating a new volume .............................................................................................................................15
5.1.3 - Mapping the volume to a server............................................................................................................ 17
5.1.4 - Viewing the volume in Windows ......................................................................................................... 20
5.1.5 - Creating a new VMware Datastore ..................................................................................................... 24
5.1.6 - Expanding the Datastore........................................................................................................................... 31
5.1.7 - Deleting the Datastore .............................................................................................................................. 32
5.1.8 - Adding a Raw Device Mapping to a Virtual Machine .................................................................. 33
5.1.9 - Deleting the RDM ........................................................................................................................................ 38
5.1.10 - Creating VM Storage Profiles ............................................................................................................... 40
5.1.11 - Deleting VM Storage Profiles ................................................................................................................ 45
Author: Mark Miley Page 2 of 100 Internal Use Only
Dell Confidential
Development
5.2 - Demo Session 2 - Data Protection .............................................................................................................. 46

5.2.0 - Introduction .................................................................................................................................................. 46
5.2.1 - Creating a Manual Replay........................................................................................................................ 48
5.2.2 - Using the Manual Replay to recover from data loss ................................................................... 49
5.2.3 - Deleting the Manual Replay volume .................................................................................................. 53
5.2.4 - Creating a Replication .............................................................................................................................. 54
5.2.5 - Viewing Replications ................................................................................................................................. 57
5.3 - Demo Session 3 - Reporting, Alerting and Managing......................................................................... 58
5.3.0 - Introduction .................................................................................................................................................. 58
5.3.1 - Using Compellent Enterprise Manager for monitoring and alerts ........................................ 60
5.3.2 - Monitoring performance ......................................................................................................................... 63
5.3.3 - Performing real-time analysis ............................................................................................................... 65
5.3.4 - Configuring Alerts and Thresholds ..................................................................................................... 67
5.3.5 - Querying past events ................................................................................................................................ 68
5.3.6 - Using the Chargeback feature............................................................................................................... 69
Dell Confidential
Development
Addendum D: Compellent Demonstration Labs
5.0 - Introduction and Preparation
5.0.0 - Introduction
We have written a document called "Booking a Demo" which will show you how to log
into Demos.Dell.com, book a demo appointment, and launch a demo. The demo that
you need to launch to perform the following labs is called Compellent SC8000.
In this addendum you will find the demos suggested to use during module 6. Each demo
will supply additional information that you will use in conjunction with the basic demo
tasks listed.
The purpose of this document is to provide the Dell Technical Sales force with the tools
they need to deliver an effective live demonstration of the Dell Compellent Storage
Center v6.3 capabilities. These include – but are not limited to – the following elements:
 Storage Center System Manager 6.3 web interface (SCSM)
 Enterprise Manager 6.3 (EM)
 Compellent vCenter Plug-in 1.5.3/2.0
When you start the demo, you will find yourself logged into a Windows 2008 Server
operating system. On the desktop you will find shortcuts to everything needed to
perform the steps in this lab guide.
Dell Confidential
Development
5.0.1 - Demo Environment Diagram
Dell Confidential
Development
5.0.2 - Preparing the Demo Environment
It is in your best interests to ensure the demo environment you will be demonstrating is
clean & tidy before you begin. For this reason we would recommend, where possible,
you log in to your demo at least 15mins prior to delivery and check the following;
 Familiarise yourself with the environment during this time and check if you are
expecting to demo Remote Instant Replay/Live Volume that you have access to the
destination Storage Center.
 Also, make sure all Volumes, Servers, “Replay Profiles”, “Storage Profiles”, and “QoS”
definitions that are not system defined are deleted. The majority of items will have
been deleted automatically by the Demo Center regeneration script but Storage
Profiles, Replay Profiles and replicated volumes are the exception.
 Check there are no SAN attached LUNs or Replays currently presented to the
Windows Host. The correct procedure for un mapping a volume is to first remote the
drive letter, then offline the disk within Windows and finally remove the mapping (or
delete the volume) from the Storage Center GUI and rescan disks via Disk
Management in Windows. You should find a PowerShell script on the desktop that
automates this process.
 NB: If drives are unmapped without ‘off lining’ the disks correctly, you may
experience issues when mapping volumes to the host.
 Ensure you are logged into the Storage Center GUI via a web browser (Internet
Explorer), the Enterprise Manager Client and also the VMware vSphere Client.
 Most importantly, be crystal clear with yourself on what it is you plan to show. A full
demo of ever feature described below (with questions) can take several hours. If you
only have a short time slot be sure to focus on the key points that address the
customer’s pain points and will drive value home to them.
Some additional steps that should be completed prior to commencing a demo;

Where possible run a DPACK as a starting point for discussions!
Understand the customer’s Current infrastructure:

 Operating Systems & Key Applications (Database types etc.)
 Current Storage Platform
 Raw Capacity/Amount of Actual Data & Capacity Growth Rate
 Total IO Performance Available
 Disaster Recovery/Snapshot Capability
 Data Retention Requirements
 Reporting/Management Tools
Dell Confidential
Development
Understand the customer’s desired infrastructure ‘Wins’

 Better Disk Utilization
 Better IO Performance
 Less Management Time
 Simplified capacity expansion on line
 Simplified Disaster Recovery
 More Informative/More Useful Reporting
 Faster Data Recovery to Servers / Less Downtime
 Eliminate System End of Life
 Eliminate Migration to new disk systems
 Reduce Cost of Storage Purchased
 Actively Manage Inactive Data
 Reduce Power/Cooling Requirements
Pre-Demo points to cover

 Review DPACK Results
o Show customer’s workload and Dell’s view on what we would size for.
o Demonstrate understanding of customer’s business as it relates to their workload.
 Fluid Data Architecture (FDA)
o Explain unique values of FDA and its impact on TCO.
o Explain how we would meet the sizing needs based on the capabilities of FDA
o Should include white-boarding of – at the very least – Tiering and Snapshots,
“Day in the Life Of A Page”.
 Co-Pilot/Support
o Explain the value of CoPilot and how Phone Home function works in real-world
scenarios
 Understand the audience
o Ensure that you understand who you are presenting to and how the benefits of
the system will enable them to ‘win’ in their roles
Dell Confidential
Development
In this section you will be completing the following tasks:

 Log into Enterprise Manager
 Log into vCenter Server
 Log into Storage Center
NB: Before starting your demo ensure that you have all GUIs open and ready for use.
Logging into Enterprise Manager
On the desk top double click on the Enterprise Manager Client icon and enter the
following details when prompted:
Username: Admin
Password: password
Note: Host/IP and Web Server port will be pre-populated and should not be changed.
Logging into vCenter Server
Double-click the vSphere client icon. The Client will log you in automatically.
Dell Confidential
Development
Logging into Storage Center
Double-click on the Compellent Storage Center icon and enter the following details
when prompted:
Username: Admin
Password: password
5.0.3 - Navigation - Set the Scene
It can be easy to forget that the customer has no idea what it is they are looking at, so
spend a moment to emphasizing the following;
 Equipment you will be using,
 Set up and current configuration information
 Connectivity methods that you will be using (FC and/or iSCSI).
 Introduce the management interfaces you plan to use (Enterprise Manager, Storage
Center and vCenter Client).
Key Talking Points

 Explain the current system configuration in terms of:
o Front End and Back End IO connectivity
o Disk Tiers (Disk Folders > Assigned) and type of drives in the system.
 It may have been some time since the customer was introduced to the Fluid Data
Architecture so use this overview of the system as an opportunity to refresh the
customer on the most relevant points of the Fluid Data Architecture.
 Web GUI can use any browser that supports JAVA and SSL.
Dell Confidential
Development
 Enterprise Manager provides a single pane of glass to all of your Storage Centers, no
matter how many you have in the environment. Similarly the vCenter Plugin allows
for multiple Storage Centers to be added.
 Although recommended as your single pane of glass, Enterprise Manager is not
required for day-to-day administrative tasks.
Gotchas:
 The methods for managing the system vary considerably between the three different
interfaces so be sure you are familiar with the method you are planning to
demonstrate.
 Storage Center only contains real-time information so use Enterprise Manager to
show all historical data.
Technical Selling Points:

 Ease of use is the key point here with the ability to simply manage the system from
whichever interface they prefer to use as their primary configuration point.
Technical Objective Handling:

Question: Why do I need to use so many different GUIs?
Answer: You can perform the same functions in a number of different ways depending
on your preferences. Most customers will spend all their time in one GUI (or even in
PowerShell) rather than jumping around between several different ones.
Question: Enterprise Manager requires a Windows installation and SQL license?

Answer: The EM data collector does require a Windows system but this does not need
to be a physical box. The clients can be on Windows or Linux systems. Instead of SQL
you can use a flat file, MySQL or SQL Express.
Recommendation: A full, managed SQL install however is recommended for any
enterprise customers.
Dell Confidential
Development
5.1 - Demo Session 1 - Compellent ease of use and volume management
Duration: 30 minutes
In this demo you will be performing the following tasks:

 Create a New Volume
 Map a Volume to Server
 View the Volume in Windows
 Create a New Datastore
 Add a Raw Device Mapping to a VM
 Delete a Raw Mapping Device
 VM Storage Profiles
 Delete VM Storage Profiles
Talking Points
 Make it clear to the customer that there is zero pre-allocation of Volume space when
a new volume is created.
 Show how all operations are simple and wizard-driven but explain that nearly all tasks
can equally be scripted (PowerShell or CompCU) for complete orchestration.
Gotchas
 Although it is true that we do not pre-allocate space on the volume there are always
some pages pre-allocated in the page-pool in order to ensure high performance
when receiving new writes. Be sure to use the correct language when describing the
zero pre-allocation of space.
 Create a volume that is 2TB or smaller. Although Windows supports volumes larger
than 2TB, these disks need to be initiated as GPT disks and this adds another step to
the process. Remember we are trying to demonstrate simplicity and ease of use so
the fewer steps the better.
 Important: Near the end of Demo Session 1 you will be using the Compellent
vSphere plug-in to create a RDM volume. When the time comes to delete the RDM
volume, the option may be “greyed out”. This is a known technical issue with the
Compellent VMware plugin. However, there is a very quick and easy to work around:
simply restart the VMware vSphere Client and you will find the option will no longer
be “greyed out”. Explain to the customer that this is an operation that would rarely be
used on a day-to-day basis. Highlight that it is a “known issue” and will likely be
resolved in the near future.
Dell Confidential
Development
Technical Selling Points

 Thin Provisioning provides the ability to allocate significantly more capacity than the
physical disk available, enabling maximum utilization of storage resources. Dynamic
Capacity only consumes physical capacity when data is written by the application.
This creates smaller, more efficient volume, increasing the performance of volume-
based operations.
 The Compellent vSphere plug-in allows users to manage datastores and Replays
(snapshots) all through the VMware vSphere client, allowing for storage tasks to be
executed from within vSphere. Integrating an organization’s virtualized storage and
server infrastructure management into a single interface allows users to manage
datastores from the storage level up; control storage Replays for data protection,
provide replication and DR assurance; and monitor storage and server statistics for its
entire virtualized environment.
 VASA facilitates compliance of SLAs using VM Storage Profiles that allow the
administrator to set required storage capabilities/characteristics for a VM’s storage.
After the volume is provisioned through Storage Center, Enterprise Manager or the
vSphere Plug-in, VASA polls Enterprise Manager for the volume’s associated VASA
strings. vSphere then compares the strings returned by the Compellent VASA provider
against the VM Storage Profile created by the virtualization administrator to check if
the volume is in compliance. Figure1 below shows a volume as “Compliant” to the
“Gold” VM Storage Profile while Figure 2 shows a volume that is “Noncompliant”.
Figure 3 shows the VASA sting when Storage Profiles are not enabled.
Dell Confidential
Development
Technical Objective Handling

Question: Can’t all vendors create volumes and servers as simply as this?
Answer: Not many can perform the tasks of creating a volume and a server and
mapping them together in such a simple workflow. Additionally if you perform the
volume create in EM then you can also configure replication/Live Volume as part of
the initial volume creation.
Question: What is to stop runaway applications or users consuming storage? Is this not
a concern when over provisioning?
Answer: Whilst this is a valid consideration, various mechanisms are in place to ensure
the system does not fill up to 100% capacity – these include:
 Email and system alerts based on pre-defined thresholds (conservation mode etc.)
 The ability to limit volume space consumption (volume properties)
 Custom Thresholds and alerts defined in Enterprise Manager
 Automatic Phone Home & Copilot notification
 It is also important to point out that although volumes ‘can’ be configured for any
size, this does not always mean volumes ‘should’ be un-necessarily over inflated
when provisioning. Small volumes still provide the same benefits when using
Dynamic Capacity.
Question: If data is deleted from a Windows volume, is the space also freed on the SAN?
Answer: For physical Windows Servers with operating systems prior to Server 2012, a
free space recovery agent is available that periodically runs to ‘free up’ dirty pages on
the associated Compellent Volume.
 For Windows Servers that are virtualised with VMware, an RDM in a physical
compatibility mode is required to use the free space recovery agent.
 For operating systems that natively support UNMAP, no agent is required. Current
OS support includes Windows Server 2012, RHEL6+, VMware ESX5*
*Although UNMAP is supported in VMware, this is for VMFS volumes only. If a

VMDK is deleted from a VMFS volume the space is recovered using UNMAP. If
data from a Windows Volume is deleted from a VMDK the space is not recovered
as VMware currently does not support passing through the UNMAP command –
this will change in a future release of VMware. Storage vMotion or a host based
copy can be used to re-thin a volume if required.
Dell Confidential
Development
5.1.1 - Signing into the Compellent Storage Center GUI
1. Double-click on the Compellent Storage Center shortcut on the desktop.
2. Click Accept on the warning window. Note the Username and Password.
3. Type Admin for User, and password for Password. Click LOGIN.
Dell Confidential
Development
5.1.2 - Creating a new volume
1. Click on the + sign next to Storage to expand the Storage view. Right-click Volumes
and select Create Volume.
2. Click on Redundant in the Create Volume wizard.
3. Click Continue to accept the default volume size of 500 GB.
Note: Dynamic Capacity allows a virtual volume that can be larger than the available
physical disk space
Dell Confidential
Development
4. Click Continue to accept the Recommended Storage Profile (All Tiers).
5. Type Demo Volume 1 for the volume name and click Continue.
Leave all other settings as default.
Note: Volume Folders are option ways for an organization to organize volumes.
For example: Exchange volumes, SQL volumes.
6. Click Create Now to complete the wizard.

Do not close the next screen, as it is needed in the next steps.
Dell Confidential
Development
5.1.3 - Mapping the volume to a server
1. Click Map this Volume to a Server.
2. Select your Windows demo server and click Continue.
Note: You can verify your windows server name by clicking the Start Menu button,
right-clicking Computer, and selecting Properties.
3. Click Advanced on the verification window.
Dell Confidential
Development
4. Click Continue when you have taken note of some of the options available in the
Advanced settings window.
5. Click Create Now to complete the volume mapping wizard.
6. Click the Close button.
7. Click Demo Volume 1 in the Storage Center GUI.
Dell Confidential
Development
8. Click the Mapping tab on the right-hand side to see the connections made between
the volume and the server.
9. Click the Statistics tab. Notice that Demo Volume 1 consumes zero space on the
SAN, regardless of the size of the volume you created.
Note: When demoing be sure to view the volume properties before the disk is
formatted. Disk formatting will cause some data to be written to disk.
Dell Confidential
Development
5.1.4 - Viewing the volume in Windows
1. Double-click on the Rescan shortcut on the desktop.
2. Click the Computer Management icon from the desktop taskbar.
3. Select Disk Management from the left hand tree.
4. Scroll down thought the disks at the bottom, and look for the 500 GB disk we created.
Note: the disk is Unknown, Offline, and the volume is Unallocated.
5. Right-click on the 500 GB Offline disk and select Online.
Note: the disk status changes from Offline to Uninitialized.
Dell Confidential
Development
6. Right-click on the disk again and select Initialize Disk.
Note: the disk status changes from Not Initialized to Online.
7. Right-click on the 500.00 GB Unallocated volume space to the right of the disk and
select New Simple Volume.
8. Walk through the New Simple Volume wizard and accept all of the defaults.
On the Format Partition screen ensure that Perform a quick format is selected.
Type My Demo Volume for the Volume label.
Note: It will take some time for the format to complete if a Quick Format is not
checked but it will make no difference to the space taken on the SAN. For this reason
we always recommend using Quick Format.
9. Click Next and Finish to complete the New Volume Wizard.
10. Right-click the My Demo Volume and select Explore.
Note: this will open Windows Explorer.
Dell Confidential
Development
11. Right-click the new Volume in Windows Explorer, and select Properties.
Note: 105 MB has been used to create and journal the NTFS filesystem.
12. In Compellent Storage Center, click the Statistics tab we looked at earlier.
Click the refresh button at the top of the GUI.
Note: Now that we have written a NTFS filesystem to the volume, the volume is now
consuming a small amount of space.
Dell Confidential
Development
13. In Windows Explorer, browse the other volume that belongs to the lab environment.
In the other volume is a folder called 1GB_Data. You can right-click the folder and
select Properties to verify the size of the data folder.
Right-click the 1GB_Data folder, select Copy.
Click on the new My Demo Volume we created, and Paste the data inside the
volume.
Refresh the volume Statistics again in Storage Center.
Note: Notice that the actual used space on the SAN is twice the size of the Volume
Space used. Since Compellent performs all new writes to RAID10 this is normal and
later modules will detail how to demonstrate the tiering effect of the system.
Dell Confidential
Development
5.1.5 - Creating a new VMware Datastore
1. Double-click the VMware vSphere Client short-cut on the desktop.
2. Right-click on your ESX host.

At the bottom of the menu click Manage Compellent Storage.
Select Add Datastore.
3. Click Next to Create New Compellent Volume.
Dell Confidential
Development
4. Type My Demo Datastore in the Volume Name field.

Click Next.
Note: Although it is possible to select a Volume Folder at this point, it is not possible
to create new Volume Folders from this view. The creation of new Volume Folders
must be performed from the Storage Center or Enterprise Manager GUI.
5. Click Next to accept the Recommended Storage Profile.
Note: Although it is possible to select any Storage Profile at this point – including any
previously created Custom profiles - it is not possible to create new Storage Profiles
from this view. The creation of new Storage Profiles must be performed from the
Storage Center or Enterprise Manager GUI.
Dell Confidential
Development
6. Click Next to accept the Daily Replay profile.
Note: Although it is possible to select any Replay Profile at this point – including any
previously created custom profiles - it is not possible to create new Replay Profiles
from this view. The creation of new Replay Profiles must be performed from the
Storage Center or Enterprise Manager GUI.
7. Click Next to leave the LUN number as default.
Note: The system will only display LUN numbers that are currently available. LUN
numbers already in use will not be displayed.
Dell Confidential
Development
8. Click Next, leaving the default protocol set to Fibre Channel.
9. Click Next to accept the default File System Version as VMFS-5.
10. Click Next, leaving default Datastore name.
Dell Confidential
Development
11. Click Finish to accept all the Datastore Settings listed in the summary.
12. At the bottom of the vSphere Client GUI, you will see a Recent Tasks section.
You can resize this section by selecting the area above Recent Tasks.
Observe the progress of the datastore creation and the rescan of the ESX HBAs.
13. At the top of the vSphere Client GUI, click on Hosts and Clusters and change this to
Datastores.
Dell Confidential
Development
14. Expand the hierarchy in the left-hand pane.

Click on the My Demo Datastore we just created.
15. There are 11 tabs in the right-pane.

Click the right arrow to display the Compellent Storage tab.
Click the Compellent Storage tab.
16. Under View, click on General.
Dell Confidential
Development
17. Under View, click on Usage Statistics.
18. Open Compellent Storage Center. Click Refresh.

Notice how our new Demo Datastore appears.
Click on My Demo Datastore, and select the Statistics tab.
Note: Compare the information seen in vSphere with the information in the Storage
Center GUI. Notice how the information is identical.
Dell Confidential
Development
5.1.6 - Expanding the Datastore
1. Open VMware vCenter.

Right-click on My Demo Datastore and select Manage Compellent Storage then
click Expand Datastore.
2. Click Next to accept the default New Volume Size.
3. Click Finish on the summary.
Dell Confidential
Development
5.1.7 - Deleting the Datastore
1. Right-click on My Demo Datastore, select Manage Compellent Storage, and click

Remove Datastore.
2. Click Next to Permanently the datastore.
Note: In normal operation the recommendation is not to permanently delete

volumes but rather to use the Place in Recycle Bin option. This allows for accidental
deletion of volumes to be rolled back with limited impact.
Dell Confidential
Development
3. Click Finish to complete the wizard.
5.1.8 - Adding a Raw Device Mapping to a Virtual Machine
1. In vSphere Client, at the top, navigate to Home, Inventory, VMs and Templates.
2. Expand the hierarchy in the left-hand pane.

Right-click the lab Virtual Machine (DoNotDelete), select Manage Compellent Storage
and click Add Raw Device.
Dell Confidential
Development
3. Click Next to accept the defaults in the Device Configuration section of the wizard.
4. Click Next leaving the default host selected.
5. Click Next to Create a New Compellent Volume.
6. Type My RDM in the Volume Name field. Click Next.

Dell Confidential
Development
7. Click Next, accepting the Recommended (All Tiers) Storage Profile.
8. Click Next, leaving the default Daily Replay Profile.
9. Click Next to accept the default LUN number.
Dell Confidential
Development
10. Click Next, leaving the Mapping Protocol set to Fibre Channel.
11. Click Next, to select Physical compatibility mode.
Dell Confidential
Development
13. Click to select the DoNotDelete Virtual Machine.

Click on the Compellent View tab on the far right as before.
Click on Usage Statistics in the central View area.
14. In Compellent Storage Center, click Refresh.

Select the new My RDM listed under Volumes.
Click the Statistics tab.
Note: Compare the difference between the space consumed statistics of Demo
Volume with My RDM. Because the RDM does not have any file system data written
to it at this time it will occupy zero space on the SAN until data is written to the drive.
Dell Confidential
Development
5.1.9 - Deleting the RDM
1. Open vSphere Client.

On the top bar, navigate to Home, Inventory, VMs and Templates.
Right-click the DoNoDelete virtual machine, select Manage Compellent Storage and
click on Remove Raw Device.
Note: See step 2 below if the option is greyed-out.
2. If Remove Raw Device is greyed out and not clickable, then restart the vSphere Client
to resolve the issue.
Note: Explain to the customer that this is an operation that would rarely be used on
a day-to-day basis. Highlight that it is a “known issue” and will likely be resolved in
the near future.
Dell Confidential
Development
3. Select the RDM created previously and click Next.
4. Click Next to permanently delete the RDM.
Note: In normal operation the recommendation is not to permanently delete

volumes but rather to use the Place in Recycle Bin option. This allows for accidental
deletion of volumes to be rolled back with limited impact.
Dell Confidential
Development
5.1.10 - Creating VM Storage Profiles
1. In vSphere Client, navigate to Home, VM Storage Profiles.
Dell Confidential
Development
2. Select Create VM Storage Profile.
3. Type Gold Service in the Name field. Click Next.
Dell Confidential
Development
4. Select the following Storage Capabilities:

 High-Performance, Multi-RAID, and Replicated
 Multi-tier, Performance, Replicated
 Multi-tier, High-Performance, Replicated.
Click Next.
5. Review the VM Storage Profile and click Finish.
6. Repeat the same steps for a Storage Profile called Bronze Service.
Dell Confidential
Development
7. Select the following Storage Capabilities: Multi-tier and Multi-tier, High-

Performance. Click Next.
8. Navigate to Home, Inventory, Hosts and Clusters.

Right-click the Compellent host and select New Virtual Machine.
9. Select Typical. Click Next.
Dell Confidential
Development
10. Select the Gold Service VM Storage Profile in the dropdown.
Note: Because of the settings of the VM Storage Profile we created earlier, all the data
stores are listed under Incompatible.
11. Select the Bronze Service VM Storage Profile in the dropdown.
Note: Because of the settings of the VM Storage Profile we created earlier, the My
Demo Datastore is listed under Compatible.
12. Having demonstrated the VM Storage functionality you can now cancel out of the
Create New Virtual Machine wizard.
Dell Confidential
Development
5.1.11 - Deleting VM Storage Profiles
1. Select each of the VM Storage Profiles you created earlier and select Delete VM
Storage Profile.
2. Click Yes to confirm removal.
Dell Confidential
Development
5.2 - Demo Session 2 - Data Protection

 Create a Manual replay
 Delete Files to Simulate Recovery
 Local Recovery
 Delete View Volume
 Create Replication
 Viewing Replications
Talking Points
 Data Instant Replay allows the creation of snapshots (Replays) that consume minimal
storage space and all snapshot overhead is typically on low-cost Tier3 disks.
 Replay Manager allows for consistent snapshots of Windows, SQL, Exchange, Hyper-V
and VM environments.
Gotchas
 Some of the older documentation refers to “Unlimited Snapshots”. Although the
snapshot limit is so high as to be effectively limitless for most customers be aware
that there is actually a soft limit today and the terminology used should be
“practically limitless”.
 Be aware of the worst-case scenario for snapshots: that a tiny change to data (4k)
could take 2MB on the SAN due to the page allocation. However explain to the
customer that for applications that have this kind of write profile a 512K page could
be used and that the snapshot overhead will typically reside on T3 disks.
 Snapshots are crash-consistent unless an application-aware technology is being used
to take them. Explain the benefits of Replay Manager.
 Be sure to point out that SAN-based snapshots are not intended to replace traditional
backups and should not be considered an E2E DR solution on their own. For single-
system/single-site environments a traditional backup is still recommend for true DR
coverage.
Dell Confidential
Development

 Replays are created without an initial clone and contain only written data, rather than
allocated but unused storage typical in other systems.
 Remote Instant Replay replicates continuous Replays between local and remote sites,
offering easy-to-implement disaster recovery at a very affordable price. With Remote
Instant Replay, a practically unlimited amount of Replays can be created and easily
replicated to one or more locations. This granularity enables small recovery intervals,
allowing more recovery points to instantly recover from any point in time. Remote
Instant Replay supports traditional Fibre Channel replication or cost-effective IP-
based replication.

Question: I want to take snapshots of individual VMs using Compellent’s Replay
technology but this only snaps the entire datastore and not in a VM-consistent state.
Answer: This capability is absolutely possible using the integrated Replay Manager 7
function of Compellent.
Question: How do I make sure that the snapshots I’m taking are consistent?
Answer: By using Replay Manager. This allows you to take application-consistent
snapshots of Exchange, SQL, Hyper-V and VMware. For products outside of the scope
of RM7 then you will need to perform some in-host consistency operation before
triggering the Compellent snapshot. Our integration with Oracle’s RMAN is a good
example of this.
Question: So if I’m using Replays I don’t need a backup strategy?

Answer: Dell still recommends a traditional backup method for long-term protection of
data. SAN-based snapshots allow for rapid recovery of data and allow the traditional
backup windows to be potentially reduced but not normally entirely replaced.
Question: Is there really no limit to the number of Replays I can take of a volume?
Answer: Although there is no ‘Hard’ limit on platform, the number of Replays you can
take will be dependent on two factors:
a) The data change rate
b) Available capacity in the system
Data-Instant-Replay stores delta level changes between snapshots, if the rate of
change between Replays is zero; the consumed space from that Replay is also zero.
Question: Is there a performance hit when using Replays?

Answer: For most environments that have a typical R/W profile (70% read / 30% write)
the associated performance hit is minimal. Dell Compellent uses redirect-on-write as
opposed to copy-on-write technology and actually recommends the use of Replays
for all volumes (except log volumes, paging files, etc.) within the system as this helps
to drive additional efficiencies when combined with Data-Progression.
Dell Confidential
Development
5.2.1 - Creating a Manual Replay
1. Open Storage Center GUI, right-click Demo Volume 1, select Replay > Create
Replay.
2. Click Create Now. Leave all settings as default.
3. Click the Replays tab to see the volume’s current Replays including the manual
Replay we just created.
Dell Confidential
Development
5.2.2 - Using the Manual Replay to recover from data loss
1. Open Windows Explorer.

Navigate to My Demo Volume and delete some of the files copied earlier.
2. Open Storage Center.

Right-click the manual Replay and select Create Volume from Replay.
Note: Check the Description field to ensure that it is the manual Replay you
configured
Dell Confidential
Development
3. Click Create Now. Leave all settings as default.
4. Click Continue to map the Replay to the server.
Note: The Windows server should be selected by default.
5. Click OK on the summary to complete the wizard.
6. Double-click the Rescan shortcut located on the Desktop.
Dell Confidential
Development
7. Open Windows Disk Management.

Right click the new 500 GB and select Online.
Note: The recovered disk is already initialized and formatted with a NTFS filesystem.
The server will recognize the volume and will assign the next sequential drive letter
automatically.
8. Right-click the Replay volume we just put Online and select Explore.
Notice that data we deleted previously is able to be accessed on the Replay volume.
9. Copy the data we deleted previously and paste it to the original Demo Volume.
10. Open Storage Center. Click on the Demo Volume 1 View 1 Replay volume.
Dell Confidential
Development
11. Click on the Statistics tab.
Note: The Replay volume has 1 GB of data in it. However, it only consumes 20 MB
on the SAN.
Dell Confidential
Development
5.2.3 - Deleting the Manual Replay volume
1. Right-click the Demo Volume View 1 and select Delete.
2. Click Yes to confirm deletion.
Note: It would be best practices in a production environment to unmap the volume

prior to deleting it but it not necessary for the purposes of this demo.
3. Double-click the Rescan shortcut on the desktop.
Dell Confidential
Development
5.2.4 - Creating a Replication
1. Open Compellent Storage Center and take note of the name of the array you are
logged into. (For example: SC 60695)
2. Double-click the Enterprise Manager Client shortcut on the desktop.
3. Click Log In. User Name is Admin. Password is password.
Dell Confidential
Development
4. Right click on your correct Storage Center name you recorded in step 1.
Select Tasks > Replication > Replicate Volumes.
5. Select a replication destination Storage Center and click Next.
Note: If more than one array is listed, select either one.
6. Select Demo Volume 1 as the volume to replicate. Click Next.
Dell Confidential
Development
7. Click Next to accept the default settings on the Replication Attributes window.
Note: If Replicate Active Replay select, replication will copy all writes from the active
Replay area of the volume. If Deduplication is selected, replication will copy only the
changed portions of the Replay history on the source volume. However, this extra
optimization is resource intensive.
Dell Confidential
Development
5.2.5 - Viewing Replications
1. Click Replications & Live Volume in the bottom left-hand navigation pane.
2. All current Replications are shown. Select the Replication job you have just created
and the current properties and status will be shown in the bottom pane. Details on
the Replays, Progress and IO Reports can be view by selecting the appropriate tab in
this view.
Note: For recently created replications this data will be minimal.
Dell Confidential
Development
5.3 - Demo Session 3 - Reporting, Alerting and Managing
With Enterprise Manager, all local and remote Storage Center systems are discovered
using a single console. This centralized interface provides a complete view of all aspects
of the Storage Center environment, significantly reducing storage administration time.

 How do I see what’s going on in the system?
 Alerts and Thresholds Configuration
 Chargeback
Talking Points
 Enterprise Manager provides the ability to display storage utilization on the Storage
Center system over a period of time, including summaries from last week, last month,
or last year.
 Enterprise Manager is able to monitor all local and remote Storage Center systems,
allowing comparable views of systems in terms of overall system storage,
configuration of storage to servers, and storage resource objects for each resource.
 Enterprise Manager summarizes I/O usage on the Storage Center system over a
period of time, including summaries from last week, last month, or last year.
 Enterprise Manager’s extensive system monitoring provides immediate insight into
Storage Center environments. System reports present storage management
information including summaries for capacity utilization, replications and events,
allowing strategic storage decisions to be made easily.
 Enterprise Manager provides the ability to e-mail storage reports daily, weekly and/or
monthly in any number of standard formats.
 Alerts generated from all local and remote Storage Center systems are forwarded to
Enterprise Manager, helping administrators to identify and resolve problems faster.
Alerts can be exported, sorted, located and cleared.
NB: Note that clearing alerts from Enterprise Manager does not clear them on the
Storage Center system(s).
 Log files from Storage Center systems can be viewed from Enterprise Manager. Log
files can be exported, sorted, located and filtered.
Gotchas
 IO views are updated fairly regularly but the Storage views are not. So be sure to
show information here that is longer term.
Dell Confidential
Development

 Enterprise Manager simplifies capacity planning and increases storage purchase
efficiency.
 Enterprise Manager helps optimize performance by providing important I/O details.

Question: I don’t want to use EM to monitor my system, I want to use my existing
monitoring tools.
Answer: Compellent supports SMI-S, SNMP and scripting to pull system information. We
have integrations with products like SCOM in order for you to monitor the system
from other tools.
Question: I don’t want to set threshold alerts, I want to define QoS for volumes, servers
and departments.
Answer: While QoS is not possible today but by creating the alerts you can quickly
identify any abnormal behavior and rectify it. It is also possible to place some
workloads on to separate disk pools in order to provide a level of separation.
Furthermore ESX 5.1 allows for IOPS thresholding per disk to give you that granular
level of control.
Dell Confidential
Development
5.3.1 - Using Compellent Enterprise Manager for monitoring and alerts
1. Click Monitoring in the bottom left-hand navigation pane.
2. The right hand pane will display the various Alerts.
3. Toggle through each of the tabs at the top.
Dell Confidential
Development
4. Click Storage (SAN/NAS) on the bottom left.
5. Click the Summary tab to show the current Storage status.

Scroll down to look at the various reports.
Dell Confidential
Development
6. At the very bottom is a Top 10 Fastest Growing Volumes report.

Highlight this report as an example of how easy it is to access to vital data.
Dell Confidential
Development
5.3.2 - Monitoring performance
1. Click the IO Usage tab to show an overview of the system’s performance.
2. Use the check boxes at the bottom of the graph to show how the data can be
filtered.
3. Use the explorer view on the left to show the performance details for a different
objects such as: Volumes, Controllers, Ports, Profiles, Disk pools and Disks.
Dell Confidential
Development
4. Click on the View icon at the top of the object hierarchy.
5. Click Comparison View.
6. Select all disks of a type. Click Update.

Demonstrate both the Comparison view and that the load is equally spread across all
disks.
Dell Confidential
Development
5.3.3 - Performing real-time analysis
1. Click on the Charting tab to start recording performance analysis data.

Click the drop down menu at the top to display different time windows.
2. Open Windows Explorer and copy some data on the My Demo Volume so that the
SAN performs some I/O operations.
Dell Confidential
Development
3. Explore the graphs to show that data is immediately displayed in the Charting viewer.
This is a great, free, resource that can be used to perform real-time analysis.
Dell Confidential
Development
5.3.4 - Configuring Alerts and Thresholds
1. Click Threshold Alerts in the bottom left-hand navigation pane.
2. Click the Definitions tab. Click Create Threshold Definition on the top right.
3. Click the Type drop-down menu to demonstrate the different types of Alerts that can
be created: IO Usage, Storage, and Replication.
4. Click the Alert Object Type to demonstrate the granularity of the alerts possible.
5. Create an example alert to show that alerts can be applied across all the Storage
Centers that Enterprise Manager is managing or just a subset.
Dell Confidential
Development
5.3.5 - Querying past events
1. Click the Queries tab and demonstrate that queries can be run instantly or saved for
future use.
2. Define a query as per the below picture.

Definition: Storage, Storage Type Tier, Actual Space and use a 1GB Threshold Value.
Click Run.
Dell Confidential
Development
5.3.6 - Using the Chargeback feature
1. Click Chargeback in the bottom left-hand navigation pane.
2. Click Edit Chargeback Settings.
3. Demonstrate the ease of configuration and flexibility of the function.
Dell Confidential
Development
4. Click the Add Department to show how simple it is to create new Departments and
define pricing structures.
5. Click the Chargeback Runs tab and select the last Manual Run point.
6. Click the Departments tab to show an overview of the systems Chargeback is

currently configured for.
Dell Confidential
Development
7. Click Add Volume and Add Volume Folders on the top right to demonstrate ease of
configuration.
8. Show the “Add Line Item” option to demonstrate that non-array related items can be
added.
Dell Confidential
Development
vLAB Pilot – Addendum E

Pilot – Compellent Live Volume and Hyper-V Cluster
Document Version 1.1

Date: August 2014
Internal Use Only
Author: Franco Manzolini
Dell Confidential
Dell
Dell
Dell Confidential
Development
Table of Contents
Hands-On Hyper-V stretched cluster and Live Volume Lab ....................................... 74
Introduction ..................................................................................................................................................................... 74
Environment Description ................................................................................................... 75
Introduction ..................................................................................................................................................................... 75
Cluster Shared Volumes (CSV) and VMs creation ......................................................... 78
Preliminary testing ........................................................................................................................................................ 84
Disaster Recovery Test and Failover Procedures........................................................... 87
Disk failure ........................................................................................................................................................................ 87
Storage Center failure scenarios ............................................................................................................................. 94
1 - Complete failure of Primary SC (Resources on Host A) .................................................................... 95
2 - Complete failure of Secondary SC (Resources on Host A).............................................................. 96
3 - Complete failure of Primary SC (Resources on Host B) .................................................................... 98
4 - Complete failure of Secondary SC (Resources on Host B) ............................................................100
Dell Confidential
Development
Hands-On Hyper-V stretched cluster and Live Volume Lab

Introduction
In this document you will find a detailed demo script illustrating the main features of the new Live
Volume SC 6.5 functionalities and their main use cases in a typical Hyper-V stretch cluster
environment.
The basic functionalities of the Live Volume feature and the most important use cases of the new
version (Storage Center 6.5) have already been described and covered in Addendum D:
“Compellent Live Volume and Storage Center 6.5””. Please refer to this document for further
details regarding Live Volume SC 6.5 and the new disaster recovery and failback functionalities.
The reader should also have some basics about Storage Center and Enterprise Manager utilization
and management, and also a very basic understanding and skills on Hyper-V are required.
Hyper-V is a layer of software that sits between the physical server’s hardware layer and the Hyper-
V guest virtual machines (VMs). Hyper-V presents hardware resources in a virtualized manner
from the host server to the guest VMs. Hyper-V hosts (also referred to as nodes or virtualization
servers) can host multiple Hyper-V guest VMs, which are isolated from each other but share the
same underlying hardware resources (e.g. processors, memory, networking, and other I/O
devices).
Microsoft Hyper-V in Windows Server 2012 contained numerous new features and improvements
from the previous version in Window Server 2008 R2. Some of the new features include a new
virtual hard disk format (VHDX), virtual fibre channel support, support for guest VMs on shared
file storage, Offloaded Data Transfer (ODX) support, live migration of multiple guests, live
storage migration, 150 built-in PowerShell Cmdlets, and better guest resource allocations.
Windows Server 2012 R2 adds additional features and improvements to Hyper-V. New features
include Live Migration with compression, shared virtual disks for guest clustering, storage quality
of service (QoS), virtual machine generation settings, enhanced session mode, and automatic
virtual machine activation.
Dell Confidential
Development
Environment Description
Introduction
The Dell Compellent storage infrastructure is based on a typical DR / LV organization with two
Storage Centers 6.5, each connected a node configured in a Microsoft Hyper-V cluster based
on two Windows Server 2012 R2 DC 64-bit Operating Systems.
As the physical characteristics of the different components may change, we will not focus on details
but just highlight the overall architectural layout:
As mentioned, we have an already configured Hyper-V stretch cluster, with a few configured
volumes and virtual machines that we will use for our disaster recovery and failback testing
procedures:
You can verify the status of the overall cluster or of any single node of the cluster using the “Failover
Cluster Manager”.
Verify that the quorum and cluster disks are on line. Depending on cluster status and events, it may
be necessary to manually bring these disks online. If the disks does not come online, it may be
Dell Confidential
Development
necessary to access Disk Management and rescan the disks on each node to make sure they
are visible on each node.
Once all the cluster disks are online, then verify the health of the cluster resources.
In this example, there are four guest VMs to verify. If necessary, manually start the guest VMs and
then verify that they are properly functioning.
Clearly the number and size of configured CSV and VMs, and consequently the number of the
already configured Live Volumes, can vary and can be adjusted depending on your needs; in
the following sections of this paper we will also address some basic configuration topics in
order to help you in modifying the configuration to better meet your needs, but please consider
that this document is not intended to be a summary of Hyper-V configuration procedures and
best practices, just a survival guide.
In this example, the environment has been set up as follows:
 The primary and secondary locations are “well connected” with adequate data bandwidth and
low latency between them to allow for data replication.
 Both locations are remotely accessible to administrators. This is important to ensure a timely
response to a DR event.
 A Dell Compellent Storage Center is configured at each location, each with sufficient IO and
volume (space) capacity to support the Hyper-V stretch cluster’s resources.
Here are the major details of the currently configured server and storage infrastructure.
Resource Name IP Address IP Address Remarks

(Mgmt) (iDRAC)
Server DT-POC- 192.168.100.245 192.168.100.84
PRI-
W12
Dell Confidential
Development
Server DT-POC- 192.168.100.252 192.168.100.85

DR-
W12
Storage SC 60601 192.168.100.100 192.168.100.96/97 Management
IP
Storage SC 60689 192.168.100.200 192.168.100.196/197 Management
IP
EM DC POC- 192.168.100.240
Mgmt-
Srvr2
VM 1 VM01-1 192.168.100.231 Gen1 –
W2008R2
VM VM02-1 192.168.100.232 Gen1 –
W2008R2
VM VM04-2 192.168.100.233 Gen1 –
W2008R2
VM VM05-3 192.168.100.234 Gen2 –
W2012R2
An Enterprise Manager Data Collector Server is installed and configured as an external location.
Usually in a real world configuration a DC will be configured in Site A, and also at the recovery
location, Site B. For example they could be installed on virtual servers that are not part of the
stretch cluster.
The remote Data Collector server’s role is to maintain a copy of the volume recovery point
information from the primary Data Collector server at Site A. This information on the remote
Data Collector server must be accessible at the recovery site in order to activate disaster
recovery.
At least two instances of the Enterprise Manager Client are installed:
 One instance is installed at the primary location on a virtual server that is not part of the stretch
cluster
 A second instance is installed at the remote location on a virtual server that is not part of the
stretch cluster.
Installing an instance of the Enterprise Manager client on the same VM as the Data Collector is
supported and recommended.
Note
The above list covers common design considerations for a stretch cluster environment but is not
meant to be all-inclusive.
1 VM name suffix shows the CSV # where the VM has been created and configured (e.g. HyperV-CSV1, HyperV-
CSV2, …). CSVs sizes are: 1 TB for CSV1, 2 TB for CSV2, 2.5 TB for CSV3
Dell Confidential
Development
Cluster Shared Volumes (CSV) and VMs creation

In order to create and add to the Hyper-V cluster a new CSV, the very first step is just to create a
new LV assigning, for example, the primary volume to the primary node (DT-POC-PRI-W12)
and the secondary copy to the other node in the cluster (DT-POC-DR-W12).
Note
Please do not forget to use the “Advanced Mapping” panel to assign the same LUN ID to the two
LUNs that the Live Volume wizard will create on the two storage centers (primary and
secondary) and finally map to the two Hyper-V clustered servers.
Also use “Edit Live Volume Settings” to adjust server and LUN configuration on the DR site.
This is fundamental for a proper failback procedure.
Dell Confidential
Development
Once the LV has been configured, you can perform a quick Live Volume swap operation between
primary and secondary storage, and vice-versa, to test the new configuration.
You can also modify LV settings, e.g. replication type.
Now, from the first node of the cluster or, anyway, from the node hosting the primary copy of Live
Volume, run the following GUI / command that will run you directly in the Disk Management
menu:
Server Manager > Tools > Computer Management > Disk Management
As in any traditional Windows system, we will need to put the new disk (volume) online, initialize it
and finally format it as MBR or GPT depending on its size or your needs.
Do not assign any drive letter now.
Dell Confidential
Development
We can now run Failover Cluster Manager:
Select “Add Disk” in the Disk panel and add the newly created Live Volume to the cluster.
Dell Confidential
Development
Once added the new disk, again from Failover Cluster Manager, select the new disk, right click on it
and select “Add to Cluster Shared Volumes”.
From now on the new CSV should be properly configured into the cluster and this is a great time
to test its failover functionalities Hyper-V cluster side, moving it from one node to the other and
checking its status independently from the LV configuration.
Note
Basically from now on you should be able to see the new CSV online after any swap between
the two nodes of the cluster and completely independently from the LV status. For example
the new CSV could be in UP status on the DR node while the primary LV is on the storage
connected to the PRI node, and vice-versa.
Dell Confidential
Development
Note
Originally Introduced in Windows Server 2008 R2 Failover Clustering, CSVs allow all nodes in a
cluster to simultaneously have read-write access to the same LUN that is formatted as an
NTFS or ReFS (2012 R2 only) volume. Using CSVs, clustered roles can fail over quickly from
one node to another node without requiring a change in drive ownership, or dismounting
and remounting a volume. In Windows Server 2008 R2, only Hyper-V workloads were
supported on CSVs. Windows Server 2012 expanded CSV functionality, allowing CSVs to be
utilized as file shares with the Scale-Out File Server role. Scale-out file shares can host
application data, such as Microsoft SQL Server and Hyper-V guests
We can now create a new VM on this CSV. Just select “Roles” in Failover Cluster Manager and then
“New Virtual Machines”:
The wizard will ask for the target node:
Dell Confidential
Development
The wizard will also ask you to assign the target folder, and you will select the standard CSV
directory in C:\ClusterStorage\Volume(n), where “n” is the assigned volume number:
You’ll need to complete a few more steps, assigning for example the “generation” of the VM, its
configured memo size, and finally the desired operating system.
Dell Confidential
Development
Preliminary testing
You can start or complete now some preliminary tests on this new cluster configuration and Live
Volume infrastructure. You can use now the standard LV documentation and procedures to
double check that, against any LV swap between primary and secondary node – and vice-
versa – both the CSV and all the configured VMs stay respectively in UP and RUNNING status:
Dell Confidential
Development
Basically the following two snapshots show how, after LV migration, both the CSVs and the
configured VMs are still on-line and running.
A further test could be that, after swapping Live Volumes, both the VMs and the CSVs preserve their
capabilities to seamlessly move from one node to the other of the Hyper-V cluster:
Dell Confidential
Development
Dell Confidential
Development
Disaster Recovery Test and Failover Procedures

Disk failure
Probably the best way to simulate a disaster is simply to delete the primary volume in a Live Volume
relationship. Just delete the volume from its primary node and even skip the recycle bin: the
primary volume is completely destroyed.
From now on, all the applications insisting on this CSV, along with the CSV itself, are completely
unavailable, and this is basically T0 for our RTO period.
Once the volume has been deleted, it will disappear from the Live Volumes tab and the
corresponding Restore Points row will show a degraded status; right click on the relevant
restore point and select “Activate Disaster Recovery”:
A pop-up menu will allow you to select different restore options and, depending on your needs,
you can select the desired PITC or, as in this example, the active replay, along with other
mapping options:
Dell Confidential
Development
Do not forget to use the “Advanced Mapping” option to verify that the DR Volume that will be
created will keep the original LUN ID. 2 You can check the status and completion of the DR
procedure through the “Recovery Progress” tab.
If you will, you can RDP to the DR site;
And again perform a volume rescan through the GUI: Server Manager > Tools > Computer
Management > Disk Management.
Once completed open Failover Cluster Manager and move the offline CSV to the DR node; it will
become immediately available and now you can restart the impacted VM or VMs:
2 For example, and for sake of simplicity, CSV #1 uses LUN ID = 10 on both nodes, CSV # 2 uses LUN ID = 20,
and so on and so forth
Dell Confidential
Development
This completes your downtime period and basically measures your real RTO.
Once the cluster has been recovered, or the primary node is back again and up and running, it’s
high time to reactivate the LV relationship.
In this example we have assumed a major disaster, with a Live Volume completely destroyed, and
this basically means that the rollback procedure will have to replicate back all data from the DR
site to the primary site.
In a second example we will consider the case of a whole Storage Center failure and see that when
the system is back into production, the alignment time simply depends on the amount of data
written in the remote site after all DR copies have been brought back into production.
In any case this procedure, where you basically select the desired recovery point and
“Restore/Restart DR Volumes”, is not service affecting and the re-alignment of the primary and
secondary (formerly primary) copies runs in the background. Basically we are coming back to
a fully protected Live Volume scenario.
Dell Confidential
Development
As mentioned before you can monitor the progress of this recovery procedure from both the
“Recovery Progress” tab of from the main “Live Volume” panel.
Note
If you simply delete the primary or secondary volume leaving these in the recycle bin, here is the
expected behavior of the whole system.
Secondary volume deleted:
 LV Status is: DOWN

 Cluster status is: Active
 LV status after volume recovery from recycle bin: UP
Primary volume deleted:
 LV Status is: DOWN

 Cluster status is: DOWN
 LV status after volume recovery from recycle bin: UP
Dell Confidential
Development
Another way to simulate a partial disaster is to remove the mapping to the host from the primary
volume in a Live Volume relationship. After removing mapping, the corresponding resources
(CSV, VMs, …) will go down:
The Live Volume Status tab will show no problem and the best and quickest way to recover from
this status will be to move the resource to the other node of the cluster, bringing it online, using
Failover Cluster Manager and benefitting of the proxy link between the two storage subsystems.
Another way to solve this failure status could be to swap the Live Volume relationship promoting
its secondary to primary role:
Once completed this swap you’ll have to simply move the cluster resource from its former primary
node to the secondary node (now primary in the Live Volume relationship):
Dell Confidential
Development
When possible you’ll recreate the broken mapping to the host and, if desired, recreate the original
Live Volume relationship.
Removing or losing mapping from a Live Volume perspective from the secondary system does not
create any disruption at Hyper-V cluster level. For example, should you delete the secondary
Live Volume you’ll have:
Please consider that, as now the Live Volume relationship is missing, the broken Live Volume will
be shown in the replication tab:
Run “Restore/Restart DR Volumes” and the system will show this panel:
Dell Confidential
Development
Note
Do not forget, once completed the restore activity, to add the proper mapping to the secondary
Live Volume as it will be created without any mapping: just map it to the secondary host in
the Hyper-V cluster and assign the relevant LUN ID.
The following tables summarize the different cluster and Live Volume statuses, their relationship
and the related stretch cluster service level with different Live Volume mapping status and in
the case of volume failure.
Basically these tables assume Host A as connected to Storage Center A and Host B connected to
Storage Center B; the (Primary) and (Secondary) note just describe a hypothetical Live Volume
configuration.
Cluster status and availability depending on Live Volume path status

# Host A Host B SC A (Primary) SC B (Secondary)
01 CSVs can move between nodes Path(s) UP Path(s) UP
VMs can move between nodes
Both always UP in any status LV status is UP LV status is UP
02 CSVs can move between nodes Path(s) UP Path(s) DOWN
Both always UP in any status LV status is UP LV status is UP
03 CSVs can move between nodes (proxy) Path(s) UP Path(s) DOWN
VMs can move between nodes Swap P > S Secondary
Both always UP in any status LV status is UP “active” LV
LV status is UP
04 CSVs can move between nodes (proxy) Path(s) UP Path(s) UP or
VMs can move between nodes Primary “active” DOWN
Both always UP in any status LV Swap S > P
LV status is UP LV status is UP
05 CSVs on Host A goes offline Path(s) DOWN Path(s) UP
Cluster brings it online on Host B
VMs restart on Host B
CSVs can stay only on Host B
LV status is UP LV status is UP
Same behavior in case 01 Once Path(s) UP
Cluster status and availability depending on primary and secondary Live Volume status
Dell Confidential
Development
# Host A Host B SC A (Primary) SC B (Secondary)

01 CSVs cannot move between nodes (UP Primary LV UP Secondary LV
on Host A) DOWN
VMs can move between nodes LV status is (deleted)
Restore procedure: DOWN LV status is DOWN
 Restore via “Restore/Restart DR”
from “Restore Point” tab
 Map the secondary LV to Host B
 Check restore progress in
“Recovery Progress” tab
 Wait for replica alignment
02 CSVs offline Primary LV Secondary LV UP
VMs offline DOWN
Restore procedure: (deleted)
 “Activate Disaster Recovery” from LV status is OFF
“Restore Point” tab LV status is OFF (no LV)
 Bring CSV online on Host B (no LV)
 VMs can move between Host A
and Host B
 Once primary is back …
 “Restore/Restart DR Volumes” da
“Restore Points”
 Proper volume mapping
 Check restore progress in
“Recovery Progress” tab
 Wait for replica alignment
 When completed, swap back
secondary to primary Live Volume
Storage Center failure scenarios

In our testing scenarios we have checked the following possible events:
Cluster resources Primary SC Secondary SC

Active on Host A 1. Complete SC failure 2. Complete SC failure
Active on Host B 3. Complete SC failure 4. Complete SC failure
Dell Confidential
Development
1 - Complete failure of Primary SC (Resources on Host A)
After a complete failure of the primary SC, all Live Volumes are in DOWN status and the cluster
services are inoperative; from now on, all the applications insisting on this CSV, along with the
CSV itself, are completely unavailable, and this is basically T0 for our RTO period.
To restart services, go to “Restore Points” tab in Replication / Live Volume panel of Enterprise
Manager, select the desired Live Volume and, starting from quorum volume, progressively
activate the disaster recovery counterparts:
In the “Recovery Progress” tab, you’ll see the progress of these events, and when their status is
“Finished” for all Live Volumes, you have completed your disaster recovery activities (T1 for our
RTO period):
Dell Confidential
Development
Once the primary storage center is back again and ready to rejoin the production environment, just
run for each Live Volume, again starting from the quorum volume, the “Restore / Restart DR
Volumes” procedure:
Again, when completed, in the “Recovery Progress” tab you’ll see:
Note
Please consider that in this case the fail back procedure will be quicker than in the case of complete
loss or destruction of the primary volume because the system has just to copy back only the
data modified since the disaster, and not the complete volume.
Also, do not forget to check that after completing the failback procedure, all Live Volume LUNs
still keep the originally assigned LUN Id. On each storage center.
2 - Complete failure of Secondary SC (Resources on Host A)
Dell Confidential
Development
After the crash of the secondary SC, all Live Volumes status is DOWN but applications are unaffected
and you can move VMs between the two nodes, even if you cannot move CSVs:
Right after secondary SC rejoins the Live Volume configuration, Enterprise Manager automatically
reconfigures all Live Volumes in a fully available status, and the Hyper-V cluster reacquires all
swap functionalities:
Dell Confidential
Development
3 - Complete failure of Primary SC (Resources on Host B)
This case is much similar to case #1. After a complete failure of the primary SC, all Live Volumes are
in DOWN status and disappear from the “Live Volume” tab. Cluster services are inoperative, and
from now on all the applications insisting on this CSV, along with the CSV itself, are completely
unavailable, and this is basically T0 for our RTO period.
To restart services, go to “Restore Points” tab in Replication / Live Volume panel of Enterprise
Manager, select the desired Live Volume and, starting from quorum volume, progressively
activate the disaster recovery counterparts:
In the “Recovery Progress” tab, you’ll see the progress of these events, and when their status is
“Finished” for all Live Volumes, you have completed your disaster recovery activities (T1 for our
RTO period):
Dell Confidential
Development
Once the primary storage center is back again and ready to rejoin the production environment, just
run for each Live Volume, again starting from the quorum volume, the “Restore / Restart DR
Volumes” procedure:
Again, when completed, in the “Recovery Progress” tab you’ll see:
Note
Please consider that in this case the fail back procedure will be quicker than in the case of complete
loss or destruction of the primary volume because the system has just to copy back only the
data modified since the disaster, and not the complete volume.
Also, do not forget to check that after completing the failback procedure, all Live Volume LUNs
still keep the originally assigned LUN Id. On each storage center.
Dell Confidential
Development
4 - Complete failure of Secondary SC (Resources on Host B)
Same Live Volume behavior, as per case 2: Live Volume status is DOWN. Hyper-V clusters moves
CSVs to Host A and, again, VMs can swap between the two nodes of the cluster. Right after
secondary SC joins the Live Volume configuration, Enterprise Manager automatically restarts all
Live Volumes in a fully available status, and the Hyper-V cluster reacquires all swap
functionalities.
Dell Confidential

Mod - 6 - FGA - CML - VLAB - v1.15 With LV65 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Mod - 6 - FGA - CML - VLAB - v1.15 With LV65 PDF

Caricato da

Copyright:

Formati disponibili

vLAB Pilot – Addendum D

Document Version 1.15

Date: Sept 2013 Internal Use Only

Author: Mark Miley & Angelo Rivano Dell Confidential

Author: Mark Miley Page 2 of 100 Internal Use Only

5.2 - Demo Session 2 - Data Protection .............................................................................................................. 46

Author: Mark Miley Page 3 of 100 Internal Use Only

Addendum D: Compellent Demonstration Labs

5.0 - Introduction and Preparation

Author: Mark Miley Page 4 of 100 Internal Use Only

5.0.1 - Demo Environment Diagram

Author: Mark Miley Page 5 of 100 Internal Use Only

5.0.2 - Preparing the Demo Environment

Some additional steps that should be completed prior to commencing a demo;

Understand the customer’s Current infrastructure:

Author: Mark Miley Page 6 of 100 Internal Use Only

Understand the customer’s desired infrastructure ‘Wins’

Pre-Demo points to cover

Author: Mark Miley Page 7 of 100 Internal Use Only

In this section you will be completing the following tasks:

Logging into Enterprise Manager

Logging into vCenter Server

Author: Mark Miley Page 8 of 100 Internal Use Only

Logging into Storage Center

5.0.3 - Navigation - Set the Scene

Key Talking Points

Author: Mark Miley Page 9 of 100 Internal Use Only

Technical Selling Points:

Technical Objective Handling:

Question: Enterprise Manager requires a Windows installation and SQL license?

Author: Mark Miley Page 10 of 100 Internal Use Only

5.1 - Demo Session 1 - Compellent ease of use and volume management

In this demo you will be performing the following tasks:

Author: Mark Miley Page 11 of 100 Internal Use Only

Technical Selling Points

Author: Mark Miley Page 12 of 100 Internal Use Only

Technical Objective Handling

*Although UNMAP is supported in VMware, this is for VMFS volumes only. If a

Author: Mark Miley Page 13 of 100 Internal Use Only

5.1.1 - Signing into the Compellent Storage Center GUI

1. Double-click on the Compellent Storage Center shortcut on the desktop.

Author: Mark Miley Page 14 of 100 Internal Use Only

5.1.2 - Creating a new volume

2. Click on Redundant in the Create Volume wizard.

3. Click Continue to accept the default volume size of 500 GB.

Author: Mark Miley Page 15 of 100 Internal Use Only

4. Click Continue to accept the Recommended Storage Profile (All Tiers).

6. Click Create Now to complete the wizard.

Author: Mark Miley Page 16 of 100 Internal Use Only

5.1.3 - Mapping the volume to a server

1. Click Map this Volume to a Server.

2. Select your Windows demo server and click Continue.

3. Click Advanced on the verification window.

Author: Mark Miley Page 17 of 100 Internal Use Only

5. Click Create Now to complete the volume mapping wizard.

6. Click the Close button.

7. Click Demo Volume 1 in the Storage Center GUI.

Author: Mark Miley Page 18 of 100 Internal Use Only

Author: Mark Miley Page 19 of 100 Internal Use Only

5.1.4 - Viewing the volume in Windows

1. Double-click on the Rescan shortcut on the desktop.

2. Click the Computer Management icon from the desktop taskbar.

3. Select Disk Management from the left hand tree.