August 15, 2017
© Copyright IBM Corporation, 2017 Page 76 of 117
candidate for reclaim, because although it contains 78.2% active data, that is 78.2% of the 509 MBytes that
were written to the volume when it was exported, so there is actually less active data on it than there is on
volume JA5204 (JA5204 has over 72,000 active MBytes versus JA5328 which has only 398 active
MBytes).
The second method is by using the host console request command, Library Request with keysords
PVOL,XXXXXX; where XXXXXX is the physical volume volser, to ask for the information about a
specific physical volume that you know has been copy exported. The information returned includes the
number of Mbytes of data written to the volume when it was exported and the current percentage of that
data that is active. As with the information provided in the status file on the export list file volume, you can
use this information to decide whether a volume should be considered a candidate for reclaim or is empty of
any active data. However, the library request showing “EMPTY” indicates the exported physical volume is
empty in current database. It can be inconsistent with the database backup gotten at previous Copy Export
operation. Hence, the information gotten by this library request should not be used for decision of returning
empty exported physical volumes to the library fore re-use after the next export operation completes and the
physical volumes are taken off-site. Here is an example of the data returned for a physical volume:
PHYSICAL VOLUME INFORMATION V1
PHYSICAL VOLUME: AB0203
MEDIA TYPE: JA
DRIVE MODE: E05
FORMAT: TS7700
VOLUME STATE: COPY-EXPORTED
CAPACITY STATE: FULL
CURRENT POOL: 1
MBYTES WRITTEN: 497413
% ACTIVE DATA: 85.2
LAST INSERTED: 2006-12-23 19:34:27
WHEN EXPORTED: 2007-4-12 08:51:31
MOUNTS: 34
LOGICAL VOLUMES: 254
ENCRYPTED: N
The third method is to use the BVIR-Physical Volume Status Pool xx function, where xx is the pool you
want the information on. For each physical volume in the specified pool, a lot of information is returned.
The particular fields of interest for copy export are whether the volume has a state of copy-exported, the
amount of data in MBytes that was written to the volume when it was exported and the current percentage
of that data that is active. BVIR showing “EMPTY” about the exported physical volume indicates it is
empty in current database. It can be inconsistent with the database backup gotten at previous Copy Export
operation. Hence, the information gotten by this BVIR should not be used for decition of returning empty
exported physical volumes to the library for re-use. Refer to the white paper - IBM Virtualization Engine
TS7700 Series Bulk Volume Information Retrieval User’s Guide for specifics about the physical volume
status pool request.
After copy export recovery has been performed, it is important to remember that the physical volumes used
in the recovery will still have a status of copy-exported and will be included in the status file on the export
list file volume even though they are resident in the source TS7700. You can differentiate the new copy-
exported volume from the ones used in a recovery by looking at the data-time value for when they were last
exported. The new ones would have a data-time value after the copy export recovery was performed.
To Next Page
Loading...
Need help?
General
