August 15, 2017
© Copyright IBM Corporation, 2017 Page 74 of 117
construct definitions, the primary physical volume pool is 1 and the secondary physical volume pool is
10. Because the ”Disaster Recovery Test Mode” checkbox was not checked, the TS7700 will follow the
new construct definitions and make copies to physical volumes in pools 1 and 10. The copy in pool 9 is
then no longer valid.
Note: The evaluation to have the TS7700 follow the new construct definitions will be performed
regardless of whether any data is actually read from the volume.
• For a logical volume that is newly written or modified
If the logical volume is newly written or is an existing one that is modified, when the volume is closed
the storage management functions will follow the new construct definitions and make copies to the
physical volumes in pool 1 and 10.
• For a logical volume that is again read
If the logical volume is read again and closed, the storage management functions will see that its prior
pool associations are the same as the new construct definitions and no further action will be taken.
Note: Reclaiming a physical volume is not enough to have the new primary or secondary copy created as
reclaim does not bring logical volumes into the cache.
The above example demonstrates that the TS7700 will not automatically create a new primary or secondary
copy of the logical volumes. You will have to, at a minimum, mount and close each logical volume to have
the TS7700 make the primary or secondary copy.
As the storage management function of the TS7700 makes new primary and secondary copies, the amount
of active data on the physical volumes with the original status of copy-exported will decrease and they will
eventually be reclaimed. Once they have been reclaimed, they must be removed from the library and then
re-inserted into the library before they will be re-used as scratch volumes.
Note: At code release level R1.3, you will have to manually remove the original copy-exported physical
volumes from the library to be able to re-insert them. They cannot be ejected through the library manager
panels. At R1.4 or later you can use the eject function of the library manager for this.
When copy export is again performed, it must now specify pool 10 and those new secondary copies in that
pool would be exported.
To Next Page
Loading...
Need help?
General
