HP XP7 Storage - Manual (Page 98)

Consistency of S-VOL Fence level Type S-VOL status
Not consistent. The S-VOL is not synchronized because not all tracks
have been copied from the P-VOL yet. The S-VOL must be initialized
(or copied from the P-VOL at a later time). Data Status
Never Initial copy
failed Suspended
Suspect. The S-VOL is not synchronized with its P-VOL if any write I/Os
were issued to the P-VOL after the pair was split. The pair should be Data Status
Never S-VOL by
operator Suspended
released and restarted using Entire for the Initial Copy Type option. If
you are sure that no data on the P-VOL changed, you can use No
Copy for Initial Copy Type.
Consistent. The S-VOL is synchronized with its P-VOL. Data All other types Suspend
Suspect. The S-VOL is not synchronized with its P-VOL if any write I/Os
were issued to the P-VOL after the pair was suspended. Restore the Status Never
consistency of the S-VOL and update it, if required. The time of
suspension indicated on the Last Update Time field of the Detailed
Information dialog box (MCU SVP time) will help to determine the last
time the S-VOL was updated.
For pairs with a P-VOL fence level setting of No Copy, further analysis is required to determine the S-VOL consistency. This can
be determined by using sense information transferred via host failover, or by comparing the contents of the S-VOL with other files
that are confirmed to be consistent (for example, database log files). The S-VOLs should be recovered using the files that are
confirmed to be consistent.
Actual data recovery must be done using recovery point data in the database operation log.
Transferring operations back to the local site
When host operations are running at the remote site, the local site should be restored and operations
transferred back.
In the following procedure, you will establish Cnt Ac-S Z pairs at the remote site, with data flow
moving from the remote site to the local. After the pairs are synchronized and in Duplex status,
they will be released, then new pairs will be created at the local site with data flow moving from
local to remote, as originally set up.
Select the appropriate procedure below based on whether you deleted pairs to switch operations
to the remote site, or ran the Business Continuity Manager YKSUSPND REVERSE command.
Procedure 35 To transfer operations to the local site—if pairs were deleted when operations were
switched to the remote site
1. At the local site, bring up the host. Make sure that Cnt Ac-S Z components are operational.
2. At the local site, release all pairs on the primary system.
Specify Force in the Deleting Mode option to release all Cnt Ac-S Z pairs in each CU. Make
sure to connect with all MCUs and all CUs to release all pairs.
3. At the local site, delete the Cnt Ac-S Z association with the secondary systems (Remove Remote
Connection). In Remote Web Console, connect to each primary system to make sure that all
RCUs are deleted.
4. At the local and remote sites, change path and port settings.
- If you plan to use the same remote paths:
•
At the local site, change the existing initiator ports to RCU target ports.
If system option mode 114 is enabled on all MCUs and RCUs, the ports will reconfigure
automatically if you use the CESTPATH or YKBLDPTH command to add the pairs at the
remote site.
For Fibre Channel interface, do not use the CESTPATH or YKBLDPTH and CDELPATH or
YKDELPTH commands at the same time as the SCSI path definition function of LUN
Manager. The Fibre Channel interface ports need to be configured as initiator ports or
98 Disaster recovery