Planned outage of the mcu and rcu, To perform a planned outage of a tc390 mcu and rcu, Truecopy disaster recovery operations – HP StorageWorks XP Remote Web Console Software User Manual
Page 133: Preparing for disaster recovery
TrueCopy for z/OS user guide 133
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 TC390 RCU or remote copy connection component:
1.
Identify all TC390 M-VOLs that will be affected by the equipment outage. You need to know the MCU,
CU image, and LDEV ID for each of these M-VOLs.
• For RCU power-off, identify all M-VOLs that are paired with R-VOLs in the RCU to be powered off.
• For remote copy connection outage, identify all M-VOLs in all MCUs that use the path/component
to be powered off.
2.
Connect to each MCU that contains affected M-VOLs and suspend all affected TC390 pairs. Make sure
to confirm the pair status changes (TC390 Pair Status window 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 resume operations, resume all TC390 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 TC390 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 TC390 MCU and RCU:
1.
If RCU power-on will be difficult to control (for example, Power-Control-Interface setting), consider
increasing or disabling the RCU ready timeout group option (see
) for each
TC390A group with R-VOLs in the RCU(s) to be powered off.
2.
Perform the planned outage of the MCU(s) as described in ”
page 133. Do not power-on the MCU(s) yet.
3.
If an RCU to be powered off is connected to an MCU that is not powered off, make sure to suspend
those TC390 pairs before powering off the RCU as described in ”
4.
Perform the planned outage of the RCU(s).
5.
Power on the RCU(s). Verify that they are fully operational and ready to resume operations before
powering on the MCUs.
6.
Power on the MCU(s) and verify that they are ready to resume operations. If you suspended any pairs
in
, you can also resume those pairs now.
TrueCopy Disaster Recovery Operations
Preparing for Disaster Recovery
The type of disaster and the status of the TC390 volume pairs will determine the best approach for disaster
recovery. For example, if all TC390 volume pairs are in the duplex state when a total system failure occurs
at a single point in time, the R-VOLs are current and recovery is straightforward. Unfortunately, some
disasters are not so “orderly” and involve intermittent or gradual failures occurring over a longer period of
time. The user should anticipate and plan for all types of failures and disasters.
The major steps in preparing for disaster recovery are:
1.
Identify the volumes and volume groups that contain important files and data for disaster recovery, such
as DB2 log files, master catalog, key user catalogs, and system control data sets. In addition to
supporting TC390 remote copy operations as well as PPRC commands, the
XP128/XP1024/XP10000/XP12000 provides battery-backed nonvolatile duplexed cache, full
hardware redundancy, dynamic sparing, and an advanced RAID-5 implementation to ensure full data
integrity in the event of a sudden power outage or other failure.
2.
Install the Command View XP or XP Remote Web Console and TC390 hardware and software, and
establish TC390 operations for the volumes and groups identified in
. Make sure to select the
correct CU images to access the appropriate volumes.
3.
Use the appropriate combination of TC390 options for disaster recovery: