Professional Documents
Culture Documents
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the
problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
© 2019 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Other trademarks may be trademarks of their respective owners.
2019 - 10
Rev. 110-6302-EN-R2
Contents
2 Installing VSM............................................................................................................................ 10
About VSM Installation........................................................................................................................................................ 10
Installation Prerequisites......................................................................................................................................................10
Specifying a vCenter Server-Managed IP................................................................................................................... 11
Using Certificates............................................................................................................................................................11
Information Required for VSM Installation Wizard........................................................................................................... 11
Perform a New Installation of VSM................................................................................................................................... 13
Updating the VSM Appliance from Version 4.7................................................................................................................14
Attaching the ISO Image to the VSM Virtual Appliance............................................................................................15
Running the Update....................................................................................................................................................... 15
Verifying the Installation...................................................................................................................................................... 16
Verifying Permissions Before Running VSM.....................................................................................................................16
Remove the VSM Appliance from vSphere......................................................................................................................16
Contents 3
System Schedules Panel...............................................................................................................................................26
Modify Schedule Dialog Box.........................................................................................................................................27
VSM Peers Panel...........................................................................................................................................................28
Replication Partners Panel........................................................................................................................................... 29
vCenter Servers Panel.................................................................................................................................................. 32
Advanced Settings........................................................................................................................................................ 32
Ports Used by VSM.............................................................................................................................................................33
8 Managing Datastores.................................................................................................................. 48
Navigating Datastores........................................................................................................................................................ 48
VSM Datastores Summary View and Actions................................................................................................................. 48
Virtual Volume Operations and Restrictions.................................................................................................................... 49
VSM Datastore Actions......................................................................................................................................................50
Create Dell Datastore Wizard...................................................................................................................................... 50
Create VMFS Datastore............................................................................................................................................... 52
Create NFS Datastore.................................................................................................................................................. 54
Create VVol Datastore..................................................................................................................................................54
Resize Dell Datastore Dialog Box.................................................................................................................................55
Delete a VSM Datastore...............................................................................................................................................56
Apply Template Dialog Box...........................................................................................................................................56
Replication Configuration Dialog Box..........................................................................................................................58
Deconfiguration Replication......................................................................................................................................... 59
4 Contents
Pause and Resume Replication....................................................................................................................................59
SyncRep Operations for Datastore Volumes............................................................................................................. 59
Datastore Storage View...................................................................................................................................................... 61
Datastore Summary View..............................................................................................................................................61
Datastore Monitor View................................................................................................................................................62
Datastore Configure View............................................................................................................................................ 62
Datastore Related Objects View..................................................................................................................................64
9 Data Recovery........................................................................................................................... 65
Structure of the Data Recovery Table............................................................................................................................. 65
Search VSM Managed Objects......................................................................................................................................... 65
10 Data Protection........................................................................................................................ 66
VSM Data Protection Table............................................................................................................................................... 66
About Snapshots................................................................................................................................................................. 67
Best Practices for Snapshots...................................................................................................................................... 67
Snapshot View in the Data Protection Table.............................................................................................................68
Planning Snapshots....................................................................................................................................................... 69
Create Snapshot Dialog Box........................................................................................................................................ 70
Restoring from a Snapshot........................................................................................................................................... 71
About Snapshot Schedules................................................................................................................................................ 72
Add Schedule/Edit Schedule Dialog Box.................................................................................................................... 73
Edit Schedule................................................................................................................................................................. 75
Delete Schedule............................................................................................................................................................. 75
Enable and Disable Schedule........................................................................................................................................75
Run Now......................................................................................................................................................................... 76
About Clones........................................................................................................................................................................76
Clone Volume from Snapshot Dialog Box...................................................................................................................76
Clone VVol VM from Snapshot.................................................................................................................................... 77
About Replication.................................................................................................................................................................78
Types of Replication Provided by VSM...................................................................................................................... 78
Replication Operations..................................................................................................................................................80
11 VSM Schedules......................................................................................................................... 88
VSM Schedules View..........................................................................................................................................................88
Filter the Schedules Table.................................................................................................................................................. 89
12 Managing Jobs......................................................................................................................... 90
Jobs View............................................................................................................................................................................. 90
Filter Job Listing.................................................................................................................................................................. 90
Getting Job Details...............................................................................................................................................................91
13 Templates................................................................................................................................ 92
About ACL Templates.........................................................................................................................................................92
ACL Templates Dialog Box........................................................................................................................................... 92
Create ACL Template................................................................................................................................................... 93
Modify ACL Template................................................................................................................................................... 93
Clone ACL Template..................................................................................................................................................... 93
Delete ACL Template.................................................................................................................................................... 94
Contents 5
Add ACL for Host.......................................................................................................................................................... 94
Add ACL for Cluster...................................................................................................................................................... 94
Create ACL Template from Volume............................................................................................................................95
About Schedule Templates................................................................................................................................................ 95
Edit Schedule Template Dialog Box............................................................................................................................ 95
Add a Schedule Template.............................................................................................................................................96
Edit Schedule Template................................................................................................................................................96
Delete Schedule Template............................................................................................................................................97
A Troubleshooting........................................................................................................................107
Installation and Startup Issues..........................................................................................................................................107
Scheduling Issues...............................................................................................................................................................108
Data Protection Issues...................................................................................................................................................... 109
Replication Issues...............................................................................................................................................................109
Group Management Issues................................................................................................................................................110
Multipathing Recommendation.........................................................................................................................................110
Index.......................................................................................................................................................................111
6 Contents
Preface
About This Manual
Revision History
Document Number: 110-6302–EN
Audience
The information in this guide is intended for VMware administrators responsible for configuring and using the Dell Virtual Storage Manager
application within VMware vSphere.
Contacting Dell
Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services
might not be available in your area. To contact Dell for sales, technical support, or customer service issues, go to dell.com/support.
Related Documentation
If you plan to install the Dell EqualLogic Multipathing Extension Module, see the Dell EqualLogic Multipathing Extension Module Installation
and User’s Guide.
In addition to this Installation and User’s Guide, the VSM documentation includes:
• Release Notes — Provides the latest information about the product, a description of new features for the release, required software
revisions, and known issues.
• Online help — Provides help about options and tasks when using the graphical user interface (GUI). You access the online help for
VSM concepts by clicking links under Explore Further on VSM menus. If a dialog box or other element contains a question mark icon
(?), you can click that icon to access help for that particular task.
The Dell EqualLogic Group Manager Administrator's Guide and the Group Manager online help describe how to use the Group Manager.
See these sources for more information about viewing storage containers and protocol endpoints from the Group Manager. The guide also
provides additional information about replication on Dell EqualLogic arrays.
Detailed descriptions of how to configure and manage vCenter and vSphere are beyond the scope of the Dell EqualLogic documentation.
For detailed descriptions of how to configure and manage vCenter and vSphere, select Help from the vSphere user interface.
Terminology
Because VSM is designed to manage Dell EqualLogic arrays and volumes within the context of the VMware vSphere environment, it is
important to understand the terminology that is specific to VMware and to the Dell EqualLogic host integration tools.
Term Definition
Replica set In the Dell EqualLogic model, a replica represents the contents of the volume at the time the replica was created.
Each replicated volume has a replica set, which is the set of replicas created over time. A VMware entity may only
be included in a single replication unit made up of a single root-managed object and all the related dependent
objects in its topology. The topology and schedule are collectively called a replica set. A replica set contains a set
of replicas, one for each machine that participates in replication.
Synchronous SyncRep is conceptually similar to data mirroring. It is a technology provided by the PS Series group that allows all
replication writes on an active volume to also be written on the standby volume before the active volume (mirror) can
(SyncRep) respond with success. Running in synchronous mode indicates that the standby volume has the same data that
resides on the active volume.
VASA provider A storage-side software component that provides a storage awareness service for vSphere.
Virtual appliance After installation, VSM resides on a virtual machine that is accessed by VMware vSphere. In VMware terminology,
this application is deployed as a virtual appliance.
Virtual volume The VMware concept virtual volume (VVol) provides the technology for dividing a physical volume into a set of
smaller virtual volumes. The VVol type can be applied during the creation of Dell datastores. The VVol type
requires VMware vSphere 6 with Dell EqualLogic firmware version 8.0.x or later.
VSM Server The term VSM Server refers to the virtual machine that is running VSM and which can be set up and managed
using the VSM console CLI and the settings in the user interface.
Topics:
• About VSM Installation
• Installation Prerequisites
• Information Required for VSM Installation Wizard
• Perform a New Installation of VSM
• Updating the VSM Appliance from Version 4.7
• Verifying the Installation
• Verifying Permissions Before Running VSM
• Remove the VSM Appliance from vSphere
Installation Prerequisites
This section describes the prerequisites for a new installation of VSM.
Software Requirements
Refer to the Dell Virtual Storage Manager Release Notes for a list of the environment requirements for VSM.
If you plan to install the Dell EqualLogic Multipathing Extension Module (MEM), see the Dell EqualLogic Multipathing Extension Module
Installation and User’s Guide.
To install OVA, you must have the VMware Client Integration plug-in installed for vCenter.
VSM must be installed from within the vCenter from which you plan to manage your virtual volumes.You must synchronize the time
between the vCenter and the VASA provider.
10 Installing VSM
Specifying a vCenter Server-Managed IP
Prior to installing VSM, verify that the vCenter Server Managed IP has been set. VSM uses this setting as a means of identifying the IP
address to communicate with vCenter. If this IP address is not set, VSM will not complete the boot process. To set the IP address using
the vSphere Web Client:
Steps
1. Select vCenter from the Home menu, then vCenter Home from the vSphere Web Client navigator.
2. Browse to find your vCenter server from the vCenter Servers inventory lists.
3. Click Configure > Settings.
4. Select the General category from the list on the left side of the Settings menu.
5. To modify the vCenter server settings, click Edit.
6. Click Runtime Settings.
7. On the Runtime Settings page, enter a valid IP address. The address must be accessible from the same subnet as the IP that will be
assigned to eth0 on the VSM virtual machine when deploying the OVA. See Figure 1. vCenter Server Settings in vSphere Web Client.
8. Click OK.
Results
Using Certificates
About this task
By default, the certificate used by VSM is a self-signed Dell certificate. If you want to use your own certificate, you must replace the Dell
certificate. Contact Dell Technical Support to facilitate a certificate change.
Installing VSM 11
NOTE: After you complete the installation wizard, you modify some of these values using the VSM Settings Manage tab.
See VSM Settings Panel.
Option Description
Name Name of the VSM virtual appliance. This name must be unique within the vCenter datacenter.
The host name must be between 1 and 255 characters (inclusive).
Folder or datacenter Parent datacenter and optionally an inventory folder where the appliance VM is located.
Resource Select a cluster, host, vApp, or resource pool in which to run the deployed virtual appliance.
NOTE: VSM should be deployed on a host that is not configured to access VVols.
This precaution prevents the potential conflict of a host attempting to access the
VASA provider during startup and the VASA provider not being available until after
the host has loaded and started the VSM appliance.
Virtual Disk Format Format used to store the virtual machine disks. Choose one of the following formats:
• Thick Provision Lazy Zeroed — Creates a virtual disk in a default thick format. Space
required for the virtual disk is allocated when the virtual disk is created. Data remaining on
the physical device is not erased during creation, but is zeroed out on demand later on first
write from the virtual machine.
Using the default flat virtual disk format does not zero out or eliminate the possibility of
recovering deleted files or restoring old data that might be present on this allocated space.
You cannot convert a flat disk to a thin disk.
• Thick Provision Eager Zeroed — Creates a type of thick virtual disk that supports clustering
features such as fault tolerance. Space required for the virtual disk is allocated at creation
time. In contrast to the flat format, the data remaining on the physical device is zeroed out
when the virtual disk is created. It might take much longer to create disks in this format than
to create other types of disks.
• Thin Provision — Creates a thin disk that only initially uses as much datastore space as the
disk needs for initial operations, based on the value that you enter for the disk size. Use this
format to save storage space.
Destination datastore Select from the list of available datastores to specify a destination storage area for the virtual
machine configuration files and all of the virtual disks that allow management connections to the
vCenter server. VSM should be placed on a datastore that is not also used by VMs for which it is
taking snapshots and performing replication.
Network Network to which the NIC should be attached. Select an available network from the list.
Host Name The fully-qualified domain name (FQDN) of the VSM virtual appliance. This name is not the name
of the ESXi host running the virtual machine.
The following restrictions apply to host-name naming:
• Host names are allowed to contain A-Z, 0–9, and the hyphen character (-). The period
character (.) is allowed as part of the name.
• Each period-separated component of the host name can have 1–31 characters, and the
entire host name must be 1–255 characters in length.
• Host names cannot begin or end with a hyphen.
• A host name cannot contain only numeric characters.
12 Installing VSM
Option Description
Management Network IP Address IP address to be used for the management network interface (eth0). The management network
is the network on which the vCenter server resides. Leave this field blank if you plan to use
DHCP.
Management Network Netmask Netmask or prefix to be used for the management network interface. Leave this field blank if you
plan to use DHCP.
vService Bindings Select from the list of available vServices to specify the vServices to which the VSM virtual
appliance should be bound.
Prerequisites
The VSM kit includes the following file that is required for installation:
VSM-5.0.n.nnn.ova — The Open Virtualization Archive package, where nnn is the current build number.
Dell recommends that you copy this file to your local system and make it available in a convenient location, such as your computer
desktop.
NOTE:
Prior to running this deployment, you must set the vCenter Server Management IP. See Specifying a vCenter Server-
Managed IP.
Steps
1. Navigate to the Hosts inventory list under vCenter in the vSphere Web Client.
2. Click Actions > Deploy OVF Template.
The Select source dialog box opens. From here you can browse your computer to locate the VSM-4.7n.nnn.ova file if you previously
saved it locally. Optionally, select the OVA file from a URL.
3. After selecting the file, click Next.
The Review details page shows the details of the selected OVA file.
NOTE: The Deploy OVF template wizard shows a message indicating that the OVF package contains extra
configuration options, which could pose a potential security risk. You can ignore this message.
4. Click Next.
The first page of the End User License Agreement opens. This first page provides a warning about the vCenter Server Management
IP.
5. To proceed, click Accept on the End User License Agreement pages.
The Select name and folder dialog box opens.
6. (Optional) Change the name of the appliance to be deployed. The default is “Dell Virtual Storage Manager for VMware.”
7. Browse the inventory to select the datacenter and (optionally) a folder in which to locate the virtual appliance. Then click Next.
The Select a resource dialog box opens.
8. Select the location (host, vApp, or resource pool) where the VSM appliance is to be deployed. Then click Next.
The Select storage dialog box opens.
9. Select the virtual disk format to be used.
10. Select from the available resource pools to specify where the virtual appliance is to be deployed. Click Next.
The Setup networks dialog box opens.
NOTE: In some cases, the vSphere Web Client shows the error A connection error occurred. Verify that
your computer can connect to vCenter Server.. This error might prevent you from going to the next step
in the installation. See vSphere Web Client Connection Error.
11. From the list of networks, select a network to which the NIC should be attached. Then click Next.
The Customize template dialog box opens.
12. Enter the values as prompted:
a) Specify a host name to be assigned to the appliance.
Installing VSM 13
b) Select the time zone for your environment.
c) Enter the NTP server to use. You can specify multiple NTP servers in a comma-separated list. If you leave the NTP Servers field
blank, NTP synchronization will be disabled
13. Click the arrow next to Networking Properties to expand the additional settings:
a) Type the IP address for the default gateway for this VM. Leave this field blank if you plan to use DHCP.
b) Type a comma-separated list for DNS servers. Leave this field blank if you plan to use DHCP.
c) Type the IP address of the management network. Leave this field blank if you plan to use DHCP.
d) Type the netmask or prefix for the management network. Leave this field blank if you plan to use DHCP.
e) Click Next.
The vService bindings dialog box opens.
14. Select from the list of vService bindings. Click Next.
The Ready to Complete page shows a summary of the selections you chose.
15. (Optional) Select the checkbox to specify that the virtual appliance should be powered on after deployment.
16. Click Finish to accept these selections.
Results
The Recent Tasks list shows that the Deploy OVF template task is in progress. When the installation has completed successfully, the Dell
Virtual Storage Manager icon will open in the vSphere Web Client. Clicking this icon launches VSM.
Next steps
NOTE: If you plan to use virtual volumes in your environment, follow the instructions in Managing Virtual Volumes With
VSM.
Source Destination
VSM version 4.7, PS Series firmware version 9.1, ESXi 5.5 Update VSM version 5.0, PS Series firmware version 10.0.1, ESXi 6.0
3 GA, vCenter 5.5 Update 3 GA Update 3 GA, vCenter 6.0 Update 3 GA
VSM version 4.7, PS Series firmware version 9.1, ESXi 6.0 Update VSM version 5.0, PS Series firmware version 10.0.1, ESXi 6.5 U2,
3 GA, vCenter 6.0 Update 3 GA vCenter 6.5 u2 GA
VSM version 4.7, PS Series firmware version 9.1, ESXi 6.5 GA, VSM version 5.0, PS Series firmware version 10.0.1, ESXi 6.7 GA,
vCenter 6.5 0b vCenter 6.7 GA
VSM vesrion 4.7, PS Series firmware version 9.1, ESXi version 6.7, VSM version 5.0.1, PS Series firmware version 10.0.1; ESXi 6.7u1,
vCenter version 6.7 6.7u2, 6.7u3; vCenter 6.7u1, 6.7u2, 6.7u3
After updating to vSphere 6, you must reregister the VASA provider. See Configuration Options.
14 Installing VSM
3. In the shell prompt type the following command to remove the old kernel RPM.
# rpm -e kernel-2.6.32-279.el6.x86_64
Prerequisites
• Dell recommends that you take a VMware snapshot of the appliance before performing an update. After you confirm that the
appliance has updated correctly, you should delete the VMware snapshot.
• Disable all snapshot and replication schedules and make sure that no VSM jobs are running.
Steps
1. Select 2 from the main CLI console menu. The Maintenance submenu opens:
Maintenance
----------------------------------------------------
1. Update appliance software version
2. Database Backup
3. Database Restore
4. Return to main menu
Item
----------------------------------------------------
1. Appliance version
2. Check for updates
3. Install updates
4. Return to main menu
Next steps
You must log out and then log in to the vSphere Web Client after the update process completes.
Installing VSM 15
NOTE: After the update completes, depending on the size of data in the storage group (number of volumes, snaps,
members, pools) it might take a while for VSM to initialize and the VASA provider to be visible. VSM should be
accessible when it is initialized and the VSM server starting-up alarm is cleared.
Steps
1. Click the Monitor tab in the Hosts inventory.
2. In the Events view, verify that the VSM Server Starting Up alarm message is displayed, indicating that the status has changed
from yellow to green.
3. Restart the web browser to allow the client to integrate the VSM plug-in within its user interface.
16 Installing VSM
3
Console CLI Options
Logging in to the CLI Console
To log in to the CLI console:
Steps
1. From vSphere, right-click the VSM appliance from the hierarchy of virtual machines, then select Open Console
2. To log in to the console, press Enter. Then log in to the virtual appliance with the following default credentials:
• User name: root
• Password: eql
NOTE: You can change the root passwords using the Configuration CLI option. See Configuration Options
Example
After you log in, the CLI menu is displayed, similar to the following example:
############################################################################
Welcome to Dell Virtual Storage Manager
Version - 5.0.0.2294 2019.Jan.18
############################################################################
Item
----------------------------------------------------------------------
1. Configuration
2. Maintenance
3. Diagnostics
4. Reboot appliance
5. Logout
Option Description
Configuration Allows you to set various configuration options. See Configuration Options.
Maintenance Allows you to update the appliance software and back up or restore your database. See Maintenance
Operations.
Diagnostics Generates diagnostic information that can be sent to Dell EqualLogic customer support. See
Collecting Diagnostics.
Reboot Reboot appliance
Logout Log out of the appliance
Steps
1. Connect to the VSM appliance or open the VSM VM console. Log in as the root user. You can use ssh (if enabled) to connect to the
appliance.
2. Select Configuration from the console menu.
3. Select Unregister to unregister VSM from vCenter.
4. Select Return to main menu.
The CLI returns to the Configuration menu.
5. Select Logout.
6. Power off the Dell Virtual Storage Manager VM from the vSphere Web Client.
7. Delete the VSM VM.
Maintenance Operations
When you select the Maintenance option, you have the following choices:
• Update appliance version
• Database Backup
• Database Restore
All files read or written by the Database Backup and Database Restore options are in the CIFS share accessible using the root
password.
The CIFS share of VSM is mountable on any platform that supports CIFS or from a browser using the https URL.
You can access the CIFS share from a browser by specifying either of the following formats:
• https://ip-address or dns-name/davenport/ip-address or dns-name/database/
• smb://ip-address or dns-name/database/
Backing Up a Database
The Backup option executes a database backup immediately and shows the name of the database file created.
Steps
1. Select Maintenance from the main CLI console menu.
The Maintenance submenu opens.
2. Select Database Backup from the Maintenance submenu.
Example
Example:
Next steps
Backups are stored locally. For disaster recovery, Dell recommends that you move these files off the CIFS share and store them in another
location.
NOTE: Only scheduled backups are shown in the plug-in user interface. Backups done through the Backup option are
not shown in the user interface. Backups are also scheduled once a day within the appliance. By default, 30 days of
backups are retained.
Restore a Database
The Restore option prompts for a backup file and restores it. This backup file could either be from a previous local backup or from
another appliance backup. The database that you attempt to restore must be from the same version of VSM that is currently running on
the installed appliance.
Use one of the following methods to identify the version of VSM that is running:
• Open the console for the VSM virtual appliance.
• From vSphere, view the properties of the VSM virtual appliance.
After completing the restore operation, you can restart the service.
The backup file must be prefixed with dbbackup and have an extension of .sql.
Steps
1. Select Maintenance from the main CLI console menu.
The Maintenance submenu opens.
2. Select Database Restore from the Maintenance submenu.
Example
Example:
Collecting Diagnostics
When you select the Collect Diagnostics option, you have these choices:
• Gather support information — Generates a zip file containing system information such as the system state and the log files that are
saved on your VSM CIFS share. Use this option when contacting Dell EqualLogic Technical Support.
NOTE: For information about the CIFS share, see Maintenance Operations.
• Enable debug server logging — Enables verbose logging. This logging can be helpful when contacting customer support.
• Execute ping to a given host name or IP address
• Show routes — Used to view the virtual appliance’s IP routing table
• Show configuration summary
Callout Description
1 VSM Home — Displays overall information about VSM and allows you to set general configuration values. See VSM Home
Workspace.
2 Dell Storage — Allows you to manage Dell storage, including PS Series groups.
See Managing Groups in VSM.
5 Workspace tabbed views. The following tabs are presented for most items:
• Getting Started — Provides a description of the feature
• Summary — Displays identification characteristics for the selected item
• Monitor — Displays detailed status information for the selected item
• Manage — Allows you to set and modify configuration values
• Related Objects — Displays VMware inventory items that are related to the selected item
6 Explore Further conceptual help links — Click a topic link to view the related help page.
Summary Tab
The Summary tab displays information about the current state of your VSM virtual appliance and provides links to other vSphere and
VSM views.
The Summary content area contains the following portlets:
• Appliance Details — Identifies these configuration values and links:
• Virtual Machine name — Clicking the virtual machine name opens the vSphere Summary view for that virtual machine.
• Hostname — Identifies the name of the host on which the VSM virtual appliance is installed.
• Management IP IPv4 — Primary management IP address, of the VSM VM, if IPv4 is the Internet Protocol being used. It is called
by the VSM plug-in through the vCenter web service for all VSM-related content.
• Management IP IPv6 — Primary management IP address of the VSM VM, if IPv4 is the Internet Protocol being used. It is called by
the VSM plug-in through the vCenter web service for all VSM-related content.
• Timezone — Identifies the time zone as set during installation.
• NTP Servers — Identifies the NTP servers as set during installation.
• ESX Host — Identifies the ESXi host currently running the VSM virtual appliance. Clicking the ESX host name opens the vSphere
Summary view for that ESXi host machine.
• Alarm Count — Provides a count of active alarms on the VSM VM. Clicking the value in the alarm count opens the vSphere
Monitor view for alarms.
• Peers — Lists the VSM peers that are currently configured, including IP address and host name and the status of each peer. Clicking
the hyperlink for Add Peer opens the dialog box for adding a VSM peer. See Add a VSM Peer.
• Storage Health — Identifies all storage groups and their status and the number of related events for each PS Series group.
• Clicking the name of a PS Series group opens the vSphere Summary view for that group.
• Clicking the value for events opens the vSphere Monitor view for events.
• Clicking the hyperlink for Add Groups opens the Add PS Series Group dialog box. See Add a PS Series Group.
Item Description
Version Version of VSM installed
Hostname Fully-qualified domain name of the VSM server. The name is limited to 255 characters. The period
character (.) is allowed as part of the name.
Timezone Time zone in which the VSM server should be running
NTP Servers Comma-separated list of NTP servers to be used. For best results, ensure that this list is the same as
that used by the vCenter server and the groups it will manage.
Steps
1. Click VSM Home > Manage.
2. Click Settings > Edit.
3. Modify the following settings:
• Hostname — Fully-qualified domain name of the VSM server. The name is limited to 255 characters. The period character (.) is
allowed as part of the name
• Timezone — Time zone in which the VSM server should be running
• NTP Servers — Comma-separated list of NTP servers to be used. For best results, ensure that this list is the same as that used
by the vCenter server and the groups it will manage.
4. Click OK.
Results
For installation instructions, see Installing VSM.
Option Description
Network Connection The virtual network that the VSM virtual machine should connect to in order to communicate management
operations with VMware services.
Configuration Determines whether the network should either be statically configured or based on DHCP
Steps
1. Click VSM Home > Manage.
2. Click Management Network > Edit.
3. Modify the configuration settings.
• Network Connection — The virtual network that the VSM virtual machine should connect to in order to communicate
management operations with VMware services.
• Configuration — Determines whether the network should either be statically configured or based on DHCP
• IP Address — IP address to be used for the management network interface (eth0). The management network is the network on
which the vCenter server resides. Leave this field blank if you plan to use DHCP.
• Netmask — Netmask or prefix to be used for the management network interface. Leave this field blank if you plan to use DHCP.
• Default Gateway — Default gateway for this virtual machine appliance. Leave this field blank if you plan to use DHCP.
• DNS Servers — Comma-separated list of domain name servers VSM should access for domain name to IP address resolution.
Leave this field blank if you plan to use DHCP.
4. Click OK.
You must use the VMware user interface to configure a new virtual switch that is on, or routed to, the array’s
management network (if enabled) or the array iSCSI network to make it visible to VSM.
Option Description
Status Identifies whether the storage network is enabled or disabled
Network Connection Lists available networks to be used for the storage network
Configuration Determines whether the network should either be statically configured or based on DHCP
IP Address IP address to be used for the storage network interface. Leave this field blank if you plan to use
DHCP.
Netmask Netmask or prefix to be used for the storage network interface. Leave this field blank if you plan
to use DHCP.
Gateway Default gateway for the storage network. Leave this field blank if you plan to use DHCP.
Additional Route Additional route to configure a single static route if a second route is required
NOTE: You can use VSM to configure a storage network only if a secondary network is available on the ESXi host on
which VSM is deployed.
You must use the VMware user interface to configure a new virtual switch that is on, or routed to, the array’s
management network (if enabled) or the array iSCSI network to make it visible to VSM.
Steps
1. Click VSM Home > Manage.
2. Click Storage Network > Edit.
3. Modify the settings:
• Status — Select the Enabled checkbox to enable the use of a storage network.
• Network Connection — Select a network from the available networks in the Network Connection menu.
• Configuration (Optional) — Select the Use DHCP checkbox.
• IP Address — Type the IP address for the storage network.
• Netmask — Type the netmask for the storage network.
• Additional Route (Optional) — Enter an additional route to configure a single static route if a second route is required from the
storage network to the SAN.
• Gateway — Type the gateway for the additional route on the storage network.
4. Click OK.
Next steps
After you complete the configuration of a storage network, VSM automatically adds the virtual network interface card (vNIC) and
requests a reboot.
The vSphere Web Client will not be able to communicate with VSM until it reboots and the application server is ready to process requests.
After the process completes, the VSM plug-in will automatically reconnect, so no restart of the Web Client should be necessary.
Monitor Monitors VSM disk space usage. If the disk space exceeds the default value of 90 percent, a
warning alarm is triggered when this task is run. Disk Space Threshold can be modified in a range
of 60 percent to 95 percent.
You can modify the time interval for repeating the schedule.
Purge Removes all those orphaned VVol snapshots which are not committed for more than two hours in
the PS Series groups that are managed by VSM. VVol snapshots which are prepared but not
committed in PS Series groups are considered orphaned from ESXi.
Icon Function
Modifies the settings for the selected system schedule
Allows any schedule to be run immediately, consuming one of its retention count maximum values
Setting Description
Schedule date and time Specify:
• At a specific time and date. Dell recommends that you not use this option.
• On weekly schedule (all days, weekdays, weekend days, or custom)
• Frequency to run the schedule, for example, as every 8 hours
From and To Specify the starting and ending time to run the schedule. You can either type the time into the From
and To text boxes, or use the grippers to drag the slider to the times you want.
The gold highlighting indicates the time boundaries over which the schedule will operate on the
selected days. By default, the full day (midnight to the next midnight) is available to run the job. By
changing the limits, the scheduled job will start at the beginning time, and will be allowed to recur at
its user-defined interval until the end time is reached.
The end time is the limit, so it cannot be used to schedule the next running job. For example, a
schedule running every hour from 8 a.m. to 1 p.m. will run on each hour starting at 8 a.m., but will not
run at 1 p.m. because the limit is reached before it can be started. If a 1 p.m. run is also needed, the
end time could be specified as any time greater than 1 p.m. but less than 2:01 p.m., because that
would cause a 2 p.m. run to occur also.
Steps
1. Click VSM Home > Manage.
2. Click System Schedules.
The System Schedules table opens.
3. Initiate the Modify task by either of these methods:
NOTE: PS Series version 9.0 firmware provides cross-platform replication between PS Series arrays and Dell Storage
Centers. However, VSM version 5.0 does not support configuration of replication on a datastore to a Storage Center
partner. VSM supports replication to PS Series partners only.
When you select VSM Peers from the Manage tab on VSM Home, the VSM Peer Replication table is displayed, showing all the peers
that have been configured.
This page provides buttons to:
• Change the local VSM password required by VSM peers to communicate with the local VSM. See Modify a VSM Peer.
• Add a VSM peer. See Add a VSM Peer.
• Modify the configuration of a VSM peer. See Modify a VSM Peer.
• Delete a VSM peer. See Delete a VSM Peer.
Option Description
VSM Server IP address or fully-qualified domain name of the server to be used as a VSM peer
Access Password Password of the remote VSM server used to authenticate replication requests by its VSM peers
Description (Optional) Text string containing a custom description of the peer
Steps
1. Click VSM Home > Manage.
2. Click the VSM Peers tab.
The VSM Peer Replication table opens.
3. Click Add.
The Add VSM Peer dialog box opens
Steps
1. Click VSM Home > Manage.
2. Click the VSM Peers tab.
The VSM Peer Replication table opens.
3. Click Modify.
The VSM Peer Replication table opens.
4. Type the values for VSM Server, Access Password, and optionally, Description. These fields are described in Table 10. VSM Peers
Settings Options.
5. Click OK.
Steps
1. Click VSM Home > Manage.
2. Click the VSM Peers tab.
The VSM Peer Replication table opens.
3. From the table of VSM peers, right-click to select the peer to be deleted.
4. Click Delete.
The Delete VSM peer dialog box opens, with a warning that the action cannot be undone.
5. To confirm that you want to delete the VSM peer, click Yes.
Next steps
CAUTION: Deleting a VSM peer performs the following tasks:
The replicas still exist on the respective PS Series groups; however, VSM is no longer able to perform any replication
operations (such as failover and failback) using those replicas. Those operations need to be performed manually using
standard group and VMware administration.
Icon Description
The partner is not managed by the VSM server or by a peer VSM server.
The partnership between the two groups is incomplete and this group is not configured as a partner of the other.
The partnership with the host is not allowed because it is a Dell Storage Center.
Replication paused.
You can also access the Replication Partners table from the PS Groups table by clicking Manage > Partners.
This page provides buttons to perform the following actions:
• Create Replication Partnership
• Configure Destination Partner
• Update Partnership Configuration
• Remove a Replication Partnership
• Pause and Resume Replication
The following table describes the information required for creating and updating replication partnerships.
Description Item
Partner Identification
Source Partner Name of a group selected from the list to be used as the source partner for replication
Destination Partner Name of a group selected from the drop-down menu to be used as the destination partner for
replication
Delegated Space
Storage Pool (single-pool selection) If the group is running PS Series firmware version 7.x, the Storage Pool selection provides a
drop-down list, from which you can select one pool.
Storage Pool (multiple-pool If the group is running PS Series firmware version 8.0.x or later, the Storage Pool selection
selection) shows a list of available storage pools.
Select one or more pools from the available pools included in the list by selecting the checkbox
next to the pool name.
Size Amount of pool space to be delegated for storing replicas. Select units of megabytes, gigabytes,
or terabytes.
Group Information
Description Text string that describes the partner group
Registration Password Password to be used for validating replication operations
Contact Information
Name Account name for a user on the group to be used for validation of group operations
E-mail address Email address for the contact
Phone Telephone number for the contact
Mobile Mobile telephone number for the contact
Table 12. Replication Partnerships Options explains the information required for creating a partnership.
NOTE: VSM does not allow a replication partnership to be set up if a partial partnership has already been set up. For
example, if Group A has established Group B as a partner, but Group B has not established Group A as a partner, this
configuration is considered a partial setup.
1. Configure the source partner. The source partner is the group from which data is to be replicated.
2. Configure the destination partner. The destination partner is the group that will receive the replicated data.
Steps
1. Click VSM Home > Manage.
2. Click Replication Partners.
The Replication Partners table opens.
3. Click Create.
The Create Partnership wizard opens.
4. Select a source partner from the list.
5. Select one or more storage pools.
NOTE: The option to select more than one storage pool is available only on groups running PS Series firmware
version 8.0 or later. If the group is running PS Series firmware version 7.x, you can select only one storage pool.
6. For each pool selected, type a value for the size. Specify a unit of measurement.
When you enter the values for the storage pool, a chart of pool capacity is updated in the Delegated Reservation Information section
of the table. The values shown for New, Used, and Unused in Available Pool Capacity represent the consolidated values of all the pools
selected,
7. Type information in the Group Information fields.
8. Type information in the Contact Information fields.
9. Click OK to complete the task.
Steps
1. In the Create Partnership wizard, click Configure Destination Partner.
2. Type the information for Delegate Space, Group Information, and Contact Information, as described in Create Replication Partnership.
3. Click OK to complete the task.
Steps
1. To select the replication partnership to update, either:
• Select VSM Home > Manage and then click the Replication Partners tab.
• From PS Groups select the group on which the partnership is set up. Click Manage > Partners.
The Replication Partners list opens.
2. Select the replication partnership to update by clicking on its image.
3. Click Update.
Steps
1. Click VSM Home > Manage.
2. Click Replication Partners.
The Replication Partners table opens.
3. Select a source partner from the list.
4. Click Remove.
5. Click OK to complete the task. This operation results in all storage replicas between groups being deleted.
Steps
1. Click VSM Home > Manage.
2. Click Replication Partners.
The Replication Partners table opens.
3. Select the replication partner from the list for which you want to pause replication.
4. Click Pause.
Next steps
To resume replication between partners that had previously been paused:
1. From the Replication Partners table, select the paused replication.
2. Click Resume.
Steps
1. Click VSM Home > Manage.
2. Click vCenter Servers.
The vCenter Server table is displayed. It lists each vCenter server that has been configured, and also the following information for that
server:
• Version of the VMware software installed
• Fully-qualified domain name (FQDN) or IP address
• Status of the VSM connection to that vCenter server
Advanced Settings
Edit the Advanced settings in VSM.
Property Description
Sleep After Rescan Time (in seconds) that VSM should wait for the iSCSI rescan command to complete.
Use the arrows to select the number of seconds (from 5 to 300).
Sleep Before Register Time (in seconds) that VSM should wait before registering a restored VM. Use the
arrows to select the number of seconds (from 5 to 300).
Polling Retry Interval Time (in seconds) to allow between VSM and the vCenter server information poll
requests. Use the arrows to select the number of seconds (from 5 to 60).
Sleep After Storage Provider Sync Number of seconds that VSM should wait for a storage provider sync to complete
(from 5-300).
iSCSI Rescan Retry Count Number of retry attempts allowed when rescanning for new volumes (from 1 to 5).
Selective Restore Timeout Time (in seconds) that VSM should wait for the Selective Restore copy command to
complete. Use the arrows to select the number of seconds (from 600 to 86400).
Disk Space Threshold Percentage of disk space used before a warning alarm is triggered. Use the arrows to
select the amount (from 10 to 95 percent).
Capacity Warning Threshold Value used to trigger a color change to yellow in the utilization bar gauge. If the
utilization is greater than or equal to this value and less than the Capacity Error
Threshold value, the change triggers.
Capacity Error Threshold Value used to trigger a color change to red in the utilization bar gauge. If the utilization
is greater than or equal to this value, the change triggers.
Steps
1. Click VSM Home > Manage.
2. Click Advanced Settings > Edit.
3. Modify the values.
4. Click OK.
Port Service
Incoming
22 SSH access, if enabled
80 Web interface (optional)
139, 445 SMB server
443 Web interface, VSM API
8443 VASA provider
Outgoing
53 DNS server
80 vCenter
123 NTP server
443 vCenter, ESXi hosts, peer VSM servers
3003 PS Series groups
Topics:
• Running VSM in a VVol Environment
• Add VVol Access to a New ESXi Host in an Existing Cluster
Prerequisites
• For VSM version 5.0 or later, VVol support requires Dell EqualLogic PS Series version firmware 8.0.x and later, and VMware vSphere 6
and later. VVol functionality will be enabled after you update these software versions.
VVol Workflow
Figure 4. VVol Components in EqualLogic Environment illustrates the workflow between the components that enable you to use VVols on
your PS Series array.
The ESXi hosts communicate with the VASA provider, which is configured using VSM to establish the connections to the array.
Prerequisites
• For each ESXi server, configure the iSCSI adapter to point to the PS Series group.
• To install VSM, you must have the VMware Client Integration plug-in installed for vCenter. For additional information, see the VMware
documentation for the VMware Client Integration plug-in.
• Dell strongly recommends using a separate host or cluster for vCenter and VSM. Dell recommends not deploying VVol VMs on this
host or cluster, but deploying them on other hosts or clusters. While it is architecturally feasible to have them share a common host,
any host-based reboots to recover from vCenter, ESXi, or VSM anomalies would complicate application I/O to the storage system.
NOTE: You must perform these steps in this exact order to avoid problems.
Next steps
After completing these steps, you should be able to create (provision) VSM VVol datastores using the VSM Datastore wizard. See Create
VVol Datastore.
After having created the VVol datastore of the appropriate size, you can use the vCenter Web Client to create VVol virtual machines, or
migrate VMFS VMs to VVol-based storage.
NOTE: If you cannot create VVol datastores or VVol VMs on VVol datastores, it is likely that you did not follow all the
configuration steps. Possible causes might include (but not be limited to) the following conditions:
NOTE: if you experience timeouts related to powering on VVol VMs, a possible cause might be excessive I/O load on the
array or associated with the particular host.
The array will give I/O operations precedence over control plane operations. Review I/O latency with SAN HQ and
contact Dell support as needed.
When VVols have been successfully configured, you can perform VSM operations such as snapshots and restores on virtual machines
located on the VVol datastores.
Using the PS Series Group Manager, you can view VVol settings including protocol endpoints. While Group Manager also allows you to
manage some VVol settings, Dell strongly recommends that you use VSM.
NOTE: VM VVol mapping jobs might not be automatically refreshed in the Group Manager VMware VVols view. To
refresh the Group Manager VMware view, the Verify System schedule should be run manually using the Run Now action
to invoke the verify VVol VM mapping job. See Verify a Schedule.
Steps
1. From the inventory in vCenter, right-click the name of the datastore of the new host
2. Select Mount Datastore to Additional Hosts.
A table of hosts opens.
3. Select the host corresponding to the ESXI cluster.
Next steps
For any additional hosts intended for VVol use, the hosts must also have protocol endpoint access established, in addition to having the PS
Series group added as a dynamic target. You do not need to perform any VASA reregistration for new hosts.
Tab Description
Getting Started Provides an overview of the tasks, and shortcuts to running actions on groups
Objects Identifies contents of the group and the following information:
• Name of object
• IP address/FQDN
• Status
• Capacity
• Utilization
• Available
• Events
To filter the objects in the table, see Filter the Group Table.
NOTE: If the Objects list is empty, you must navigate to the Groups Getting Started tab to add one or more groups.
Steps
1. Click the arrow next to the filter box, then choose Select Columns.
2. Select or deselect the attributes you want.
3. Click OK.
Icon Function
Add a group. See Add PS Series Group Dialog Box.
The following table describes the data to be provided when you add a group.
Item Description
Group Name/IP PS Series group host name. Dell recommends you use either a fully-qualified domain name (FQDN) or
management IP address of the group.
VSM supports both IPv4 and IPv6 IP addresses.
After you set this value, you should not change it because VSM relies on this value being constant.
User name Account name for a user on the group to be used for validation of group Add/Edit operations.
Password Password of the user account. A password can consist of 3 to 16 visible ASCII case-sensitive characters.
Steps
1. Start the Add Group task by any one of the following methods:
Results
The new group is added to the Groups view.
Steps
1. Start the task by any one of the following methods:
Steps
1. Start the task by any one of the following methods:
Steps
1. Start the task by any one of the following methods:
Tab Description
Getting Started Provides an overview of the group’s tasks, and shortcuts to running actions on groups
Summary Provides group information and graphical summaries. See Group Summary View.
Monitor Provides status, alerts, statistics, and trending information about the group. See Group Monitor View.
Manage Allows you to set configuration values. See Group Manage Display.
Related Objects Provides information and actions for datastores. See Group Related Objects View.
Section/Portlet Description
Status Identifies connection status, group management IP address/FQDN, location, and description
configuration values
Group Members Provides an overview of the member status. It identifies the following columns:
• Name — Name of the member
• Type — Hardware member type
• Pool Name — Name of the pool in which the member is located
• Status — Last polled value of the member status field
• Firmware Version — Current member controller firmware version
Protocol Endpoints Connections NOTE: This portlet is displayed only if protocol endpoints have been configured.
Steps
Results
Tab Description
Settings Identifies the group name, IP address, and name of the group account. Clicking Update Credentials opens a
dialog box that allows you to modify the user name and password settings for the group.
Members A table that shows the following information about each member of the group:
• Type — Hardware member type
• Pool Name — Name of the pool the member is in
• Health — Operational health variable (on the array)
• Capacity — Total disk space capacity of member
• Free Space — Remaining disk space
• RAID — RAID policy used by the member
• # Disks — Number of physical disks and their type
• Status — Last polled value of the member status field
The Member Details pane provides the following information about the selected member:
• Total capacity
• Volume space
• Snapshot/Replica space
• Number of disks
• Number of connections
• Fimrware version
• Model number
• Serial number
• Service tag
• Disk type
• RAID policy
• Compression state
Identifes the volume compression for the member. The possible states include:
• Unknown
• Not started
• No capable hardware
• No capable RAID
• Running
• Suspended
Protocol Endpoints NOTE: This information is displayed only if protocol endpoints have been configured using
vCenter.
Identifies the following credential details for protocol endpoints that have been configured for hosts and
clusters:
• Hostname
• IQN
• IP address
To grant access to a host or cluster, click Allow.
See About Protocol Endpoints.
Indicator Description
All of the HBAs in the cluster have access to the PS Series group.
None of the HBAs in the cluster have access to the PS Series group.
At least one of the HBAs in the cluster does not have access to the PS Series group.
One of the hosts within the cluster does not have access to the group.
Steps
1. From PS Groups, select a group.
2. Click Manage > Protocol Endpoints.
The Clusters & Hosts column lists all clusters and hosts that have been configured for protocol endpoints. Any host or cluster that
currently is denied access is identified with the identifiers as described in Protocol Endpoint Indicators.
3. In the Credential Details pane, select a host or cluster.
4. Click Allow.
If the Allow operation is successful, the exclamation icon disappears from the HBA.
Steps
1. From PS Groups, select a group.
2. Click Manage > Protocol Endpoints.
The Clusters & Hosts column lists all clusters and hosts that have been configured for protocol endpoints. Any host or cluster that
currently has access enabled is identified with the identifiers as described in Protocol Endpoint Indicators.
3. In the Credential Details pane, select a host or cluster.
4. Click Remove.
In the VMware model, a datastore is a logical container that holds virtual machine files and other necessary files for virtual operations. With
VSM, you can create and manage your Dell datastores and datastore clusters.
NOTE: In the VMware environment, datastores can be created, monitored, and managed using the vSphere Web Client.
You use the same vSphere tools for all datastores that you add and manage in your Dell storage environment. For
instructions on using vSphere to create and manage datastores, see the VMware documentation and online help that
comes with the vSphere Web Client.
Topics:
• Navigating Datastores
• VSM Datastores Summary View and Actions
• Virtual Volume Operations and Restrictions
• VSM Datastore Actions
• Datastore Storage View
Navigating Datastores
The views and options for the VSM inventory of datastores depend on your selection within the Dell Inventory hierarchy:
• When you select Datastores from the VSM navigator, the content area shows a table of all datastores in this vCenter that reside on
volumes which belong to PS Series groups managed by this VSM.
From the Datastores Summary view, you can perform actions including creating a datastore, resizing a datastore, and deleting a
datastore. See VSM Datastores Summary View and Actions.
• If you then select an individual datastore within the datastores table, the content area shows several tabs with details for the selected
datastore, including a Dell VSM tab. See Datastore Storage View.
Refer to the VMware vSphere documentation for information about the information shown in the Details view.
48 Managing Datastores
• Snapshot Space Utilization
• Replication Status:
• Unknown
• Disabled
• In progress
• Ready
• Far end is down
• Authorization failure
• Complete
• Paused
• Remote resize failed
• Remote paused
• Partner paused local
• Failed
• Remote replication reserve low
• No more snaps allowed
• Remote replication reserve invalid
• Cancelling
• Pending data transfer
• Manual data transfer in progress
• Remote disallow down-grades not set
• Remote partner needs upgrade
• In sync
• Out of sync
• Out of sync (paused)
• Out of sync (snapshot reserve exhausted)
• Out of sync (member offline)
• Out of sync (SyncAlternate pool free space exhausted)
• Out of sync (alternate pool lost blocks)
• Replication Partner — Identifies the name of the replication partner, if replication has been configured
The Datastores summary view allows you to perform the actions on datastores described in Datastore Summary View.
Managing Datastores 49
VSM Datastore Actions
The following table explains the tasks available from the toolbar and the Actions menu in the Datastore top-level summary view.
Icon Function
Create a Dell datastore. See Create Dell Datastore Wizard.
Clone ACL from Volume. See Create ACL Template from Volume.
Option Description
Name, Type & Placement
Name Name to be assigned to the new datastore
Type Select the type:
• VMFS
• VMFS-3
• VMFS-5
• VMFS-6
• NFS
• VVOL
File System Block Size For the VMFS-3 type, select from a list of block sizes that can be applied:
• 1MB
• 2MB
• 4MB
• 8MB
50 Managing Datastores
Option Description
Inventory Location Select from the hierarchy to specify the inventory location for the datastore.
Hardware Resource
Hardware Resource Select from the hierarchy to specify the target resource pool, host, or cluster that uses the provisioned
datastores.
Storage Location & Size
PS Group Choose a group from the list to configure as the iSCSI target.
Storage pool Select the storage pool for datastore volumes.
Thin provisioned volumes Checkbox to be selected or deselected to specify if the provisioned datastore uses thin-provisioned
volumes.
NOTE: This option does not apply to NFS or VVol datastore creation.
Enable Thin Provision Stun Checkbox to be selected or deselected to enable the VMware thin provision stun feature. The thin
provision stun pauses virtual machines if a thin-provisioned volume runs out of space.
NOTE: This option does not apply to NFS or VVol datastore creation.
Number of datastores Select the number of new datastores to be created. Use the arrows to increase or decrease the
number.
Container Size Size of the datastore to be provisioned. You can choose units of MB, GB, or TB.
NOTE: The maximum container size for a VVol datastore is 4PB (petabytes) or the size of
the PS Series group pool size, whichever is smaller.
Snapshot Reserve The percentage of datastore volume size to be allocated for snapshot reserve.
NOTE: This option does not apply to VVol datastore creation.
Snapshot Reserve Warning The percentage of used snapshot reserve at which a warning should be issued.
NOTE: This option does not apply to VVol datastore creation.
Enable Snapshot Space Checkbox to be selected or deselected to enable the Snapshot Borrowing feature. See the Dell
Borrowing EqualLogic Group Manager Administrator's Guide for more information.
NOTE: This option does not apply to NFS or VVol datastore creation.
Access Policy
NOTE: The Access Policy options do not apply to VVol datastore creation.
IPv4 address mask The IPv4 address mask to be used to limit access.
NOTE: This option applies to the NFS datastore type only.
ACL Source Select the source for the access policy. Click either of these options:
• Auto-generate an ACL for the initiators in the resource pool
• Specify a unique ACL
Select an ACL If an ACL policy has been set previously, you can select it from the list by clicking the down arrow and
choosing from the existing ACLs.
NOTE: This option applies to the VMFS datastore type only.
Name A name for the new ACL if you choose to create a new one
NOTE: This option applies to the VMFS datastore type only.
Managing Datastores 51
Option Description
iSCSI Access Control Entries • Click Add to configure the CHAP user name, IP address, and iSCSI initiator values.
• Click Modify to make modifications to an existing ACL policy.
Click Remove to delete a selected ACL policy.
Snapshot Schedules
NOTE: The Snapshot Schedule options do not apply to VVol datastore creation.
Add Schedule ( ) Add a snapshot schedule. See Add Schedule/Edit Schedule Dialog Box.
Configure Replication Checkbox to be selected or deselected to enable replication on the datastore that is being created.
Local Reserve Size Percentage of disk space to be allocated for local reserve space.
Allow temporary use of free Checkbox to be selected or deselected to allow temporary use of free pool space for replication.
pool space
Keep failback snapshot Checkbox to be selected or deselected to keep the failback snapshot during replication.
Replication Partner Select from the list of replication partners that have been configured.
Remote Schedules Percentage of disk space to be used for remote reserve space.
Replication Schedules Table of any current replication schedules. You can create a new replication schedule, edit an existing
one, or delete a schedule.
Synchronous Replication
NOTE: The Synchronous Replication option does not apply to NFS or VVol datastore creation.
Configure Synchronous Checkbox to be selected or deselected to specify that synchronous replication should be used.
Replication
Steps
1. Initiate the Create Datastore wizard by one of these methods:
52 Managing Datastores
3. Select a datastore type: VMFS-3, VMFS-5 or VMFS-6.
If you select VMFS-3, choose a file system block size for the datastore from the list.
4. In the inventory location section, expand the hierarchy as necessary to specify an inventory location. Then click Next.
The next dialog box, Hardware Resource, opens.
5. Select from the inventory of Dell resource pools, hosts, or clusters to specify the resource that is using the new datastore. Then click
Next.
The next dialog box, Storage Location & Size, opens.
6. Select from the list of PS groups and storage pools.
a) Type the value for the number of datastores.
b) Type the value for container size.
c) Type the value for snapshot reserve.
d) Type the value for snapshot reserve warning.
e) Specify whether you want to create thin-provisioned volumes, enable thin provision stun, and enable snapshot borrowing space.
f) Click Next.
NOTE: For details about snapshot reserve, snapshot reserve warning, and snapshot borrowing, see the Dell
EqualLogic Group Manager Administrator's Guide.
The next dialog box, Access Policy, opens.
7. Select the option for ACL source:
• Auto-generation ACL for the initiators in the resource pool. If you choose this option, VSM auto-generates ACL records for host
initiators in the resource pool.
• Use the option to select a previously defined ACL policy from the list.
• To create an ACL policy, type a name and optionally a description for the ACL policy. Click Add to supply the iSCSI Access
Control Entries values. You can save the new ACL policy as a template by clicking Save as Template.
• To modify the values for an existing ACL policy, first select the ACL policy from the list, then change any of the values. Click
Modify to finish.
Click Next.
The Snapshot Schedule dialog box opens.
NOTE: If the volume of the datastore is created on Dell EqualLogic PS Series firmware version 7.0 or later, the ACL
associated with the volume on the PS group has a name with the prefix VSM” This ACL name can be shown from the
PS Series Group Manager.
8. (Optional) Create a new snapshot schedule for the datastore being created. You can also edit existing schedules or delete schedules.
For instructions, see About Snapshot Schedules. To continue, click Next.
The next dialog box, Replication, opens.
9. To continue without configuring replication, click Next.
To configure replication, select the Configure Replication checkbox.
• Keep the default value for Local reserve size or type a new value in the field.
• Select your options for Allow temporary use of free space and Keep failback snapshot.
• From the list of replication partners that have been set up, choose a replication partner.
• Keep the default value for remote reserve size or type a new value in the field.
• (Optional) Create a new replication schedule for the datastore being created. You can also edit existing schedules or delete
schedules. For instructions, see About Snapshot Schedules.
Click Finish to complete the replication configuration. To continue, click Next.
The Synchronous Replication dialog box opens.
10. To continue without configuring synchronous replication, click Next. To configure synchronous replication, click the Configure
Synchronous Replication checkbox.
a) From the table of alternate storage pools, select a storage pool.
b) Click Finish to complete the synchronous replication configuration
c) To continue, click Next.
The Ready to Complete screen shows all the settings that have been selected.
11. Click Finish.
The new datastore is then listed in the VSM datastores view.
Managing Datastores 53
Create NFS Datastore
When you have a Network Attached Storage (NAS) appliance connected for back-end storage, the NFS datastore option is available.
Steps
1. Initiate the Create Datastore wizard by one of these methods:
NOTE: VSM does not allow creation of a VVol datastore with the type thick-provisioned.
As each screen in the wizard is displayed, supply the requested information. This required information is described in Table 23. Create Dell
Datastore Options.
54 Managing Datastores
Steps
1. Initiate the Create Datastore wizard by one of these methods:
The maximum container size for a VVol datastore is 4PB (petabytes) or the size of the PS Series group pool size,
whichever is smaller.
c) Click Next.
The Ready to Complete screen shows all the settings that have been selected.
7. Click Finish.
The new datastore is then listed in the VSM datastores view.
Results
A datastore created with the VVol type is considered to be a storage container. If you use Group Manager, this type of datastore is
identified as a storage container.
For example: If a VMFS5 datastore current size is 2TB and available size of pool is 3TB, then it displays Maximum: 5TB
because it is less than the allowed size of 15TB.
The following table describes the information required when you run the wizard to resize a datastore volume.
Option Description
Volume Size Specify a value for the datastore volume. You can choose units of MB, GB, or
TB.
Snapshot Reserve Specify a value for the percentage of volume size.
Snapshot Reserve Warning Specify a value for the snapshot space warning as a percentage of the snapshot
reserve.
Managing Datastores 55
Option Description
Enable Snapshot Space Borrowing Checkbox that, if selected, specifies that snapshot space borrowing is enabled. If
this checkbox is deselected, indicate one of the following options for handling
any snapshots that are currently in borrowed space:
• Increase snapshot reserve and move the snapshots there
• Discard the snapshots
Storage Pool Capacity Graphic that shows the percentages of storage pool capacity.
Steps
1. Initiate the action by one of these methods:
Steps
1. Initiate the action by one of these methods:
• In the Datastores hierarchy, select a datastore, and on the Datastores Getting Started tab, click the Delete Datastore ( ) icon.
• In the hierarchy view, right-click the Datastore item, then click Delete.
A confirmation dialog box opens, reminding you that the operation will permanently destroy all files on the datastore.
2. Select the checkbox.
3. Click Yes.
56 Managing Datastores
Table 25. Apply ACL Template Dialog Box Options
Option Description
Select an ACL List of previously defined templates. Click the arrow to view any existing
templates. Select the ACL template to be applied from the list.
ACL
Name Name to be used for the ACL policy
Description (Optional) Text string that describes the ACL policy
iSCI Access Control Entries
Authenticate using CHAP user name Type a CHAP user name to be used for authentication.
Limit access by IP address Type an IP address or IP mask to be used to limit access.
Limit access by iSCSI initiator name Type the name of an iSCSI initiator to use to limit access.
Apply Template
Use VSM to apply an ACL to a single datastore.
Steps
1. Select a datastore in the Datastores table.
2. Initiate the Apply ACL action by one of these methods:
• Click Actions > Apply ACL.
• Right-click an object in the inventory, then select Apply ACL.
• Click the Apply ACL icon ( ) in the toolbar.
The Apply ACL dialog box opens.
3. Click the arrow next to Select an ACL to show the list of any previously defined templates. Click an ACL to select the ACL to be
applied.
The values defined for the selected ACL are displayed in the table.
4. To change any of the values, click Modify, then change the values for Name and Description. To add iSCSI access controls, click Add,
then fill in the values (see Table 25. Apply ACL Template Dialog Box Options). Click OK.
5. (Optional) Add a new policy from this dialog box by clicking Add and then filling in the values in the fields.
6. To save all changes, click OK.
Next steps
NOTE: If you modify an ACL policy associated with datastores, VSM does not apply the ACL automatically. You must
perform a manual rescan of the datastores to view the ACL policy modification. To perform the rescan action:
Steps
1. Display the Datastores table by first choosing Hosts/Clusters from the vSphere inventory, then click Configure > Dell VSM.
2. To select multiple datastores, click the first item, and press and hold down the Shift key, and then click the last item.
3. Initiate the Apply ACL action by one of these methods:
Managing Datastores 57
• Click Actions > Apply ACL.
• Right-click an object in the inventory, then select Apply ACL.
• Click the Apply ACL icon ( ) in the toolbar.
The Apply ACL dialog box opens.
4. Follow the instructions as described in Apply Template to complete the ACL policy.
Next steps
NOTE: If you modify an ACL policy associated with datastores, VSM does not apply the ACL automatically. Perform a
manual rescan of the datastores to view the ACL policy modification. To perform the rescan action:
Item Description
Volume Size Identifies the size of the volume that is chosen for replication
Local Reserve Size Specify a value between 5 and 200 percent to be used for local reserve space. The default is 100 percent.
Allow temporary use of Checkbox that, if selected, permits the replication operation to use free pool space temporarily
free pool space
Keep failback snapshot Checkbox that, if selected, instructs VSM to keep the failback snapshot when performing the replication
operation
Storage Pool Graphic representation of the reserved and free space on the volume that is chosen for replication
Replication Partner Name of a group selected from the drop-down menu to be used as the partner for replication
Remote Reserve Size Specify a value (in percentage) for reserve size on the replication partner. The minimum is 105 percent. The
default is 200 percent.
Delegated Space Graphic representation of the reserved and free space that is delegated on the replication partner
Replication Configuration
Use VSM to configure replication.
Steps
1. Initiate the action by either of these methods:
• Click Actions > Replication Configuration.
• Right-click the datastore volume and select Replication Configuration.
The Replication Configuration dialog box opens. The dialog box identifies the volume size of the datastore being replicated.
2. Specify a value for Local Reserve Size. The modification is reflected in the table of Storage pool space graphic.
3. (Optional) Choose whether you want the replication operation to allow temporary use of free pool space and whether a failback
snapshot should be kept.
4. Specify the replication partner by selecting from the menu.
58 Managing Datastores
5. Specify a value for remote reserve size.
6. Click OK to complete the replication configuration. Click Cancel to cancel the operation.
Deconfiguration Replication
Deconfiguring replication removes the replication partnership.
Steps
1. Initiate the action by any one of the following methods:
• Click Actions > Deconfigure Replication.
• Right-click the datastore volume and select Deconfigure Replication.
VSM displays a dialog box with a warning that deleting the replication configuration will stop the replication of the volume to the
partner, and will delete any replica sets on the partner that is associated with the volumes and any replicas.
2. Click Yes to continue, or click No to abort the procedure.
Steps
1. Click VSM Home > Manage.
2. Click Replication Partners.
The Replication Partners table opens.
3. Select the replication partner from the list for which you want to pause replication.
4. Click Pause.
Next steps
To resume replication between partners that had previously been paused:
1. From the Replication Partners table, select the paused replication.
2. Click Resume.
Managing Datastores 59
Steps
1. Right-click the Datastores item, then select Enable SyncRep.
A dialog box opens showing alternate storage pools.
2. From the list, select a datastore volume to be used as an alternate storage pool. The chart in the lower half of the dialog box identifies
the pool space properties of the destination storage pool.
3. Click OK.
Next steps
To disable synchronous replication (SyncRep) on a datastore volume:
• Right-click the Datastores item, then select Disable SyncRep.
• Acknowledge the operation.
NOTE: The action of disabling SyncRep might remove any volume snapshots. As a result, the Verify system schedule will
purge these snapshots from the VSM database. The process of removing snapshots from the database occurs in the
background Verify Snapshots job schedule.
Steps
1. Right-click the Datastores item, then select Pause SyncRep.
2. Confirm the action by clicking Yes in the dialog box.
Next steps
To resume synchronous replication (SyncRep) on a datastore volume:
• Right-click the Datastores item, then select Resume SyncRep.
• Confirm the action by clicking Yes in the dialog box.
Disconnect SyncActive
If the pool containing the SyncActive volume becomes unavailable to initiators, or communications between the SyncActive and
SyncAlternate are disrupted, you can restore volume connectivity by disconnecting the SyncActive volume and failing over to the
SyncAlternate.
Steps
1. Right-click the Datastores item, then select Disconnect SyncActive.
2. Confirm the action by clicking Yes in the dialog box.
Switch to SyncAlternate
The Switch to SyncAlternate command performs the SyncRep function of switching active volumes to the standby counterpart that had
previously been defined. This command is available if all volumes are currently in-sync
Steps
1. Right-click the Datastores item, then select Switch to SyncAlternate.
2. Confirm the action by clicking Yes in the dialog box.
60 Managing Datastores
Failover to SyncAlternate
The Failover to SyncAlternate command performs the SyncRep function of failing over active volumes to the standby counterpart that
had previously been defined. This command is available if all volumes are out-of-sync or paused.
Steps
1. Right-click the Datastores item, then select Failover to SyncAlternate.
2. Confirm the action by clicking Yes in the dialog box.
Tab Description
Getting Started Provides an overview of the tasks, and shortcuts for datastores
Summary Shows details and graphical summaries of the selected datastore. See Datastore Summary View.
Monitor Provides status on performance, tasks, events, reports, and other information for the selected
datastore. See Datastore Monitor View.
Configure Displays configuration options for the selected datastore. See Datastore Configure View.
Related Objects Provides information on virtual objects related to the selected datastore. See Datastore Related Objects
View.
Section/Portlet Description
Identification/Status Identifies the datastore type, URL, and capacity information
Details Lists the following information:
• Location of datastore
• File system type
• Number of hosts
• Number of virtual machines
Capacity Shows a graph of capacity and details of the following types of space:
• Used space
• Free space
• Total provisioned space
Tags Allows you to assign new tags to the datastore or detach tags that have previously been assigned.
See Datastore Summary Tags.
Storage Capabilities Identifies any system storage capabilities or user-defined storage capabilities
Managing Datastores 61
Table 29. Datastore Summary Tags
Field Description
Name Name to be assigned to the tag
Description Text string describing the tag
Category List of available categories to which the tag should be associated
For details about tags, see the VMware vSphere documentation and online help.
Item Description
Volume
Volume and Snapshot Space Identifies the following information for Volume Space Utilization:
• Volume name
• Access type (read-only, read/write)
• Volume type
• Reserved space
• Unreserved space
Identifies the following information for Snapshot Space Utilization:
• Space Recovery
62 Managing Datastores
Item Description
• Number of snapshots
• Borrowed
Resize action—Opens the Resize Datastore dialog box, allowing you to modify the volume size and
snapshot reserve. See Resize Dell Datastore Dialog Box.
Access Control List Identifies the details for the access control list that is associated with the datastore volume.
The toolbar provides access to these actions:
• Add an ACL
• Add cluster access
• Add host access
• Edit an ACL
See About ACL Templates.
iSCSI Connections Identifies the following information for iSCSI connections to the volume:
• Initiator address
• Connection Time
• Data Read—in MB or GB
• Data Written—in MB or GB
• Name of the iSCSI target
Protection
Snapshot Schedules Displays details for all existing snapshot schedules for the selected datastores.
Enables you to create a snapshot schedule, edit the schedule, or delete the schedule.
These actions are described in About Snapshot Schedules.
Replication Schedules Displays details for all existing replication schedules for the selected datastores.
Enables you to create a replication schedule, edit the schedule, or delete the schedule.
See About Snapshot Schedules.
Synchronous Replication Displays the status of any synchronous replication tasks in progress. Depending on the status, you can
select different actions.
These actions are described in SyncRep Operations for Datastore Volumes.
Recovery
Snapshots Identifies the following information for all snapshots of the selected datastore:
• Managed Object
• Creation Time
• Schedule
Actions enable you to create a snapshot or delete a snapshot.
Managing Datastores 63
Datastore Related Objects View
In the Datastore Storage view, when you click the Related Objects tab, the content area displays a view of virtual objects related to the
selected datastore. This display contains tabs for selecting the following objects:
• Virtual machines
• VM templates
• Hosts
For details about the items shown in the Monitor view, see the VMware vSphere documentation and online help.
64 Managing Datastores
9
Data Recovery
The Data Recovery item in the VSM navigator provides access to a view for searching VSM data protection managed objects, including
inbound and outbound replicas, storage recovery replicas, and snapshots. For an explanation of the types of replicas supported by VSM,
see Types of Replication Provided by VSM.
You can search managed objects by object name and type. When the search is complete, you can open the object to perform additional
tasks, such as restoring a virtual machine that has been deleted.
Topics:
• Structure of the Data Recovery Table
• Search VSM Managed Objects
Steps
1. Select Data Recovery from the VSM navigator panel.
The Data Recovery table opens.
2. Type all or part of the name of the object in the Managed Object Name field. You can use wildcards to filter the name.
3. Select the object type from the object menu.
4. Click Search.
The Search Results portion of the table lists the managed objects found as a result of the search operation.
5. To open an object, select its name in the table, then click Open.
The object and its related actions are shown in the table. The type of actions available depends on the object type:
• Inbound and outbound replicas and storage replicas — Actions include Delete, Delete All, Failover, Recover, and Clone. See About
Replication.
• Snapshots — Actions include Delete, Delete All, and Clone. See About Snapshots.
Data Recovery 65
10
Data Protection
About VSM Data Protection
The Dell Virtual Storage Manager for VMware provides more functions for data protection actions on folders, datastores, and virtual
machine-based snapshot and replication actions. When VSM is installed, the vCenter view in the vSphere Web Client includes:
• New Dell VSM actions on the context menus to perform snapshot and scheduling tasks
• A Dell VSM tab under the Configure tab. This view contains the VSM Data Protection hierarchy table.
These data protection functions are integrated into the VMware vSphere user interface to allow you to manage snapshots, clones, and
replicas of virtual objects consisting of your Dell storage.
Topics:
• VSM Data Protection Table
• About Snapshots
• About Snapshot Schedules
• About Clones
• About Replication
66 Data Protection
Figure 5. VSM Data Protection Hierarchy Table
About Snapshots
In the VMware virtual environment, a snapshot is a point-in-time copy of one or more VMware virtual objects.
The vSphere Web Client contains an action called Take Snapshot, which can be invoked by selecting an object in the vCenter hierarchy
and then choosing this action from the context menu. This action to take a snapshot is the default action for objects that do not include
Dell storage managed by VSM. When VSM is installed and you select an object managed by VSM, you can select the Create
Snapshot action, which appears only on VMs that are stored on datastores managed by VSM on Dell EqualLogic PS Series volumes.
VSM maintains a database of snapshots and verifies that the corresponding snapshots and replicas exist. You can optionally include a
virtual memory dump or include related objects in a snapshot.
Snapshot Actions
The following actions can be selected for VSM snapshots:
• Create snapshot. See Create Snapshot.
• Add schedule for a snapshot. See Add Schedule/Edit Schedule Dialog Box.
• Selective restore from a snapshot. See Selective Restore Snapshot.
• Rollback restore from a snapshot. See Rollback Restore of Snapshot Dialog Box.
• Delete a snapshot. See Delete Snapshot.
• Delete all snapshots. See Delete All Snapshots.
• Clone a volume from a snapshot. See Clone Volume from Snapshot.
• Clone a VVol VM from a snapshot. See Clone VVol VM from Snapshot.
Data Protection 67
VSM Schedule Keep Count and VM Max Snapshot Depth
When taking snapshots of VMs, VMware imposes a maximum snapshot depth of 32. This restriction includes snapshots taken through
VSM (either manually or using schedules) and snapshots taken from the VMware UI. When this limit is reached, snapshot creation for that
VM begins to fail. When configuring your keep count for VSM snapshot schedules on VVol VMs, be careful to set the keep count low
enough to avoid hitting the 32-snapshot limit. When taking snapshots, VSM takes the new snapshot before purging the oldest snapshot,
so a keep count of 10 means 11 snapshots exist for a brief time. If a VM is protected by multiple schedules, VSM attempts to maintain
several snapshots equal to the sum of their keep counts. A VSM schedule only removes snapshots taken by that schedule, so any
snapshots taken manually, or by another VSM schedule, are preserved.
VSM snapshots of VMFS VMs create only a single short-lived snapshot that is removed when the PS Series group snapshots are
completed. No matter how many VSM snapshots are retained of a VMFS VM, only this single, temporary snapshot counts towards max
snapshot depth, so it does not cause an issue unless many manual snapshots already exist.
Field Description
Managed Object Name of the virtual object for which the snapshot has been created. This column also includes an icon
indicating the type of object, for example, virtual machine, virtual machine folder, or datastore.
Snapshot Name Name of the VSM snapshot
Creation Time Time and date when the snapshot operation was run
Schedule Link to the schedule for the snapshot. Clicking an item in this column opens the snapshot schedules
view for the selected snapshot.
68 Data Protection
Table 32. Snapshot Action Toolbar Icons
Icon Function
Create snapshot. See Create Snapshot.
Planning Snapshots
To prepare for a VSM snapshot task:
• Review the status of the virtual infrastructure object by selecting it from the hierarchy and displaying its status in the information
panel.
• Ensure that the selected object has no active tasks.
• Ensure that enough snapshot reserve is available to maintain the number of snapshots you want to keep.
• VSM relies on iSCSI target volumes to have active connections to the volume from the virtual machine that has been selected for the
snapshot operation. If this connection is not present or is temporarily down, the volume will not be included in the snapshot.
• For snapshots on datastores:
• If the affected datastores are in a datastore cluster, VSM puts the cluster into manual mode during the snapshot operation. This
action applies to all datastores that have snapshots taken, including snapshots on a VM or VM folder.
• VSM attempts to skip datastores associated with a CD-ROM or ISO image on a virtual machine.
NOTE: In version 3.0 and later, VSM assumes that all operating systems can quiesce data (bring to a state suitable for
backups) except for the following operating systems:
• Microsoft Windows ME
• Microsoft Windows 98
• Microsoft Windows 95
Data Protection 69
Create Snapshot Dialog Box
When you create a snapshot of a VSM-managed virtual object, the Create Snapshot dialog box opens. The following table describes the
options in this dialog box.
Option Description
Include PS Series volumes accessed by guest Check this option to include the PS Series volumes in the snapshot.
iSCSI initiators
Perform virtual machine memory dump Check this option if you want to create a snapshot of the virtual memory of any virtual
machine included in the snapshot.
Ignore unsupported datastores Check this option to specify that any datastores that VSM does not support should be
ignored when performing the snapshot.
Create Snapshot
Create a Dell VSM snapshot using VSM.
Steps
1. Initiate the Create Snapshot task by one of the following methods:
• In vCenter, right-click the name of the virtual object in the inventory and select Create Snapshot.
• In vCenter, click the Configure tab, then the Dell VSM tab. Click the Create Snapshot icon ( ), and select Create Snapshot.
The Create Snapshot dialog box opens.
The Operation Summary section of the dialog box identifies the PS Series volumes that are supported for the operation and any
volumes that are excluded. If VSM detects any problems with the attempted operation, those problems are listed under Detected
Problems. Correct these problems before you can perform the snapshot operation.
2. (Optional) Select these additional tasks to perform as part of the snapshot task:
• Include PS Series volumes that are accessed by guest iSCSI initiators
• Perform a virtual machine memory dump
• Ignore unsupported datastores
3. To complete the task, click OK.
Results
VSM then performs the snapshot.
NOTE: Unless the Ignore unsupported datastores option has been selected, if VSM detects that unsupported datastores
exist, it stops the operation.
Delete Snapshot
Use VSM to delete a snapshot.
Steps
1. In vCenter, click Configure > Dell VSM to view the Data Protection Hierarchy table.
2. In the Recovery section, select the snapshot to delete.
3. Click the Delete icon ( ), or click Actions > Delete Snapshot.
VSM displays a dialog box with the following message: Deleting Snapshot cannot be undone. Continue with the
Delete Action?
4. Click Yes to delete the schedule, or click No to cancel the procedure.
70 Data Protection
Delete All Snapshots
Use VSM to delete all snapshots that are related to a specific virtual object.
Steps
1. In vCenter, click Configure > Dell VSM, then the tab to view the Data Protection Hierarchy table.
2. In the Recovery section, either right-click the object in the Managed Object column for which you want to delete all the snapshots and
select Delete All Snapshots, or click Actions > Delete All Snapshots.
VSM displays a dialog box with the following message: Deleting All Snapshots for the selected object cannot
be undone. Continue with the Delete Action?
3. Click Yes to delete the schedule, or click No to cancel the procedure.
If any VMs have been relocated to another datastore, the restore operation will first attempt to migrate these VMs back
to their original datastore
Before attempting the Restore operation, verify that all members of your network are accessible.
The wizard shows a list of all snapshot recovery points from which you can select to restore the VM’s state to that point in time. This list
includes recovery points that were not only taken from that VM itself, but any snapshot on any VMware inventory entity in that VM’s
hierarchy that contains a valid snapshot of that VM.
When you select the specific recovery point, all the VMs contained within that snapshot are also displayed in the Details panel. Because
the snapshot on the array is really of the volume, any VMs that are on that same volume will be included in the volume snapshot.
To view information in the Details panel, select the name of the virtual machine in the inventory shown in the wizard. The following table
describes the information shown in the Details panel for the selected virtual machine.
Field Description
Hard Disk Name of the disk
Original Datastore The datastore in which the VM was located when the snapshot was taken
Current Datastore The datastore in which the VM is currently located at the time of the restore operation
Restore To The datastore location which the restore operation will access
Data Protection 71
VSM restores to the original datastore even if the VM was moved to a different datastore (after the snapshot being restored from had
taken place). The datastores in the Restore To column will be the same as the Original Datastore, so the Restore To column will be the
same as the Original Datastore. If the original datastore has been removed, VSM will not able to restore it. If the datastore name is empty,
the datastore no longer exists.
Steps
1. Select the snapshot in the Managed Object column of the Snapshots table.
2. Initiate the task by one of these methods:
Steps
1. Select the snapshot in the Managed Object column of the Snapshots table.
The Restore Details portion of the table identifies the properties of the virtual machine and volumes associated with the snapshot.
72 Data Protection
The following table describes the information provided for snapshot schedules.
Field Description
Managed Object Name of the virtual object for which the snapshot schedule has been created. This column also
includes an icon indicating the type of object, for example, virtual machine, virtual machine folder, or
datastore.
Schedule Time and frequency defined for the schedule
Status Indicates whether the schedule is enabled or disabled
Last run Identifies the job status of the latest job created from the schedule:
• Never Run: The schedule has not yet been executed
• Successful: The most recent job completed successfully
• Complete with Error: The job completed, but errors were found during its execution
• Complete with To-do: The job completed, but users had one or more To Do items to complete
• Aborted: The job was aborted during its execution
Recovery Points Links to the recovery and snapshots pages for recovering virtual objects
Schedule Actions
When the scheduling table is selected within the Data Protection Hierarchy table, you can choose from a list of scheduling actions from
the toolbar. The following table describes the toolbar buttons.
Icon Function
Add a schedule. See Add Schedule/Edit Schedule Dialog Box.
Setting Description
Name A unique name to be associated with the schedule.
VSM treats schedule names as case insensitive; if you enter uppercase letters when specifying a
name, the name will be listed with lowercase letters.
Template Select a template from the list by clicking the down arrow to view any schedule templates.
VSM provides three default schedule templates that you can use and modify:
Data Protection 73
Setting Description
From and To Specify the starting and ending time to run the schedule, in half-hour increments. You can either type
numbers into the From and To text boxes, or use the grippers to drag the slider to the times you
want.
Retention Count Type a value for the maximum number of snapshots or replicas created from the schedule to be kept.
NOTE: Because of VMware’s hierachy snapshot count limitations, the retention count
of schedules of VVol VMs is limited to 31. For details about the hierarchy of snapshots,
refer to the VMware documentation.
Advanced Expand the Advanced settings to select the optional data you want to include in the snapshot:
• Include PS Series volumes accessed by guest iSCSI initiators
Check this option to include the PS series volumes in the snapshot.
• Perform a virtual machine memory dump
Check this option if you want to create a snapshot of the virtual memory of any virtual machine
included in the snapshot. This snapshot is necessary to fully recover virtual machines at a point in
time.
• Ignore unsupported datastores
Check this option to specify that any datastores that VSM does not support should be ignored
when performing the schedule.
Steps
1. In vCenter, select the name of the virtual object in the inventory and then click the Manage tab.
2. Under Protection on the left side, click Snapshot Schedules.
Th Snapshot Schedules view opens.
74 Data Protection
Edit Schedule
You can modify certain parameters of the snapshot schedules that you created previously.
Steps
1. In vCenter, click Configure → Dell VSM. Click the Edit icon ( ) or click Actions > Edit Schedule.
The Edit Schedule dialog box opens. The options are described in Table 37. Add Schedule Options.
2. Modify any of the schedule settings.
3. To complete the task, click OK.
Delete Schedule
Use VSM to delete a schedule.
You can use the VSM Schedules view to delete schedules for objects that have already been deleted from vSphere.
Remove these schedules because they fail to run.
Steps
1. In vCenter, click Configure > Dell VSM. Click the Delete icon ( ), or click Actions > Delete Schedule.
VSM displays a dialog box with the following message: Delete the schedule schedule_name?
2. Click OK to delete the schedule, or click Cancel to cancel the procedure.
Steps
1. If the schedule is enabled, the following message is displayed: Would you like to disable the schedule
schedule_name? Click Yes to disable the schedule, or click No to abort the procedure.
2. If the schedule is disabled, click the schedule you want to enable.
Data Protection 75
Run Now
The Run Now schedule action executes the action specified in the selected schedule immediately, rather than waiting for the time
specified in the schedule.
Steps
1. In the VSM Schedules table, click the schedule for the action to be run.
2. Click Actions > Run Now.
VSM opens a dialog box with the following message: Run schedule schedule_name?
3. Click OK to run the schedule, or click Cancel to abort the procedure.
Next steps
NOTE: VSM runs an event process for the Dell EqualLogic Group Manager that shows the correlation of VMs to VVols. In
some cases, the vCenter virtual machine-related event might not be correctly propagated to Group Manager. To
manually trigger a verification between VSM and Group Manager, select System Schedule > Verify > Verify Snaps and
Replicas > Run Now. This verification process does not run on automatic system schedules.
About Clones
VSM supports two types of clone operations:
• Clone Volume from Snapshot — Any snapshot that contains VMFS volumes offers this option. With this operation, the underlying
volumes are cloned and presented as new datastores. The VM files are accessible on the datastores, but are automatically registered
as new VMs only when cloning from a replica.
• Clone VVol from Snapshot — Any snapshot of a VVol VM offers this option. With this operation, VMware creates a new VM that is
equivalent to the state of the selected VM at the time the snapshot was taken.
When snapshots contain both VMFS volumes and VVol VMs, the options available depend where you are viewing the snapshot. Clone
Volumes from Snapshot is available all the time, but the Clone VVol VM From Snapshot option appears only on the individual
VVol VMs that can be cloned from the snapshot.
CAUTION: Be careful when registering and powering on cloned VMs, because the cloned VMs will have the same
network, storage, and application configuration as the original VM and might conflict or corrupt resources that are
shared unexpectedly.
NOTE: When cloning a VM that has disks on multiple datastores, VSM creates clones of all the necessary datastores,
but the VM configuration will have references to the original locations of the VMDKs used by the VM. If you register the
VM, your new VM will use the original VMDK files, not the cloned copies. It is recommended that you either connect to
the VMDKs from existing VMs to access the data that you need or create a new VM with the same configuration and add
the cloned VMDKs as existing hard disks.
Option Description
Name Suffix Name suffix assigned to the clone, which includes a timestamp. You can modify this name suffix.
Description (Optional) Description of the clone
Hardware Resource Select from the hierarchy to specify a cluster or resource pool on which to mount the cloned object.
ACL Source Select either:
• Auto-generate ACL for the initiators in the resource pool
• Specify an ACL from the list of available ACLs or create a new ACL using the table on this page of
the wizard
76 Data Protection
Option Description
ACL Creation Options
Name Name to be used for the new ACL
Description (Optional) Text string that describes the ACL
iSCI Access Control Entries
Authenticate using CHAP user Type a CHAP user name to be used for authentication.
name
Limit access by IP Address Type an IP address or IP mask to be used to limit access.
Limit access to iSCSI Initiator Type the name of the iSCSI initiator to be used to limit access.
Steps
1. In vCenter, click Configure > Dell VSM to view the Data Protection Hierarchy table.
2. Right-click the object to clone in the Managed Object column and select Clone Volume from Snapshot.
The Clone from Snapshot wizard opens.
3. (Optional) Modify the name suffix.
4. (Optional) Type a description for the clone.
5. From the hardware resource hierarchy, select either a cluster, host, or resource pool where you want to mount the cloned datastores.
6. Click Next.
The Access Policy page of the wizard opens.
7. Specify the access control list (ACL) policy for the clone, using one of these options:
• Autogenerate an ACL for the iSCSI initiators in the resource pool.
• Select an existing ACL from the list by clicking the down arrow on the select one list.
• Create an ACL by entering the fields for Name and Description, then click the Add button to specify iSCSI access control settings.
8. Click Next.
The Ready to Complete page of the wizard opens.
9. Click Finish.
Steps
1. In vCenter, click Configure > Dell VSM to view the Data Protection Hierarchy table.
2. Right-click the object to clone in the Managed Object column and select Clone VVOL VM from Snapshot.
The Clone VVol VM from Snapshot dialog box opens. A name suffix is provided with the format:
—clone-date-time
3. (Optional) Type a different value for the name suffix.
4. Click OK.
VSM runs the clone procedure. The cloned VM is shown in the Virtual Machines inventory in vCenter.
Data Protection 77
About Replication
The replication technology provided by the Dell EqualLogic PS Series firmware enables you to copy volume data from one group to
another, protecting the data from a variety of failures, with no effect on data availability or performance. Replication provides a method
for protecting volume data without setting the volumes offline, with the corresponding disruption to applications and users, and also
provides a disaster-recovery option in case the original group or volume is destroyed or unavailable. If a volume is destroyed, you can fail
over to the recovery group and recover data from a replica. Users can then resume access to the recovery volume. When the original
volume becomes available, you can fail back to the original group.
You can use PS Series replication functionality in conjunction with VSM. Using VSM, you can configure a replication partnership between
groups in a single action. VSM can create replicas of VMware objects that span multiple PS Series groups.
When replication partners are configured, you can create replicas and schedule replicas of virtual objects. Replicas can be used in failover,
failback, and restore operations.
For details on replication operations using Group Manager, see the Dell EqualLogic Group Manager Administrator's Guide.
78 Data Protection
Figure 6. Disaster Recovery Concepts
Callout Description
1 vCenter Server
2 VSM virtual appliance
3 Peer-to-peer relationship between VSM virtual appliances
4 PS Series groups
Snapshot replication requires cooperation between peer VSM servers. You configure a VSM peer that manages the replication partner
PS Series group.
To support replication between groups, you must establish a connection between your local instance of VSM and an instance of VSM
that is managing a secondary PS Series group.
VSM identifies replicas as Inbound (VSM is hosting replicas of volumes located on a remote site) or Outbound (VSM is replicating local
volumes to groups managed by a peer VSM). VSM shows a graphic (Figure 7. Replication Direction Graphic).
In this example, production-sitea is the primary site, replicating to production-siteb, the secondary site.
• Storage Recovery Replica — An intra-VSM replication operation, this type of operation can preserve a virtual machine state on a
secondary PS Series group within the same VSM virtual appliance (vCenter Server instance). Unlike the Disaster Recovery Replica
model, a Storage Recovery Replica does not require a second VSM peer appliance or an additional vCenter server. This type of
replication does not guarantee complete disaster recovery. However, it does provide these benefits:
• Preserves the virtual machine state on a secondary PS group using just one VSM and vCenter server
• Performs selective restore operations
Data Protection 79
Figure 8. Storage Recovery Replica Model
Callout Description
1 vCenter Server
2 VSM virtual appliance
3 PS Series groups
Replication Operations
The following figure shows the typical workflow for replication between the primary and secondary sites.
80 Data Protection
Figure 9. Replication Workflow
Callout Description
1 On the primary site, use the Create Replica task to initiate the VSM replication operation
2 Replication completed successfully
3 Failover
4 Replicate Back (optional)
5 Failback
6 Register Failback on the primary site
You create a replica on the VSM peer that is the primary site. In the VSM replication view, the status of the replication is identified. On the
secondary site, if the inbound replication completed successfully, you have these options:
• Failover — Temporarily hosts a replica set on the secondary site and moves its data from the primary site to the secondary site in the
event of a disaster on the primary site. See Failover Replica.
• Replicate Back — (Optional) Pushes changes from the recovery volume back to the original volume. See Replicate Back.
• Failback — Returns the datastore and its contents back to the primary site. After the failback operation, the datastore is removed
from the secondary site. See Failback Replica.
• Register Failback — Reloads the VM and registers any new VMs. Datastores and VMs are removed. This action is the last step on the
primary side. See Register Failback.
VSM provides command actions for each of these options.
NOTE: For Storage Recovery replicas, the actions are limited to Create Replica, Failover, Replicate Back, Failback, and
Selective Restore.
The following additional actions can be performed on replicas:
• Verify a replica schedule. See Verify a Schedule.
• Clone a replica. See Clone a Replica.
• Delete a replica. See Delete Replica.
• Delete all replicas. See Delete All Replicas.
The actions available within the replication recovery view depend on the state of the replication for the selected entity. The options in the
State column represent the state of the replica set and, depending on whether this site is the primary or secondary VSM, only a subset of
the states and actions are available. The following table describes the differences between the primary and secondary sides and the
various recovery states.
Data Protection 81
Table 39. Possible VSM Replication Actions
State Actions
Primary Side: State=Ready (Outbound replicating)
Ready, In-Progress Create, Delete, Delete All
Primary Side: State=Failed Back to Primary
Most recent replica = Failed Back to Primary Delete, Delete All, Register Failback
Secondary Side, State=Ready (Inbound Replicating)
Ready, In-Progress Delete, Delete All
Secondary Side, State=Replication Complete
Most recent replica = Replication Complete Failover
Secondary Side, State=Failover Done
Most recent replica = Failover Done, Replicated to Primary Failback, Replicate Back, Delete
Secondary Side, State=Failed Back
Most recent replica = Failed Back, All others = Inactive Delete
Many of the replication tasks can be invoked using an action icon in the toolbar. The set of icons varies depending on the replication state.
The following table describes the replication action icons.
Icon Function
Create replica. See Create Replica Dialog Box.
Option Description
Include PS Series volumes accessed by guest iSCSI Check this option to include the PS Series volumes in the replica.
initiators
Perform virtual machine memory dump Check this option if you want to create a replica of the virtual memory of any
virtual machine included in the replica.
Ignore unsupported datastores Check this option to specify that any datastores that VSM does not support
should be ignored when creating the replica.
82 Data Protection
The same requirements apply to deleting partners. If you remove one partner from Group Manager, you must also remove the other
partner from Group Manager.
Before configuring a replication partnership, you must perform the following tasks:
1. Using the Groups view, add the partner group to a VSM server.
• For disaster recovery replication, add the partner group to the peer VSM server.
• For storage recovery replication, add the partner group to the same local VSM server.
See Add a PS Series Group for instructions.
2. If you are establishing replication between two VSM peers:
a. Create an access password for each VSM peer in the VSM tab of the Configure VSM Properties dialog box. This task is a one-time
operation. See Edit VSM Setting.
b. From the VSM Peers view, add the VSM peer that manages the remote groups to which you want to replicate. This task is a one-
time operation.
Create a Replica
Use VSM to create a replica.
Steps
1. Initiate the Create Replica task by one of the following methods:
• From the Data Protection Hierarchy table, click the Create Replica icon ( ). For instructions on accessing this view, see VSM
Data Protection Table.
• In the VSM Datastores table, right-click the name of the datastore in the inventory and click All Dell VSM Actions > Create
Replica.
• After selecting replicas from Data Recovery Search, select the object from which to create a replica, then click the Create
Replica icon ( ).
The Create Replica wizard opens.
The Plan Details section of the wizard identifies the VM and PS Series volumes that are supported for the operation. If VSM detects
any problems with the attempted operation, those problems are listed under Plan Errors. You must correct these problems before you
can perform the replication operation.
2. (Optional) Select these additional tasks to perform as part of the replica task:
• Include PS Series volumes accessed by guest iSCSI initiators
• Perform a virtual machine memory dump
• Ignore unsupported datastores
3. To complete the task, click OK.
Results
VSM then initiates the replication operation.
Verify a Schedule
Use VSM to verify system schedules.
Data Protection 83
or a replica is missing all of its replicas, VSM removes the corresponding entry from it database. VSM creates an event for the VSM virtual
appliance for each snapshot and replica that the verify job removes from the database.
To ensure that replication states are synchronized, use the Verify System Schedule action to verify the replication schedule.
Verify Schedule is one of the system schedules available from the VSM Home workspace.
To run Verify System Schedule for snapshots and replicas:
Steps
1. From the VSM Home view, click Manage > System Schedules.
2. In the Schedules table, click Verify schedule.
3. Either right-click Verify schedule and select Run Now or click the Run Now icon ( ).
VSM displays a dialog box with the following message: Run system schedule Verify now?
4. Click OK.
Failover Replica
You can perform a failover operation on a replica whose state is “Ready.”
Steps
1. Display the table of replicas. You can use Data Recovery Search to specify a replica by name or to display all replicas by type. See
Search VSM Managed Objects.
2. From the table, select the replica to be failed over.
Replicate Back
You can perform a replicate back operation on a replica on the secondary site that has a state of “Failover Completed” or “Replicated to
Primary.”
Steps
1. Display the table of replicas. You can use Data Recovery Search to specify a replica by name or to display all replicas by type. See
Search VSM Managed Objects.
2. From the table, select the replica to be replicated back.
The Recovery Point Details table identifies the VM name, status of the snapshot (Yes, No), the datastore storage name, and the
source and destination for the replicate back operation.
84 Data Protection
4. Click Next.
The Groups page opens.
5. Enter the credentials (user name and password) for the selected peer group, then click Set Password. This step is required only in a
remote replication scenario.
6. Click Next.
The Ready to Complete page provides a summary of the operation.
7. To complete the operation, click Finish.
Failback Replica
You can perform a failback operation on a replica on the secondary site that has a state of “Failover Completed” or “Replicated to
Primary.”
Steps
1. Display the table of replicas. You can use Data Recovery Search to specify a replica by name or to display all replicas by type. See
Search VSM Managed Objects.
2. From the table, select the replica to be failed back.
Register Failback
The Register Failback operation reconnects the datastores and virtual machines that were hosted on the primary partner. If virtual
machines were added while the datastores were active on the second site, you will have the option of adding those to the inventory of the
primary site.
Steps
1. Display the table of replicas. You can use Data Recovery Search to specify a replica by name or to display all replicas by type. See
Search VSM Managed Objects.
2. From the table, select the object for which you want to register the failback.
The Recovery Point Details portion of the table identifies the related VM name, status of the VM snapshot (Yes, No), the datastore
storage name, and the source and destination peers.
3. Click Actions > Register Failback Virtual Machines.
The first page of the Register Failback wizard, New Virtual Machines, opens. This page identifies the VMs that were added after the
failover operation.
4. (Optional) To register the virtual machines as part of the failback, select the Register new virtual machines selection box, then click
Next.
The Inventory Location wizard opens.
5. From the inventory, select a filter, then click Next.
The Hardware Resource page opens.
6. Expand the hierarchy to select a cluster, host, or resource pool where the new virtual machines will run.
Data Protection 85
7. Click Next.
The Ready to Complete page provides a summary of the operation.
8. To complete the operation, click Finish.
Setting Description
Hardware Resource
Hardware Resource Select from the hierarchy to specify the cluster, host, or resource pool on which to mount the cloned
datastore.
Access Policy
ACL Source Select the source for the access policy. Click one option. You can either:
• Auto-generate an ACL for the initiators in the resource pool
• Specify a unique ACL
Select an ACL If an ACL policy has been set previously, you can select it from the list by clicking the down arrow and
choosing from the existing ACLs.
Name A name for the new ACL if you choose to create a new one
Description A description of the new ACL
iSCSI Access Control Entries • Click Add to configure the CHAP user name, IP address, and iSCSI initiator values.
• Click Modify to make modifications to an existing ACL policy.
• Click Remove to delete a selected ACL policy.
Clone a Replica
Use VSM to clone a replica.
Steps
1. Display the table of replicas. You can use Data Recovery Search to specify a replica by name or to display all replicas by type. See
Search VSM Managed Objects.
2. From the table, select the replica to be cloned.
86 Data Protection
Delete Replica
Use VSM to delete a replica.
Steps
1. Display the table of replicas. You can use Data Recovery Search to specify a replica by name or to display all replicas by type. See
Search VSM Managed Objects.
2. From the table, select the replica to be deleted.
3. Click the Delete Replica icon ( ).
VSM displays a dialog box with the following message: Deleting a recovery point for the selected managed
object cannot be undone. Continue with Delete Action?
4. To continue with the deletion, click Yes.
Steps
1. Display the table of replicas. You can use Data Recovery Search to specify a replica by name or to display all replicas by type. See
Search VSM Managed Objects.
2. From the table, select the replicas to be deleted.
Data Protection 87
11
VSM Schedules
When you select Schedules in the VSM navigator, you can view and manage snapshot and replication schedules that were created
previously.
VSM allows a schedule to have only one active job at a time. If the frequency of the schedule is too high, jobs might fail because a job for
that schedule is already running.
Topics:
• VSM Schedules View
• Filter the Schedules Table
Column Description
Name Name of schedule
Type Type of schedule (snapshot, replication)
Managed object Target object for the scheduled operation, such as a virtual machine or datastore
Schedule Current schedule time and frequency
Status Status of the most recent job associated with the schedule (enabled, disabled)
Last Run Result of the last run of the schedule (Success, Failure, Completed with Error)
Recovery Points Lists the number of recovery points for the operation and provides a hyperlink to the recovery points. By
clicking in this column, you open the VSM Data Protection Hierarchy table and can access additional actions.
See VSM Data Protection Table.
VSM privileges are required to perform scheduling actions. See Managing VSM Privileges.
Icon Function
Edit a schedule. See Edit Schedule.
88 VSM Schedules
Icon Function
Clear schedule filters. See Filter the Schedules Table.
Steps
Next steps
VSM Schedules 89
12
Managing Jobs
When you initiate an action or task, the task runs as a background activity. You can monitor the progress of the task in the Jobs view.
Typical results of tasks include:
• Error states, including error messages, resulting from a failed task. These messages help you to identify where a task might be failing.
• Any additional tasks required by the user. Several manual tasks might be required as a result of complex procedures such as recovering
virtual objects from a replica. The task execution report helps to guide you through the procedure.
• List of restored volumes
• List of restored virtual machines
• List of rolled-back snapshots
Topics:
• Jobs View
• Filter Job Listing
• Getting Job Details
Jobs View
When you select Jobs from the VSM navigator, the content area shows a table of all jobs related to VSM actions. The top pane of the
table lists all jobs. If you click a job in the table, the bottom pane shows details for that job.
Information included in the top pane includes:
• Name
• Status
• Queued time
• Start time
• Duration
• Completion time
NOTE: VSM does update the Jobs view automatically. To update the Jobs view, click the Rescan button ( ) in the
vSphere Web Client toolbar.
Steps
90 Managing Jobs
• Name — Type all or part of a text string, then click Enter.
• State — Select from the list of states.
• Start Time — Click the calendar icon ( ) to select the date range to use as a search criteria. You can specify:
• On or after a specific date
• On or before a specific date
NOTE: The Start Time filter can be used to filter by specific dates. This filter does not allow you to search for
specific times.
The table then displays schedules matching the filters.
Field Description
Job Description of the job
Status Whether the job was successful or not. If unsuccessful, error details are provided in the
Task Information pane.
Start Time The local system clock time when the job started
Duration The amount of time the job took to run
Completion Time The local system clock time when the job ended
Details Displays information on a selected job:
• The type of task and its status (failure, success)
• Information about the success or failure of the task within the job
• Relevant error messages in the event of a failure
• Listing of any additional tasks required to complete the job. Manual tasks might be
required to complete complex procedures such as recovering virtual objects from a
replica. The task execution report helps to guide you through the manual tasks.
• Describes virtual objects and objects (such as snapshots) that were used or created
in the task
Managing Jobs 91
13
Templates
VSM provides two types of templates for you to use when you create or modify virtual objects:
• Access control list (ACL) templates, which can be applied to objects to define the related permissions.
• Schedule templates, which can be used when creating new snapshot or replication schedules.
Topics:
• About ACL Templates
• About Schedule Templates
NOTE: The actions to add an ACL for a host or a cluster are available from the VSM Data Protection table only.
Icon Function
Create ACL template. See Create ACL Template.
The following table describes the options that can be set when you create or modify an ACL template.
Option Description
Authenticate using CHAP user name Type a CHAP user name to be used for authentication.
Limit access by IP Address Type an IP address or IP mask to be used to limit access.
Limit access by iSCSI initiator name Type the name of an iSCSI initiator to use to limit access.
92 Templates
Create ACL Template
Use VSM to create an ACL template.
Steps
1. To initiate the Create ACL Template action, either:
Results
The new template and its values are shown in the table.
Steps
1. To initiate the Modify ACL Template action, either:
Results
The revised template and its values are listed in the table.
Steps
1. To initiate the Apply ACL action, either:
• Click Actions > Clone ACL Template.
Templates 93
• Right-click a template in the ACL Templates table, then select Clone ACL Template.
The Clone ACL Template dialog box opens.
2. Click the arrow next to the templates.
3. Change the values for Name and Description. To add iSCSI access controls, click Add, then fill in the values (see Table 47. iSCSI
Access Control Entry Options). Click OK.
4. To save all changes, click OK.
5. To complete the operation, click OK.
Results
The new template and its values are listed in the table.
Steps
1. To initiate the Delete ACL Template action, either:
• Click Actions > Delete ACL Template.
• Click the Delete ACL Template icon ( ) in the toolbar.
• Right-click a template in the ACL Templates table and select Delete ACL Template.
A warning dialog box opens.
2. Click Yes to confirm the deletion.
Steps
1. From vCenter, view Hosts.
vCenter shows a table of all hosts.
2. Select a host by clicking its name.
3. Click the Dell VSM button.
The VSM Data Protection table opens.
4. Select a datatore.
5. Click Access Control List.
A table of all currently defined ACLs opens.
Steps
1. From vCenter, view Clusters.
vCenter shows a table of all ACLs.
2. Select a host by clicking its name.
3. Click the Dell VSM button.
The VSM Data Protection table opens.
94 Templates
4. Select a datatore,
5. Click Access Control List.
A table of all currently defined ACLs opens.
Steps
1. From the VSM datastores table, select the datastore from which to create the ACL template.
2. To initiate the action, either:
• Click Actions > Clone ACL from volume.
• Right-click a datastore in the table, then select Clone ACL from volume.
The Create ACL Template dialog box opens.
3. Type a name for the new template in the Name field.
4. (Optional) Type a description in the Description field.
5. Click the Add button to specify iSCSI access control entry options.
The iSCSI Access Control Entry dialog box opens.
6. Type the values for the type of access selected (see ACL Templates Dialog Box), then click OK.
7. To save the template, click OK.
Results
The new template and its values are shown in the ACL templates table.
Icon Function
Create a schedule template. See Add a Schedule Template.
Templates 95
Table 49. Edit Schedule Template Options
Setting Description
Name A unique name for the schedule template.
NOTE: VSM treats schedule names as case insensitive; if you enter uppercase letters
when specifying a name, the name will be listed with lowercase letters.
From and To Specify the starting and ending time to run the schedule, in half-hour increments. You can either type
numbers into the From and To text boxes, or use the grippers to drag the slider to the times you
want.
Keep Count Type a value for the maximum number of snapshots or replicas created from the schedule to be kept.
Advanced Expand the Advanced settings to select the optional data you want to include in the snapshot:
• Include PS Series volumes accessed by guest iSCSI initiators
Check this option to include the PS series volumes in the snapshot.
• Perform a virtual machine memory dump
Check this option if you want to create a snapshot of the virtual memory of any virtual machine
included in the snapshot. This action is necessary to fully recover virtual machines at a point in
time.
• Ignore unsupported datastores
Check this option to exclude datastores that are not supported by Dell from the snapshot or
replica operation.
Steps
1. From the VSM navigator, select Schedule Template.
The Schedule Template table opens in the content area.
Steps
1. In the Schedule Templates table, click the Edit icon ( ), or click Actions > Edit Schedule Template.
The Edit Schedule Template dialog box opens. The options are described in Edit Schedule Template Dialog Box.
2. Modify any of the schedule settings.
96 Templates
3. To complete the task, click OK.
NOTE: Consider keeping schedule templates for future schedules that you require.
Steps
1. In the Schedule Templates table, click the Delete icon ( ), or click Actions > Delete Schedule Template.
VSM displays a dialog box with the following message: Delete schedule template schedule_name?
2. Click OK to delete the schedule template, or click Cancel to abort the procedure.
Templates 97
14
Managing VSM Privileges
VSM uses the VMware vSphere model for user authentication and role-based security. A selected user or group can have different role
privileges on each VMware entity. The vCenter server gives access to objects, such as datastores or datastore folders, only to users who
have assigned privileges.
vCenter has a set of standard privileges that an administrator can manage. VSM provides security control by extending the VMware
vSphere security model for user authorization with permissions and roles on VSM-managed objects. VSM includes its own set of VSM-
specific privileges that are added to vCenter during installation of VSM. Figure 10. VSM Privileges Within vCenter shows an example of the
Dell Virtual Storage Manager privileges from the vCenter Role Manager.
See Privileges for VSM Operations for a complete list of VSM privileges.
Host Cluster
Resource Pool
Datastore Cluster
Datastore Folder
Datastore Cluster
1 VSM verifies the privilege on the object that is the parent of the datastore that is being created or configured.
Modify Replication Partner Modify Replication Partner vCenter Server vCenter Server
Deconfigure Replication Partner Deconfigure Replication vCenter Server vCenter Server
Partner
Change Password for VSM Peers Configure VSM Peering Secret vCenter Server vCenter Server
Replication Failback Failback a replica vCenter Server vCenter Server
Replication Failover (Storage Failover a replica Datastore Datastore
Recovery)
Datastore Folder Datastore Folder
Datastore Cluster Datastore Cluster
Register VMs after failback Register the VMs after failback Datastore Datastore
of a replica
Datastore Folder Datastore Folder
Datastore Cluster Datastore Cluster
Replicate a replica back Replicate back a replica vCenter Server vCenter Server
View VSM Peer View Peer VSM vCenter Server vCenter Server
View Replication Partners View Replication Partners vCenter Server vCenter Server
VM Folder VM Folder
Datastore Datastore
Datastore Folder Datastore Folder
Datastore Cluster Datastore Cluster
Restore VM from Snapshot 2 Restore VM from Snapshot/ Virtual Machine Virtual Machine
Replica
VM Folder Datastore
Datastore
Datastore Folder
Datastore Cluster
1For the Delete Snapshot operation, VSM checks the operation permission on the object at the root of the snapshot if it exists locally. If
the object existed, but has been deleted, VSM checks the operation permission on the object on the vCenter Server.
2 If the VM being restored still exists in the inventory, VSM checks the privilege on the VM. If the VM has been deleted and the Restore
operation is creating it, VSM checks the privilege on the set of datastores on which the VM will be created.
3 Rollback is checked on the datastores being rolled back.
Verify Replica State Verify Snapshot/Replica state vCenter Server vCenter Server
View Replicas View Snapshot/Replicas vCenter Server vCenter Server
replica is inbound, then VSM checks the privilege on the vCenter Server.
2 If the VM being restored still exists in the inventory, VSM checks the privilege on the VM. If the VM has been deleted and the Restore
operation is creating it, VSM checks the privilege on the set of datastores on which the VM will be created.
1 If the object that the schedule refers to no longer exists, it can be deleted by any user. No privileges are checked.
1 If the object that the schedule refers to no longer exists, it can be deleted by any user. No privileges are checked.
Datastore Folder
Datastore Cluster
Clone ACL Policy from Volume View EQL Volumes vCenter Server vCenter Server
Add/Modify/Delete ACL for View EQL Volumes vCenter Server vCenter Server
Volume
Modify Datastore Datastore Datastore
Datastore Folder
Datastore Cluster
Add Host/Cluster Access for View EQL Volumes vCenter Server vCenter Server
Volume
Create ACL Template
Datastore Folder
Datastore Cluster
Steps
1. Create the role “VSM Views.” This role should have the following VMware and VSM privileges:
• View PS Group
• View VSM Jobs and Tasks
2. Create the role “Datastore Operator.” This role should have the following VMware and VSM privileges:
• VMware Datastore/Move Datastore
• Provision Datastore
• Modify Datastore
• Delete Datastore
• Specify ACL
• Configure SyncRep on Datastore (optional)
• Configure Replication on Datastore (optional)
3. Create the user “Patricia,” if not already defined.
4. Access the vCenter server object and add the permission for the user “Patricia” with the role of “VSM Views.”
5. Create a storage folder “My Folder” and add the permission for the user “Patricia” with the role of “Datastore Operator.” The role
should be configured to “Propagate to children.”
Results
After performing these steps, the user “Patricia” will have all the required permissions to perform VSM datastore operations in “My
Folder.”
As a workaround, Dell recommends that you deploy the OVF template on a datastore that is not in a folder.
Troubleshooting 107
Virtual Appliance and Virtual Center Connectivity
In some situations, if the VSM virtual appliance is not on the same domain name as the vCenter server, the value entered for the VSM
server might not be recognized if a short form of a name is entered. You should enter a fully-qualified domain name (FQDN) in the VSM
server field to avoid this problem.
Scheduling Issues
Depending on your locale, if a time-change savings time event occurs (for example, if the time is set ahead or back) it could prevent a
schedule from being run, or delay it from running by 1 hour. Carefully consider the implications of creating schedules that trigger between
midnight and 3:00 a.m.
After the time zone in which the VSM Server is running shifts from Standard Time to Daylight Saving Time, or shifts back from Daylight
Saving Time to Standard Time, shutting down and restarting the VSM Server will change the behavior of schedules.
After a Daylight Saving Time shift, all existing system and user-defined schedules are adjusted to run at the same hour in Daylight Saving
Time. For example, if a schedule was to run at 2:00 a.m. every day, it continues to run at 2:00 a.m. every day. In the user interface (UI),
however, displayed user-defined schedule run times are shifted by an hour, so that, for example, if before the Daylight Saving shift the UI
displayed that a schedule will run at 2:00 a.m., after the shift the UI displays that the schedule runs at 3:00 a.m. (The actual run time
depends on whether the server has been restarted. This problem does not apply to new user-defined schedules created after the shift;
they run and are displayed as expected.
Restarting the server now shifts by an hour the time of day when user-defined schedules created before the Daylight Saving shift runs.
For example, if before the Daylight Saving shift a schedule ran at 2:00 a.m, after the server is restarted that schedule runs at 3:00 a.m,
which now matches what is displayed in the UI. System schedules, and user-defined schedules that were created after the shift, are not
affected by restarting the server.
108 Troubleshooting
Data Protection Issues
Maximum Snapshots Limit Exceeded
If you take a snapshot of a VM folder consisting of multiple VMFS VMs, and any one VM's snapshots exceeds the maximum limit in the
snapshot hierarchy, failures for other VM snapshots could occur, but might not be reported. Consider the following scenario:
1. Take a snapshot of all VMs that are powered on and able to be quiesced using the VMware tools. Failures of VMs on VMFS storage is
reported, but are not fatal. Failures of VVol VMs are fatal and cause the Create VSM Snapshot job to fail.
2. Take a snapshot of each PS Series group volume one at a time. Any failure aborts the remainder of the task and causes the Create
VSM Snapshot job to fail.
All VMFS VM snapshots taken in step 1 are removed.
Any volumes that had snapshots taken successfully prior to the failure will have a snapshot visible in Group Manager and the snap is
reported as an "Unmanaged snapshot" by the Verify job.
If a snapshot contains VVol and VMFS storage, snapshots of the VVol VMs are taken first. Snapshots of PS Series group volumes are
taken second. So, if a VVol VM snapshot fails, no volume snapshots are attempted. If a volume snapshot fails, all the VVol VM snapshots
that were already taken remain.
Replication Issues
Replica Is Deleted After Failback From Replica
If a restore by rollback fails, you should demote all promoted replica sets and rerun the restore. When VSM detects that replication has
paused, it then starts a 90-minute timeout, allowing you time to rectify the situation. The job status will be updated to reflect that
replication has paused or failed. You should selectively restore these virtual machines.
When performing a Restore operation, make sure you have the resources to replicate back.
Troubleshooting 109
Group Management Issues
Adding a Group Fails If Either FQDN or Group IP Address
or Management Address Is Used
The task of adding a group could fail with the following error: Not a valid group IP for group connection.
This error condition could be due to a variety of factors, including:
• An incorrect Group or Management IP address. Be sure to use the Management IP address or Group IP address and not an address
from an eth port of a member.
• If the group is behind a Network Address Translation (NAT) router using IP Mapping, instead of using the Group or Management IP
address, use the address that is mapped to the Group or Management IP address through the NAT.
Multipathing Recommendation
If you are not using the Dell EqualLogic Multipathing Extension Module (MEM), Dell suggests you run the following rule on your ESXi
nodes. To assist in round-robin I/O efficiency, after running this rule, reboot the nodes.
See the following Dell Tech Center document for additional best practices for implementing vSphere in a Dell EqualLogic environment:
http://en.community.dell.com/techcenter/extras/m/white_papers/20434601/download.aspx
110 Troubleshooting
Index
A definitions 9
delegated reservation information 31
access control 92–94 delete a schedule 75
ACL delete all replicas 87
applying 57 delete replica 87
applying to a cluster 94 deploying the virtual appliance
applying to a host 94 procedures 13
applying to multiple dastastores 58 diagnostics 20
specifying during datastore creation 51 disk format for virtual machines 12
ACL template documentation
creating 93 VMware 99
deleting 94 VSM 7
modifying 93
active volume 9, 59
add a group 41
E
adding a group failure 110 error states 90
advanced VSM Server settings 32 events
alerts 43 filtering 43, 90
viewing 43, 90
B
BackupDB
F
default schedule time 26 failback replica 85
failover replica 84
C failover to SyncAlternate 61
filtering objects 40
Capacity Error Threshold 32 firmware requirements 10
Capacity Warning Threshold 32 FQDN 12, 32, 40–42
CIFS share 18 fully-qualified domain name, See FQDN
CLI menu 17
clone
replica 86
G
volume from snapshot 76, 77 group
VVol VM from snapshot 77 adding 41
compression 45 filtering objects 40
console 17 operations 39
console CLI credentials 18 removing 42
create replica 83 unmanaging 42
create snapshot 70 update credentials 41
Group Manager
D launching 42
guest iSCSI volumes 71
database operations
back up 19
restore 19
H
datastore type 50 help
datastores VSM online 7
capacity 55 host name
creating 52 requirements 12
deleting 56
managing 62
monitoring 62 I
related objects 64
installation
rollback 71
drive capacity requirement 10
tags 61
memory requirement 10
tasks 48
prerequisites 10
volume resizing 55
procedure for new installation 13
daylight saving time 108
update 14
deconfigure replication 59
verifying 16
default gateway 14
J replicas (continued)
delete 87
job history 90 delete all 87
jobs failback 85
filtering 43, 90 failover 84
viewing 43, 90 replicate back 84
replicate back replica 84
replication
M configuration 58
maintenance CLI options 18 configuring partner 31
management network 14 creating replicas 83
MEM 10, 110 deconfigure 59
multipathing recommendation 110 limitations 80
pausing 32, 59
problems 109
N resuming 32, 59
replication partner
NAS 39
deleting 32
netmask
modifying configuration 31
for management network 14
report
Network Attached Storage, See NAS
error states 90
network mapping 12
resize datastore volumes 55
NFS 50
restore
NFS datastre
by rollback 71
creating 54
selective 71
NTP server 14
restore from snapshot 71, 72
restoring a database 19
O resume replication 32, 59
Role Manager 98
online help 7 roles
OVA file 13 managing 99
rollback restore from snapshot 72
P rollback the datastores 71
root password 18
password for VSM appliance 18
peer
maximum number of peers 28
S
permissions 99 schedule
ports 33 BackupDB 26
privileges deleting 75
assigning 99 disabling 75
VSM 100 editing 75
protocol endpoints enabling 75
allow access to group 46 monitor 26
definition 35 purge 26
indicators 45 run now 76
information about 43, 45 snapshot 73
remove access to group 46 time zone issues 108
Purge 26 schedule template
defaults 73, 95
Q editing 96
security concepts 99
quiescable operating systems 69 selective restore 71
snapshot
best practices 67
R cloning from 76
recent tasks 91 cloning volume from 77
recovery point 88 creating 70
related documentation 7 deleting 70
remove a group 42 deleting all 71
remove VSM appliance 16 planning 69
replicas restoring from 71, 72
clone 86 restrictions on datastores 69
creating 83 restrictions on VMs and VM folders 69
snapshot (continued) virtual appliance
rollback restore 71, 72 removing 18
selective restore 71 unregistering 18
snapshot reserve virtual volume, See VVol
warning 55 VMFS 50
snapshot schedule volume compression 45
time setting 27, 74, 96 volumes
snapshot space borrowing 51, 56 guest iSCSI 71
SSH access 18 VSM peer
standby volume 9, 59 configuring 29
storage awareness 8 VSM Server
storage containers 35, 43, 49, 55, 66 appliance 23
Storage Health 23 VVol
storage network actions permitted on datastores 49
editing settings 26 datastore 50
storage pool definition 9
multiple pool selection 30 restrictions 49, 78
storage pool capacity 56 support 8
storage providers 18 using VSM to set up 36
storage utilization 43 vCenter environment prerequisites 36
switch to SyncAlternate 60 VVol datastores
SyncActive creating 54
disconnecting 60
synchronous replication, See SyncRep
SyncRep
disabling on datastore volumes 60
enabling on datastore volumes 59, 60
failover to SyncAlternate 61
pausing on datastore volumes 60
resuming on datastore volumes 60
switch to SyncAlternate 60
system schedules
modifying 28
run now 76
verify 83
T
tags 61
terminology 9
thin provision stun 51
time zone 14, 108
troubleshooting
data protection 109
installation 107
replication 109
U
update appliance 14
user name for VSM appliance 18
V
VASA provider
configuration 18
definition 34
vCenter Server
authentication problems 107
connectivity problems 107
setting 11
view 32
verify snapshots and replicas 83
verify system schedule 27, 37, 83