| Task | Required Privilege Class |
|---|---|
| Display information about volumes | Any administrator |
You can query the server for general information about storage pool volumes, or you can view a detailed report to evaluate:
To request general information about all volumes defined to the server, enter:
query volume
The following shows an example of the output of this standard query. The example illustrates that data is being stored on the 8mm tape volume named ADSM01, as well as on several other volumes in various storage pools.
+--------------------------------------------------------------------------------+ | | |Volume Name Storage Device Estimated %Util Volume | | Pool Name Class Name Capacity Status | | (MB) | |------------------------ ----------- ---------- --------- ----- -------- | |/dev/raixvol1 AIXPOOL1 DISK 240.0 26.3 On-Line | |/dev/raixvol2 AIXPOOL2 DISK 240.0 36.9 On-Line | |/dev/rdosvol1 DOSPOOL1 DISK 240.0 72.2 On-Line | |/dev/rdosvol2 DOSPOOL2 DISK 240.0 74.1 On-Line | |/dev/ros2vol1 OS2POOL1 DISK 240.0 55.7 On-Line | |/dev/ros2vol2 OS2POOL2 DISK 240.0 51.0 On-Line | |ADSM00 TAPEPOOL TAPE8MM 2,472.0 0.0 Filling | |ADSM01 TAPEPOOL TAPE8MM 2,472.0 2.2 Filling | | | +--------------------------------------------------------------------------------+
To query the server for a detailed report on volume ADSM01 in the storage pool named TAPEPOOL, enter:
query volume adsm01 format=detailed
The following shows the output of this detailed query.
+--------------------------------------------------------------------------------+ | Volume Name: ADSM01 | | Storage Pool Name: TAPEPOOL | | Device Class Name: TAPE8MM | | Estimated Capacity (MB): 2,472.0 | | %Util: 26.3 | | Volume Status: Filling | | Access: Read/Write | | Pct. Reclaimable Space: 5.3 | | Scratch Volume?: No | | In Error State?: No | | Number of Writable Sides: 1 | | Number of Times Mounted: 4 | | Write Pass Number: 2 | | Approx. Date Last Written: 12/04/1996 11:33:26 | | Approx. Date Last Read: 12/03/1996 16:42:55 | | Date Became Pending: | | Number of Write Errors: 0 | | Number of Read Errors: 0 | | Volume Location: | |Last Update by (administrator): ADSMADMIN | | Last Update Date/Time: 12/02/1996 13:20:14 | | | +--------------------------------------------------------------------------------+
Here are some ways to use this report:
Check the Volume Status to see if a disk volume has been varied offline, or if a sequential access volume is currently being filled with data.
Check the Access to determine whether files can be read from or written to this volume.
The Estimated Capacity is determined by the device class associated with the storage pool to which this volume belongs. Based on the estimated capacity, the system tracks the percentage of space occupied by client files. In this example, 26.3% of the estimated capacity is currently in use.
ADSM maintains usage statistics on volumes that are defined to storage pools. Statistics on a volume explicitly defined by an administrator remain for as long as the volume is defined to the storage pool. ADSM continues to maintain the statistics on defined volumes even as the volume is reclaimed and reused. However, ADSM deletes the statistics on the usage of a scratch volume when the volume returns to scratch status (after reclamation or after all files are deleted from the volume).
In this example, ADSM01 is a volume defined to ADSM by an administrator, not a scratch volume (Scratch Volume? is No).
The Write Pass Number indicates the number of times the volume has been written to, starting from the beginning of the volume. A value of one indicates that a volume is being used for the first time. In this example, ADSM01 has a write pass number of two, which indicates space on this volume may have been reclaimed or deleted once before. Compare this value to the specifications provided with the media that you are using. The manufacturer may recommend a maximum number of write passes for some types of tape media. You may need to retire your tape volumes after reaching the maximum passes to ensure the integrity of your data. To retire a volume, move the data off the volume by using the MOVE DATA command. See "Moving Files from One Volume to Another Volume".
Use the Number of Times Mounted, the Approx. Date Last Written, and the Approx. Date Last Read to help you estimate the life of the volume. For example, if more than six months have passed since the last time this volume has been written to or read from, audit the volume to ensure that files can still be accessed. See "Auditing a Storage Pool Volume" for information about auditing a volume.
The server reports when the volume is in an error state and automatically updates the access mode of the volume to read-only. The Number of Write Errors and Number of Read Errors indicate the type and severity of the problem. Audit a volume when it is placed in error state. See "Auditing a Storage Pool Volume" for information about auditing a volume.
When you define or update a sequential access volume, you can give location information for the volume. The detailed query displays this location name. The location information can be useful to help you track volumes, for example, offsite volumes in copy storage pools.
A sequential access volume is placed in the pending state after the last file is deleted or moved from the volume. All the files that pending volumes had contained were expired or deleted, or were moved from the volume. Volumes remain in the pending state for as long as specified with the REUSEDELAY parameter for the storage pool to which the volume belongs.
Any administrator can request information about the contents of a storage pool volume. Viewing the contents of a storage volume is useful when a volume is damaged or before you do the following:
Because ADSM tracks the contents of a storage volume through its database, the requested volume need not be accessed in order to determine its contents.
The report generated by a QUERY CONTENT command shows the contents of a volume. This report can be extremely large and may take a long time to produce. To reduce the size of this report, narrow your search by selecting one or all of the following search criteria:
To view the first seven backup files on volume ADSM01 from file space /usr on client node TOMC, for example, enter:
query content adsm01 node=tomc filespace=/usr count=7 type=backup
Figure 31 displays a standard report which shows the first seven files from file space /usr on TOMC stored in ADSM01.
Figure 31. A Standard Report on the Contents of a Volume
+--------------------------------------------------------------------------------+ |Node Name Type Filespace Client's Name for File | | Name | |------------------------ ---- ---------- -------------------------------------- | |TOMC Bkup /usr /bin/ acctcom | |TOMC Bkup /usr /bin/ acledit | |TOMC Bkup /usr /bin/ aclput | |TOMC Bkup /usr /bin/ admin | |TOMC Bkup /usr /bin/ ar | |TOMC Bkup /usr /bin/ arcv | |TOMC Bkup /usr /bin/ banner | | | +--------------------------------------------------------------------------------+
The report lists logical files on the volume. If a file on the volume is an aggregate of logical files (backed-up or archived client files), all logical files that are part of the aggregate are included in the report. An aggregate file can be stored on more than one volume, and therefore not all of the logical files in the report may actually be stored on the volume being queried.
To query the server to display detailed information about the files stored on volume VOL1, enter:
query content vol1 format=detailed
Figure 32 displays a detailed report that shows the files stored on VOL1. The report lists logical files and shows whether each file is part of an aggregate file. If a logical file is stored as part of an aggregate file, the information in the Segment Number, Stored Size, and Cached Copy? fields apply to the aggregate, not to the individual logical file.
If a logical file is part of an aggregate file, the Aggregated? field shows the sequence number of the logical file within the aggregate file. For example, the Aggregated? field contains the value 2/4 for the file AB0CTGLO.IDE, meaning that this file is the second of four files in the aggregate. All logical files that are part of an aggregate are included in the report. An aggregate file can be stored on more than one volume, and therefore not all of the logical files in the report may actually be stored on the volume being queried.
For disk volumes, the Cached Copy? field identifies whether the file is a cached copy of a file that has been migrated to the next storage pool in the hierarchy.
Figure 32. Viewing a Detailed Report of the Contents of a Volume
+--------------------------------------------------------------------------------+ | Node Name: DWE | | Type: Bkup | | Filespace Name: OS2 | |Client's Name for File: \ README | | Aggregated?: No | | Stored Size: 27,089 | | Segment Number: 1/1 | | Cached Copy?: No | | | | Node Name: DWE | | Type: Bkup | | Filespace Name: DRIVE_L_K: | |Client's Name for File: \COMMON\DSMCOMMN\ AB0CTCOM.ENT | | Aggregated?: 1/4 | | Stored Size: 202,927 | | Segment Number: 1/1 | | Cached Copy?: No | | | | Node Name: DWE | | Type: Bkup | | Filespace Name: DRIVE_L_K: | |Client's Name for File: \COMMON\DSMCOMMN\ AB0CTGLO.IDE | | Aggregated?: 2/4 | | Stored Size: 202,927 | | Segment Number: 1/1 | | Cached Copy?: No | | | | Node Name: DWE | | Type: Bkup | | Filespace Name: DRIVE_L_K: | |Client's Name for File: \COMMON\DSMCOMMN\ AB0CTTRD.IDE | | Aggregated?: 3/4 | | Stored Size: 202,927 | | Segment Number: 1/1 | | Cached Copy?: No | | | | Node Name: DWE | | Type: Bkup | | Filespace Name: DRIVE_L_K: | |Client's Name for File: \COMMON\DSMCOMMN\ AB0CTSYM.ENT | | Aggregated?: 4/4 | | Stored Size: 202,927 | | Segment Number: 1/1 | | Cached Copy?: No | | Cached Copy?: No | | | +--------------------------------------------------------------------------------+