HP StorageWorks XP Remote Web Console Software - Manual (Page 141)

3. Perform the planned outage of the TrueCopy for Mainframe MCU.
4. When the MCU is fully powered on and ready to resynchronize operations, resynchronize
the TrueCopy for Mainframe Asynchronous pairs at all MCUs that were powered off (use the
resynchronize group option).
Planned Outage of the RCU or Remote Copy Connection
You must suspend all affected TrueCopy for Mainframe pairs prior to a planned outage of an RCU
or of a remote copy connection component (for example, switch, extender). If you do not suspend
the pairs first, the MCU(s) will detect the communication failure, suspend all affected pairs, and
generate SIMs and console messages reporting the failures. To perform a planned outage of a
TrueCopy for Mainframe RCU or remote copy connection component:
1. Identify all TrueCopy for Mainframe M-VOLs which will be affected by the equipment outage.
You need to know the MCU, CU, and LDEV ID for each of these M-VOLs.
•
For RCU power-off, identify all M-VOLs which are paired with R-VOLs in the RCU to be
powered off.
•
For remote copy connection outage, identify all M-VOLs in all MCUs which use the
path/component to be powered off.
2. Connect to each MCU which contains affected M-VOLs, and suspend all affected TrueCopy
for Mainframe pairs. Make sure to confirm the pair status changes (TrueCopy for Mainframe
Detailed Information dialog box or CQUERY TSO command).
3. Perform the planned outage of the RCU or remote copy connection.
4. When the RCU is fully powered on and ready to resynchronize operations, resynchronize all
TrueCopy for Mainframe pairs at each MCU. Make sure to confirm the pair status changes.
Planned Outage of the MCU and RCU
When you plan an outage of TrueCopy for Mainframe MCUs and RCUs at the same time, the
MCUs must be powered off before the RCUs and powered on after the RCUs. To perform a planned
outage of a TrueCopy for Mainframe MCU and RCU:
1. If RCU power-on will be difficult to control (for example, Power-Control-Interface setting), you
should consider increasing or disabling the RCU Ready CT group option for each TrueCopy
for Mainframe Asynchronous group with R-VOLs in the RCU(s) to be powered off.
2. Perform the planned outage of the MCU(s). Do not power-on the MCU(s) yet.
3. If an RCU to be powered off is connected to an MCU which is not powered off, make sure to
suspend those TrueCopy for Mainframe pairs before powering off the RCU.
4. Perform the planned outage of the RCU(s).
5. Power on the RCU(s). Make sure that they are fully operational and ready to resynchronize
operations before powering on the MCUs.
6. Power on the MCU(s), and make sure that they are ready to resynchronize operations. If you
suspended any pairs in step (3), you can also resynchronize those pairs now.
Discontinuing TrueCopy for Mainframe Operations
If you plan to use TrueCopy for Mainframe for nondisruptive data migration or duplication, you
will configure and establish TrueCopy for Mainframe operations, allow TrueCopy for Mainframe
to synchronize the volumes, redirect application I/Os (if migrating), and then discontinue TrueCopy
for Mainframe operations. When you are ready to discontinue TrueCopy for Mainframe operations
, you will need to perform TrueCopy for Mainframe operations in the correct order to avoid
generating error messages. For example, TrueCopy for Mainframe will not allow you to delete an
RCU path until you have released all TrueCopy for Mainframe pairs still using that path, and you
cannot delete a group until you have released all TrueCopy for Mainframe Asynchronous pairs in
that group from the MCU.
Discontinuing TrueCopy for Mainframe Operations 141