August 15, 2017
© Copyright IBM Corporation, 2017 Page 65 of 117
At this point, load the copy exported physical volumes into the library. It is likely that there are multiple sets
of physical volumes that have been exported from the source TS7700 over time. All of the exported stacked
volume from the source TS7700 must be loaded into the library. If multiple pools were exported and you
want to recover with the volumes from these pools, load all sets of the volumes from these pools. Just be
sure the volser you provided is from the latest pool that was exported as it will then have the latest overall
database backup copy.
Note: You need to make sure that all of the copy exported physical volumes to be used in the recovery have
been added to the library prior to continuing with the recovery process. This means that they must have been
recognized by the library and are now known by the TS7700. One way to check is to use the search library
manager database function on pre 8.5.x.x systems and systems with a 3494 library attached. On 8.5.x.x and
higher systems, choose the Physical Volumes Search panel from the MI. For example, if you had 73
physical volumes that were marked copy exported, you would see that all 73 volumes are in the database.
Any volumes not added to the library will be flagged as manually ejected.
Note: If your library is a 3494 and you had already loaded the copy exported physical volumes in to the
library prior to beginning the recovery process and had executed the erasure step, all of the physical volume
database records for the library partition associated with the recovery TS7700 will have been erased. You
will need to perform a re-inventory operation on the library to restore those records before proceeding.
Note: Do not add any physical scratch volumes at this time, do that after the copy export recovery operation
has completed and you are ready to bring the recovery TS7700 online to its attached hosts.
Note: If you specified the copy export accelerator option (LMTDBPVL) when performing the export, only a
subset of the tapes that were exported will have a valid database backup that can be used for recovery. If a
tape that is selected for recovery does not have the backup the user will get the following error: “The
database backup could not be found on the specified recovery volume”.
Once you have added all of the physical volumes into the library and they are now known to the TS7700,
you use the above page to enter the volume serial number of one of the copy exported volumes from the last
set exported from the source TS7700 that has a valid backup. It will contain the last database backup copy
and that will be used to restore the recovery TS7700’s database. The easiest place to find a volume to enter
is from the status file records on export list file volume from the latest copy export operation.
If you are using copy export recovery to perform a disaster recovery test, you will likely want to leave the
“Disaster Recovery Test Mode” checkbox checked. The normal behavior of the TS7700 storage
management function, when a logical volume in the cache is unloaded, is to examine the definitions of the
storage management constructs associated with the volume. If the volume had been written to while it was
mounted, the actions defined by the storage management constructs are applied. If the volume had not been
modified, actions are only taken if there has been a change in the definition of the storage management
constructs since the last time the volume was unloaded. For example, if a logical volume is assigned to a
storage group which had last had the volume written to pool 4 and either the storage group was not
explicitly defined on the recovery TS7700 or specified a different pool, on the unload of the volume, a new
copy of it will be written to the pool determined by the new storage group definition, even though the
volume was only read. If you are just accessing the data on the recovery TS7700 for a test, you would not
want the TS7700 to recopy the data. Leaving the checkbox checked causes the TS7700 to bypass its
checking for a change in storage management constructs.
Another consideration with just running a test is reclamation. Running reclamation while performing a test
will require scratch physical volumes and expose the copy exported volumes to being re-used once
reclaimed. By leaving the “Disaster Recovery Test Mode” checkbox checked, reclaim is not performed.
To Next Page
Loading...
Need help?
General
