HP XP24000 HP Replication Adapter for VMware vCenter Site Recovery Manager Adm - Page 8

Discovery Devices sequence, Testing failover, Failover, Snapshot for target group keys: Snapshot ID

Page 8 highlights

1. SRM makes a request to RM SRA to find available arrays. 2. RM SRA connects to a RAID Manager Instance and requests all groups to find array controller information (WWN) and, using RAID Manager commands, to find remote arrays. 3. RM SRA returns the results to SRM. Discovery Devices sequence The Device discovery sequence is: 1. SRM makes a request to RM SRA to find replicated devices on both the local (protected) and Remote (recovery) arrays. 2. RM SRA connects to a RAID Manager instance and requests all groups to find replicated PVOL on the protected array and the replicated SVOL on the recovered array using RAID Manager commands. 3. RM SRA looks for PVOLs/SVOLs that are members of data replication groups. 4. For each replicated PVOL found on the protected array and SVOL on the recovered array , RM SRA gathers the following information: • Replicated groups and names: Group ID and name • Target group keys: Group name • Replicated devices and IDs: LDEV# and LUN WWN • Target device keys: LDEV# • Snapshot for target group keys: Snapshot ID, each SnapShot LDEV# and LUN WWN • Snapshot for target device keys: Snapshot LDEV# and LUN WWN 5. RM SRA returns this information to SRM. 6. SRM mapps proteced devices with datastore using the replicated devices and LUN WWN. Testing failover The failover testing sequence is: 1. SRM makes a request to RM SRA to test the failover to replicated devices on a remote (recovery) array. 2. RM SRA connects to a RAID Manager Instance and requests finding replicated SnapShot SVOL on the recovery array using RAID Manager commands. 3. RM SRA looks and checks for Snapshot SVOLs that are members of data replication groups and then makes R/W SVOLs. 4. RM SRA provides information and performs test failover operations for nondisruptive testing of SRM failover recovery plans and returns the following information: • Snapshot for target group keys: Snapshot ID, each Snapshot LDEV# and LUN WWN • Snapshot for target device keys: Snapshot LDEV# and LUN WWN 5. SRM maps LUNs with datastore using the replicated target keys and LUN WWN. 6. SRM verifies the SVOL snapshots can be recovered after failure of the local array (via a recovery plan). SRM uses RM SRA to unpresent and delete the snapshots. NOTE: To test failover, the SVOL snapshots must be created as PAIR state and must be registered to horcm.conf as group. Failover The failover sequence is: 8 VMware Site Recovery Manager overview

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53

1.
SRM makes a request to RM SRA to find available arrays.
2.
RM SRA connects to a RAID Manager Instance and requests all groups to find array controller
information (WWN) and, using RAID Manager commands, to find remote arrays.
3.
RM SRA returns the results to SRM.
Discovery Devices sequence
The Device discovery sequence is:
1.
SRM makes a request to RM SRA to find replicated devices on both the local (protected) and
Remote (recovery) arrays.
2.
RM SRA connects to a RAID Manager instance and requests all groups to find replicated PVOL
on the protected array and the replicated SVOL on the recovered array using RAID Manager
commands.
3.
RM SRA looks for PVOLs/SVOLs that are members of data replication groups.
4.
For each replicated PVOL found on the protected array and SVOL on the recovered array ,
RM SRA gathers the following information:
Replicated groups and names: Group ID and name
Target group keys: Group name
Replicated devices and IDs: LDEV# and LUN WWN
Target device keys: LDEV#
Snapshot for target group keys: Snapshot ID, each SnapShot LDEV# and LUN WWN
Snapshot for target device keys: Snapshot LDEV# and LUN WWN
5.
RM SRA returns this information to SRM.
6.
SRM mapps proteced devices with datastore using the replicated devices and LUN WWN.
Testing failover
The failover testing sequence is:
1.
SRM makes a request to RM SRA to test the failover to replicated devices on a remote (recovery)
array.
2.
RM SRA connects to a RAID Manager Instance and requests finding replicated SnapShot SVOL
on the recovery array using RAID Manager commands.
3.
RM SRA looks and checks for Snapshot SVOLs that are members of data replication groups
and then makes R/W SVOLs.
4.
RM SRA provides information and performs test failover operations for nondisruptive testing
of SRM failover recovery plans and returns the following information:
Snapshot for target group keys: Snapshot ID, each Snapshot LDEV# and LUN WWN
Snapshot for target device keys: Snapshot LDEV# and LUN WWN
5.
SRM maps LUNs with datastore using the replicated target keys and LUN WWN.
6.
SRM verifies the SVOL snapshots can be recovered after failure of the local array (via a
recovery plan). SRM uses RM SRA to unpresent and delete the snapshots.
NOTE:
To test failover, the SVOL snapshots must be created as PAIR state and must be registered
to
horcm.conf
as group.
Failover
The failover sequence is:
8
VMware Site Recovery Manager overview