Discontinuing xp continuous access operations, Performing xp continuous access pair operations, Performing xp – HP StorageWorks XP Remote Web Console Software User Manual
Page 94
Discontinuing XP Continuous Access operations
If you plan to use XP Continuous Access for nondisruptive data migration or duplication configure
and establish XP Continuous Access operations, allow XP Continuous Access to synchronize volumes,
redirect application I/Os (if migrating), and discontinue XP Continuous Access operations. When
you are ready to discontinue XP Continuous Access operations, perform XP Continuous Access
operations in the correct order to avoid error messages. For example, XP Continuous Access will
not delete an RCU path until you delete all XP Continuous Access pairs still using that path, and
you cannot delete a group until you delete all XP Continuous Access Asynchronous pairs in that
group.
1.
Delete all XP Continuous Access pairs from MCUs (pairsplit-S ). For XP Continuous Access
Async pairs, use the Delete Range-Group option to delete all pairs in a group at one time.
Verify that the pair status changed to SMPL for all XP Continuous Access volumes before
continuing.
2.
Delete XP Continuous Access Async groups from MCUs (see
). The RCU automatically deletes a group when all pairs in the
group are deleted.
3.
Delete RCUs (see
“Deleting RCUs (Delete RCU)” (page 76)
). Check each CU image of each
MCU to ensure that all RCUs are deleted before continuing.
4.
Remove remote copy connections (physical paths). If you are not familiar with the operation
of remote copy hardware components, call HP technical support for assistance.
5.
For Fibre Channel interface, reset initiator ports to ordinary targets at MCUs (see
).
Performing XP Continuous Access pair operations
Before starting XP Continuous Access operations, consider the relative importance of disk array
I/O performance and disaster recovery preparation. As described in
Access operations and disk array performance” (page 92)
, remote copy operations can affect I/O
performance of MCUs and RCUs. XP Continuous Access provides many options (initial copy options,
pair options, group options, async options) to control impact of XP Continuous Access operations
on I/O performance. These options can be set separately for each pair, XP Continuous Access
Async group, and MCU to provide maximum flexibility. You can select options that minimize impact
of XP Continuous Access operations on disk array performance or options that maximize
effectiveness of XP Continuous Access operations to ensure the best level of backup data integrity.
System-level factors (for example, number of paths) can also affect XP Continuous Access operations
and disk array performance (see
“Disk array performance conditions and recommendations”
).
For XP Continuous Access disaster recovery operations, ensure that RCUs are attached to a host
server to enable sense information reporting and host failover information transferring. If the remote
site is unattended, attach RCUs to a host server at the main site, so the system administrator can
monitor operational condition of RCUs.
To prepare for XP Continuous Access volume pair operations, identify volumes (by port, TID, and
LUN and/or by LDEV ID) for which you want to establish XP Continuous Access remote copy
operations. Identify volumes required for system operations and volumes containing important data
to be backed up (for example, DB log files). Copying these volumes to the remote site enables
faster disaster recovery than maintaining a current version of these files at the remote site. For large
databases spanning multiple volumes, plan to establish an XP Continuous Access Asynchronous
consistency group for each database, so update sequence consistency of the database can be
ensured at the remote site.
94
Performing XP Continuous Access configuration operations