Handling backup system failure – HP 3PAR Operating System Software User Manual
Page 247
c.
Issue the showrcopy command on the asynchronous periodic backup system (SystemC)
and verify that it has resumed the role of backup system.
The following example shows the showrcopy command output for SystemC:
# showrcopy
Remote Copy System Information
Status: Started, Normal
Target Information
Name ID Type Status Options Policy
SystemA 42 IP ready mirror_config
SystemB 44 IP ready mirror_config
Link Information
Target Node Address Status Options
SystemA 0 10.100.33.96 Up
SystemA 1 10.101.33.96 Up
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 Started Secondary Periodic Period 5m, over_per_alert
LocalVV ID RemoteVV ID SyncStatus LastSyncTime
testvv.0 300 testvv.0 100 Synced 2009-06-29 14:57:34 PDT
testvv.1 301 testvv.1 101 Synced 2009-06-29 14:57:33 PDT
testvv.2 302 testvv.2 102 Synced 2009-06-29 14:57:35 PDT
testvv.3 303 testvv.3 103 Synced 2009-06-29 14:57:32 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 14:57:45 PDT
testvv.1 301 testvv.1 201 Synced 2009-06-29 14:57:46 PDT
testvv.2 302 testvv.2 202 Synced 2009-06-29 14:57:42 PDT
testvv.3 303 testvv.3 203 Synced 2009-06-29 14:57:46 PDT
Handling Backup System Failure
If one backup system in an SLD remote-copy configuration fails, remote copy can still continue
between the primary system and the second backup system.
illustrates an SLD configuration in which the backup system (SystemB), fails,
yet remote copy in asynchronous periodic mode still continues between the primary system (SystemA)
and second backup system (SystemC). Similarly, if SystemC failed, remote copy in synchronous
mode would still continue between the primary system (SystemA) and the first backup system
(SystemB).
Handling Backup System Failure 247