Recovery for 1-to-n configurations – HP 3PAR Operating System Software User Manual
Page 196
2.
Verify the reversal of volume group roles.
a.
Issue the showrcopy command on the failover system (System2).
b.
In the Group Information area, check that the Role column for the reversed volume
group displays Primary-Rev (primary as a result of reversal).
The following example of the showrcopy command output for System2 shows that the Role
of periodic_group_1.r96 is now Primary-Rev:
# showrcopy
Remote Copy System Information
Status: Started, Normal
Target Information
Name ID Type Status Options Policy
System1 7 IP failed mirror_config
Link Information
Target Node Address Status Options
System1 0 10.100.33.96 Down
System1 1 10.101.33.96 Down
receive 0 10.100.33.96 Down
receive 1 10.101.33.96 Down
Group Information
Name Target Status Role Mode Options
periodic_group_1.r96 System1 Stopped Primary-Rev Periodic over_per_alert
LocalVV ID RemoteVV ID SyncStatus LastSyncTime
remotevv.0 21 localvv.0 413 Stopped Thu Dec 14 18:23:52 PST 2006
remotevv.1 22 localvv.1 414 Stopped Thu Dec 14 18:23:52 PST 2006
3.
(Optional) To back up data in the reversed volume groups, export the reversed virtual volumes
(for example, remotevv.0 and remotevv.1) as read/write snapshots.
Recovery for 1-to-N Configurations
1.
Recover the failed system.
2.
When both systems in the remote-copy pair are ready to resume normal operation, reverse
the natural direction of data flow and resynchronize the systems.
a.
Stop I/O to the reversed volume groups on the failover system.
b.
On the failover system (System2), issue the following command:
# setrcopygroup recover -t
where
(System1)
The setrcopygroup recover command copies data from the reversed volume groups on
the failover system to the corresponding volume groups on the recovered system. In this
example, it copies data from periodic_group_1.r96 on System2 to periodic_group_1
on System1.
3.
Verify that the remote-copy pair is synchronizing:
a.
Issue the showrcopy command on the failover system (System2).
196
Disaster Recovery for M-to-N Configurations