Operating System Software Owner manual

multi.1
5909 rcpy.222.103.59.1 snp vcopy testvv.3 103 RO normal -- -- -- 1024 snap
multi.1
5915 rcpy.222.103.58 snp vcopy testvv.3 103 RO normal -- -- -- 1024 snap
multi.1
3. Verify that the primary system is up and the Remote Copy pairs are synchronized:
a. Issue the showrcopy command on the failover system (SystemC).
b. Verify that for the target system (SystemA):
• the Status of the target system is ready
• the Status of primary system’s sending links (SystemA) is Up
• the SyncStatus of all volumes in the Primary-Rev volume groups is Synced
For example, the showrcopy output on SystemC looks like:
# 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 Primary-Rev Periodic Last-Sync 2009-06-29 14:54:14 PDT ,
Period 5m, over_per_alert
LocalVV ID RemoteVV ID SyncStatus LastSyncTime
testvv.0 300 testvv.0 100 Synced 2009-06-29 14:54:54 PDT
testvv.1 301 testvv.1 101 Synced 2009-06-29 14:54:50 PDT
testvv.2 302 testvv.2 102 Synced 2009-06-29 14:54:51 PDT
testvv.3 303 testvv.3 103 Synced 2009-06-29 14:54:52 PDT
Name Target Status Role Mode Options
multi.1.r96 SystemB Started Primary-Rev Periodic Last-Sync 2009-06-29 14:54:28 PDT ,
Period 5m, over_per_alert
LocalVV ID RemoteVV ID SyncStatus LastSyncTime
testvv.0 300 testvv.0 200 Synced 2009-06-29 14:54:38 PDT
testvv.1 301 testvv.1 201 Synced 2009-06-29 14:54:36 PDT
testvv.2 302 testvv.2 202 Synced 2009-06-29 14:54:41 PDT
testvv.3 303 testvv.3 203 Synced 2009-06-29 14:54:34 PDT
c. Issue the showrcopy command on the recovered system (SystemA).
172 Disaster Recovery for Synchronous Long Distance