Operating System Software User Manual

SystemA 42 IP failed mirror_config
SystemB 44 IP ready mirror_config
Link Information
Target Node Address Status Options
SystemA 0 10.100.33.96 Down
SystemA 1 10.101.33.96 Down
SystemB 0 10.100.33.195 Up
SystemB 1 10.101.33.195 Up
receive 0 receive Up
receive 1 receive Up
Group Information
Name Target Status Role Mode Options
multi.1.r96 SystemA Stopped Secondary Periodic Period 5m, over_per_alert
LocalVV ID RemoteVV ID SyncStatus LastSyncTime
testvv.0 300 testvv.0 100 Stopped 2009-06-29 12:07:51 PDT
testvv.1 301 testvv.1 101 Stopped 2009-06-29 12:07:51 PDT
testvv.2 302 testvv.2 102 Stopped 2009-06-29 12:07:51 PDT
testvv.3 303 testvv.3 103 Stopped 2009-06-29 12:07:51 PDT
Name Target Status Role Mode Options
multi.1.r96 SystemB Backup Secondary Periodic Period 5m, over_per_alert
LocalVV ID RemoteVV ID SyncStatus LastSyncTime
testvv.0 300 testvv.0 200 Synced 2009-06-29 12:00:40 PDT
testvv.1 301 testvv.1 201 Synced 2009-06-29 12:00:39 PDT
testvv.2 302 testvv.2 202 Synced 2009-06-29 12:00:40 PDT
testvv.3 303 testvv.3 203 Synced 2009-06-29 12:00:41 PDT
Stages of Disaster Recovery in SLD Remote-Copy Configurations
1. The primary system fails or you take it offline.
2. Failover changes the secondary volume groups to primary on the failover system (the backup
system that is still working) and enables I/O to the failover system.
3. The primary system recovers and comes online.
4. Recovery reverses the natural direction of data flow and resynchronizes the systems.
5. Restore restores all volume groups to their natural direction of data flow and starts remote
copy.
NOTE: Target names change depending on the links between the systems. For example, a
target name such as SystemA with an IP address of 10.100.33.96 might appear in some
output as RC096IP.
Failing Over to the Synchronous Backup System
If the primary system fails or is taken offline, you can fail the storage system over to the synchronous
backup system (see Figure 66 (page 208)) if the backup system:
• Is still functioning properly.
• Is not affected by the situation that took the primary system offline (is not in danger of failing
as well).
When the synchronous backup system becomes the failover system, the synchronous backup system
temporarily assumes the role of the primary system.
Failing Over to the Synchronous Backup System 207