User's Manual
Table Of Contents
- HP 3PAR Storage Replication Adapter 5.5.2 for VMware® vCenter Site Recovery Manager™ User Guide
- Contents
- 1 Introduction
- 2 VMware vCenter Site Recovery Manager overview
- 3 Supported configurations
- 4 HP 3PAR SRA installation and configuration prerequisites
- 5 Installing HP 3PAR SRA
- 6 HP 3PAR storage system setup
- 7 Configuring VMware vCenter Site Recovery Manager and HP 3PAR SRA
- 8 Recovery and failback
- 9 HP 3PAR SRA for the VMware SRM 5.5 utility
- 10 Partial licensing
- 11 HP 3PAR SRA 5.5.2 SRM vs HP 3PAR Remote Copy state diagram
- 12 Special notes
- 13 Support and other resources
- 14 Documentation feedback
Support for multiple array pair configuration
HP 3PAR SRA supports multiple array pair configurations. Different remote copy groups from the
array pairs can be part of a single recovery plan or separate recovery plan.
Support for virtual volume sets and host sets
HP 3PAR SRA supports vvset (virtual volume set) and host set features of HP 3PAR StoreServ Storage
system.
The following are the HP 3PAR SRA pre-requisites for HP 3PAR host set and HP 3PAR virtual volume
set features:
• For HP 3PAR OS versions 3.1.3 or later:
When an RC group is created, virtual volume set is automatically generated for the remote
copy group virtual volumes in both primary and secondary HP 3PAR StoreServ Storage systems.
To use the vv set feature for presenting LUNs to a host, then HP recommends that you use
automatically created vv sets to present the virtual volumes to the host.
• For HP 3PAR OS version 3.1.2 MU3:
To use the vv set feature for presenting the primary LUNs to host, you must manually create
the vv set and map the remote copy group virtual volumes to the created vv set in the primary
HP 3PAR StoreServ Storage system. Similarly, HP recommends that you create the vv set
manually in the secondary HP 3PAR StoreServ Storage system and map the RC group virtual
volumes to the created vv set. In the event of failover, HP 3PAR SRA will use the manually
created vv set to present LUNs to the host and HP 3PAR SRA does not create the vv set by
itself.
All virtual volumes exposed via the same HP 3PAR virtual volume set and protected by SRM
must belong to the same remote copy group.
If virtual volumes are from a virtual volume set with multiple VMs created, make sure to include
all virtual volumes in a single remote copy group and in the same protection group. Otherwise,
there is a potential of losing connectivity to the VMs if virtual volumes are included in more
than one remote copy group and all remote copy groups are not included in the same protection
group.
NOTE:
• If a remote copy group has virtual volumes that are not participating in datastore creation and
if these virtual volumes are exposed to a different host, then there are chances of data
corruption.
• You must make sure that all virtual volumes in remote copy group are participating in datastore.
The virtual volumes in a remote copy group that are not participating in datastore creation
must not be presented to a host.
• If the virtual volumes participating in an SRM configuration are exposed using a virtual volume
set, any virtual volume member in this set, not used by SRM in the same protected group loses
connectivity to the LUN after a failover.
• In the event of a failover, if the participating virtual volumes and hosts are part of vv set and
host set respetively, then the LUNs are exposed using vv set and host set features.
• If the participating virtual volumes and host are not part of vv set and host set features, then
the LUNs are exposed individually to the ESX(i) hosts.
Support for virtual volume sets and host sets 37