Disaster recovery for 1-to-n configurations – HP 3PAR Operating System Software User Manual
Page 191
d.
Verify that the Role of the primary volume groups is Primary.
The following example of the showrcopy command output for System2 shows that the
Role
of periodic_group_1 is correctly restored to Primary:
# showrcopy
Remote Copy System Information
Status: Started, Normal
Target Information
Name ID Type Status Options Policy
System1 11 IP ready mirror_config
Link Information
Target Node Address Status Options
System1 0 10.100.33.63 Up
System1 1 10.101.33.63 Up
receive 0 10.100.33.63 Up
receive 1 10.101.33.63 Up
Group Information
Name Target Status Role Mode Options
periodic_group_1 System1 Started Primary Periodic Last-Sync Thu Dec 14 18:19:17 PST
2006 , over_per_alert
LocalVV ID RemoteVV ID SyncStatus LastSyncTime
localvv.0 413 remotevv.0 21 Synced Thu Dec 14 18:40:14 PST 2006
localvv.1 414 remotevv.1 22 Synced Thu Dec 14 18:39:03 PST 2006
Disaster Recovery for 1-to-N Configurations
Before you begin disaster recovery:
1.
Review the example remote-copy pair used to illustrate
1-to-N disaster recovery.
“System Information during Normal Operation for 1-to-N
Configurations” (page 192)
2.
Review system information for 1-to-N configurations.
“System Information during Failover for 1-to-N Remote-Copy
Configurations” (page 194)
3.
Understand what system information to look for during
a failover.
Recover the systems:
“Recovering from Disaster for 1-to-N Configurations”
(page 195)
1.
Change secondary volume groups to primary.
2.
Export recovered data if desired.
3.
Recover the failed system.
4.
Reverse the natural direction of data flow and
synchronize data.
5.
Verify volume groups are started.
6.
Restore the natural direction of data flow.
For additional information, see the following:
•
“About the Remote-Copy Commands” (page 261)
•
“Quick Disaster Recovery Guide” (page 259)
The disaster recovery steps for 1-to-N configurations refer to the setup illustrated in
.
Disaster Recovery for 1-to-N Configurations
191