Copy export recovery

Use this page to test a copy export recovery or perform an actual copy export recovery on the TS7700.

If the cluster does not possess a physical library, the Copy export recovery page is not visible on the TS7700 web interface.

Copy export permits the export of all virtual volumes and the virtual volume database to physical volumes, which can then be ejected and saved as part of a data retention policy for disaster recovery. You can also use this function to test system recovery.
Note: For a detailed summary of copy export recovery including preparation for and performing a copy export recovery, refer to the following white paper https://www.ibm.com/support/pages/node/6355037.
Before attempting a copy export, ensure all physical media to be used in the recovery is inserted. During a copy export recovery, all current virtual and physical volumes are erased from the database and virtual volumes are erased from the cache. Do not attempt a copy export operation on a cluster where current data is to be saved.
Support Matrix
Table 1. Recovery Cluster Support Matrix
  Recovery Cluster
Source Cluster R2.1 R3.3 R4.1 Phase 1 R4.1 Phase 2 R4.2 R5.0 R5.1 R5.2
R2.1 X X X X (*1) X X(*1) X(*1) *2
R3.3   X X X X X X *2
R4.1 Phase 1     X X X X X *2
R4.1 Phase 2       X X X X X
R4.2           X X X
R5.0           X X X
R5.1             X X
R5.2               X
*1 In order to restore from a backup created at R2.1 vtd_exec.244 needs to be installed

*2 Restoring tapes created at these levels have to be attempted at an earlier code level.

Important: In a grid configuration, each TS7700 is considered a separate source. This means that only the physical volume exported from a source TS7700 can be used for recovery of that source. Physical volumes exported from more than one source TS7700 in a grid configuration cannot be combined to use in recovery. Recovery can only occur to a single cluster configuration; the TS7700 used for recovery must be configured as Cluster 0.
Secondary Copies
If you create a new secondary copy, the original secondary copy is deleted since it becomes inactive data. For instance, if you modify constructs for virtual volumes that have already been exported and the virtual volumes are remounted, a new secondary physical volume is created. The original physical volume copy is deleted without overwriting the virtual volumes. When the copy export operation is rerun, the new, active version of the data is used.
The following fields and options are presented to the user to assist in testing recovery or performing a recovery.
Volser of physical stacked volume for Recovery Test
The physical volume from which the copy export recovery attempts to recover the database.
Disaster Recovery Test Mode
This option determines whether a Copy Export Recovery is run as a test or to recover a machine that has suffered a disaster. If this box contains a checkmark (default status), the Copy Export Recovery runs as a test. If the box is cleared, the recovery process runs in "normal" mode, as when recovering from an actual disaster.
When the recovery is run as a test, the content of exported tapes remains unchanged. Additionally, primary physical copies remain unrestored and reclaim processing is disabled to halt any movement of data from the exported tapes. Any new volumes written to the machine are written to newly added scratch tapes and will not exist on the previously exported volumes. This ensures that the data on the copy export tapes remains unchanged during the test.
In contrast to a test recovery, a recovery performed in "normal" mode (box cleared) rewrites virtual volumes to physical storage if the constructs change, so that the virtual volume's data can be put in the correct pools. Also in this type of recovery, reclaim processing remains enabled and primary physical copies are restored, requiring the addition of scratch physical volumes. A recovery run in this mode allows the data on the copy export tapes to expire in the normal manner and those physical volumes to be reclaimed.
Note: The number of virtual volumes that can be recovered is dependent on the number of FC 5270 licenses installed on the TS7700 used for recovery. Additionally, a recovery of more than two million virtual volumes must be performed by a TS7700 Tape Attach operating with a 3957-V07 or 3957-VEC and with microcode level 8.30.0.xx or later.
Erase all existing virtual volumes during recovery
This check box is shown if virtual volume or physical volume data is present in the database. A Copy Export Recovery operation will erase any existing data. No option exists to retain existing data while performing the recovery. You must check this check box to proceed with the Copy Export Recovery operation.
Submit
Click this button to initiate the Copy Export Recovery operation.
Confirm Submission of Copy Export Recovery
You are asked to confirm your decision to initiate a Copy Export Recovery option. Click OK to continue with the Copy Export Recovery operation. Click Cancel to abandon the Copy Export Recovery operation and return to the Copy Export Recovery page.
Password
Your user password. If you checked the Erase all existing virtual volumes during recovery check box, the confirmation message includes the Password field. You must provide a password to erase all current data and proceed with the operation.

Canceling a Copy Export Recovery operation in progress
You can cancel a Copy Export Recovery operation that is in progress from the Copy Export Recovery Status page.