Dell AX4-5 Specifications Page 47

  • Download
  • Add to my manuals
  • Print
  • Page
    / 58
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 46
Configuring SnapView snapshots for SRM testing purposes via NaviSecCli
1. Add the LUNs bound for SnapView Sessions into the Reserved LUN Pool.
naviseccli –h SP ipaddress reserved –lunpool –addlun <LUN IDS separated by spaces>
2. Create a snapshot for each LUN at the recovery site, and add the SnapShot to ESX Server’s
CLARiiON Storage Group at the recovery site.
(
NOTE: This snapshot will not be activated until a user tests the SRM failover operation, in which SRM
will create a session and activate it with the corresponding snapshot.)
naviseccli –h SP ipaddress snapview –createsnapshot <LUN ID>
-snapshotname VMWARE_SRM_SNAP
1
_LUNID
naviseccli –h SP ipaddress storagegroup –addsnapshot –gname <ESX CLARiiON Storage
Group name> -snapshotname <name of snapshot>
For more information about using Navisphere CLI with MirrorView, please see the
MirrorView/Synchronous Command Line Interface (CLI) Reference, MirrorView/Asynchronous Command
Line Interface (CLI) Reference and SnapView Command Line Interface (CLI) References available on
Powerlink.
EMC recommends that you configure SRM and the CLARiiON MirrorView Adapter with vCenter
Infrastructure after the mirrors and consistency groups have been configured. Refer to the VMware SRM
Administration Guide along with the EMC MirrorView Adapter for VMware Site Recovery Manager
Version 1.3 Release Notes for installation and configuration instructions.
SRM Protection Groups
A Protection Group specifies the items you want to transition to the recovery site in the event of a disaster.
A Protection Group may specify things such as virtual machines (VMs), resource pools, datastores, and
networks. Protection Groups are created at the primary site. Depending on what the SRM will be
protecting, you can define the Protection Group using VMs or based on the application being protected (for
example, distributed application across multi-VMs). Usually there is a 1-to-1 mapping between a SRM
Protection Group and a CLARiiON consistency group. However, if your CLARiiON model does not
support the number of devices being protected within a Protection Group, you can create multiple
CLARiiON consistency groups for each Protection Group.
Table 5 shows the maximum number of devices allowed per consistency group.
Table 5. Maximum number of sync mirrors and consistency groups
Parameter CX4-120 CX4-240
CX4-480 CX4-960
Total mirrors per storage
system
128 256 512 512
Total mirrors per consistency
group
32 32 64 64
Total consistency groups per
storage system
64 64 64 64
1
The text VMWARE_SRM_SNAP must be somewhere in this name for the SRA adapter to function
properly.
EMC CLARiiON Integration with
VMware ESX Server
Applied Technology 47
Page view 46
1 2 ... 42 43 44 45 46 47 48 49 50 51 52 ... 57 58

Comments to this Manuals

No comments