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

reverseReplication command, CA_SVOL for target group keys: CA_SVOL ID, each CA_SVOL LDEV# and LUN WWN

Get HP XP24000 PDF manuals and user guides View all HP XP24000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

1. SRM makes a request to RM SRA to failover to replicated devices on a remote (recovery) array. 2. RM SRA connects to a RAID Manager instance and requests finding replicated CA_SVOL on the recovery array using RAID Manager commands. 3. RM SRA looks and checks for CA SVOLs that are members of data replication groups and then executes horctakeover -SS to make R/W SVOLs. 4. RM SRA provides information and performs failover operations to execute SRM failover recovery plans and returns the following information: • CA_SVOL for target group keys: CA_SVOL ID, each CA_SVOL LDEV# and LUN WWN • CA_SVOL for target device keys: CA_SVOL LDEV# and LUN WWN 5. SRM maps LUNs with datastore using the replicated target keys and LUN WWN, and then moves all resources to the recovery site. NOTE: During configuration setup, replicated PVOLs and SVOLs must be presented to both the protected and recovery ESX hosts. reverseReplication command The reverseReplication command sequence is: 1. SRM makes a request to RM SRA to reverse replication after failover and start replicating changes made at the recovery site to the original protected site. 2. RM SRA connects to a RAID Manager instance and requests finding the target ID returned by failover on the recovery array using RAID Manager commands. 3. RM SRA looks and checks for the target IDs that are members of data replication groups and then executes pairresync -swaps to reverse the replication. 4. RM SRA returns Success or ERROR for the specified consistency group and/or device. 5. SRM follows the reverseReplication command with syncOnce and querySyncStatus commands to initiate and monitor data transfer. This is necessary when production services have been running at site B for long enough to create a large amount of data that must be replicated back to site A. NOTE: During configuration setup, the reverseReplication command must be executed from the recovery site as replication source. restoreReplication command The restoreReplication command sequence is: 1. SRM makes a request to RM SRA to restore replication from the protected site to the recovery site after executing failover at the recovery site. SRM allows users to perform a disruptive test identical to failover in case of a disaster. 2. RM SRA connects to a RAID Manager instance and, using RAID Manager commands, requests finding the source device returned by the protection array. 3. RM SRA looks and checks for the target IDs that are members of data replication groups and then executes pairsplit -RB and pairresync to restore the replication. 4. RM SRA returns Success or ERROR for the specified consistency group and/or device. 5. SRM follows the restoreReplication command with syncOnce and querySyncStatus commands to initiate and monitor data transfer. SRM displays status of this data transfer to the user. Once that data transfer is complete SRM indicates to the user that the system is ready for test and failover. NOTE: During configuration setup, the restoreReplication command must be executed from the protection site as replication source. RMSRA20 configurations 9

  • 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 failover to replicated devices on a remote (recovery)
array.
2.
RM SRA connects to a RAID Manager instance and requests finding replicated CA_SVOL on
the recovery array using RAID Manager commands.
3.
RM SRA looks and checks for CA SVOLs that are members of data replication groups and
then executes
horctakeover -SS
to make R/W SVOLs.
4.
RM SRA provides information and performs failover operations to execute SRM failover
recovery plans and returns the following information:
•
CA_SVOL for target group keys: CA_SVOL ID, each CA_SVOL LDEV# and LUN WWN
•
CA_SVOL for target device keys: CA_SVOL LDEV# and LUN WWN
5.
SRM maps LUNs with datastore using the replicated target keys and LUN WWN, and then
moves all resources to the recovery site.
NOTE:
During configuration setup, replicated PVOLs and SVOLs must be presented to both the
protected and recovery ESX hosts.
reverseReplication
command
The
reverseReplication
command sequence is:
1.
SRM makes a request to RM SRA to reverse replication after failover and start replicating
changes made at the recovery site to the original protected site.
2.
RM SRA connects to a RAID Manager instance and requests finding the target ID returned by
failover on the recovery array using RAID Manager commands.
3.
RM SRA looks and checks for the target IDs that are members of data replication groups and
then executes
pairresync -swaps
to reverse the replication.
4.
RM SRA returns
Success
or
ERROR
for the specified consistency group and/or device.
5.
SRM follows the
reverseReplication
command with
syncOnce
and
querySyncStatus
commands to initiate and monitor data transfer. This is necessary when production services
have been running at site B for long enough to create a large amount of data that must be
replicated back to site A.
NOTE:
During configuration setup, the
reverseReplication
command must be executed
from the recovery site as replication source.
restoreReplication
command
The
restoreReplication
command sequence is:
1.
SRM makes a request to RM SRA to restore replication from the protected site to the recovery
site after executing failover at the recovery site. SRM allows users to perform a disruptive test
identical to failover in case of a disaster.
2.
RM SRA connects to a RAID Manager instance and, using RAID Manager commands, requests
finding the source device returned by the protection array.
3.
RM SRA looks and checks for the target IDs that are members of data replication groups and
then executes
pairsplit -RB
and
pairresync
to restore the replication.
4.
RM SRA returns
Success
or
ERROR
for the specified consistency group and/or device.
5.
SRM follows the
restoreReplication
command with
syncOnce
and
querySyncStatus
commands to initiate and monitor data transfer. SRM displays status of this data transfer to
the user. Once that data transfer is complete SRM indicates to the user that the system is ready
for test and failover.
NOTE:
During configuration setup, the
restoreReplication
command must be executed
from the protection site as replication source.
RMSRA20 configurations
9