Administrator's Reference

AUDIT VOLUME (Verify Database Information for a Storage Pool Volume)

Use the AUDIT VOLUME command to check for any inconsistencies between database information and a storage pool volume. During the audit process, the server sends processing information to the activity log and the server console.

While an audit process is active, clients cannot restore data from the specified volume or store new data to that volume.

This command can be used to audit a volume assigned either to a primary storage pool or to a copy storage pool. If a file on a volume is detected with integrity errors, handling of the file will depend on the type of storage pool to which the volume belongs, whether the FIX option specified on this command, and whether the file is also stored on a volume assigned to other pools.

You cannot audit a volume if the volume specified on this command is being deleted from a primary or copy storage pool.

If the AUDIT VOLUME command does not detect data-integrity errors for a file that had previously been marked as damaged, the state of the file is reset so that the file can be used. This provides a means for resetting the state of damaged files if it is determined that the errors were caused by correctable hardware problems such as a dirty tape head.

Do not use the AUDIT VOLUME command with FIX=YES if a restore process (RESTORE STGPOOL or RESTORE VOLUME) is running. The AUDIT VOLUME command could cause the restore to be incomplete.

To display information about the contents of a storage pool volume, use the QUERY CONTENT command.

This command creates a background process that can be canceled with the CANCEL PROCESS command. To display information on background processes, use the QUERY PROCESS command.

Privilege Class

To issue this command, you must have system privilege, unrestricted storage privilege, or restricted storage privilege for the storage pool to which the volume is defined.

Syntax

                           .-Fix--=--No-------.
>>-AUDit Volume--volname---+------------------+----------------->
                           '-Fix--=--+-No--+--'
                                     '-Yes-'
 
     .-SKIPPartial--=--No-------.  .-Quiet--=--No-------.
>----+--------------------------+--+--------------------+------><
     '-SKIPPartial--=--+-No--+--'  '-Quiet--=--+-No--+--'
                       '-Yes-'                 '-Yes-'
 

Parameters

volname

Specifies the name of the storage pool volume you want to audit. This parameter is required.

Fix=fixvalue

Specifies how ADSM resolves any logical inconsistencies between the database inventory and the specified storage pool volume. This parameter is optional. The default value is NO.

The actions ADSM performs based on this parameter also depend on whether the volume is assigned to a primary or a copy storage pool.

Primary Storage Pool

For a volume in a primary storage pool, the value for the FIX parameter has the following effects.

Fix=No

ADSM reports, but does not delete, any database records that refer to files found with logical inconsistencies.

If the AUDIT VOLUME command detects a data-integrity error in a file:

• ADSM marks the file as damaged in the database. If a backup copy is stored in a copy storage pool, the file can be restored using the RESTORE VOLUME or RESTORE STGPOOL command.

• If the file is a cached copy, references to the file on this volume can be deleted by issuing the AUDIT VOLUME command and specifying FIX=YES. If the physical file is not a cached copy, and a duplicate is stored in a copy storage pool, it can be restored using the RESTORE VOLUME or RESTORE STGPOOL command.

If the AUDIT VOLUME command does not detect a data-integrity error in a file that had previously been marked as damaged, the state of the file is reset so that the file can be used. This provides a means for resetting the state of damaged files if it is determined that the errors were caused by correctable hardware problems such as a dirty tape head.

Fix=Yes

ADSM fixes any inconsistencies as they are detected.

If the AUDIT VOLUME command detects a data-integrity error in a file:

• If the physical file is a cached copy, ADSM deletes the database records that refer to the cached file. The primary file is stored on another volume.

• If the physical file is not a cached copy, and the file is also stored in one or more copy storage pools, the error will be reported and the physical file marked as damaged in the database. The physical file can then be restored using the RESTORE VOLUME or RESTORE STGPOOL command.

• If the physical file is not a cached copy, and the physical file is not stored in a copy storage pool, each logical file for which inconsistencies are detected will be deleted from the database.

If the AUDIT VOLUME command does not detect a data-integrity error in a file that had previously been marked as damaged, ADSM resets the state of the file so that it can be used. This provides a means for resetting the state of damaged files if it is determined that the errors were caused by correctable hardware problems such as a dirty tape head.

Copy Storage Pool

For a volume in a copy storage pool, the value for the FIX parameter has the following effect if ADSM detects a file with integrity errors:

Fix=No

The error is reported and the physical file copy is marked as damaged in the database.

Fix=Yes

References to the physical file on the audited volume are deleted. ADSM deletes any database records that point to a physical file on the audited volume that does not exist.

SKIPPartial=skipvalue

Specifies whether ADSM ignores files that span multiple storage pool volumes (skipped files), when performing the audit for the specified storage pool volume. This parameter is optional. The default value is NO. When performing an audit operation on a sequential access media volume, this parameter prevents additional sequential access media mounts that may be necessary to audit any skipped files. Possible values are:

No

Specifies that ADSM audits physical files that span multiple volumes when performing an audit operation on a specified volume. For sequential access volumes, multiple volumes can be mounted.

Yes

Specifies that ADSM only audits complete physical files that are stored on the volume to be audited. For sequential access volumes, only the specified volume is mounted. The status of any skipped files is unknown.

Quiet=quietvalue

Specifies whether ADSM sends detailed informational messages to the activity log and the server console about irretrievable files on the volume. This parameter is optional. The default value is NO. Possible values are:

No

Specifies that ADSM sends detailed informational messages and a summary report to the activity log and the server console. Each message contains the node, file space, and client name for the file.

Yes

Specifies that ADSM only sends a summary report to the activity log and the server console.

Usage Notes

Unless you specify SKIPPARTIAL=YES, ADSM attempts to process each file stored on the volume, including files that span into and out of other volumes. In order to audit files that span multiple volumes, the following conditions must be true:

• For sequential access volumes, the additional sequential access volumes must have an access mode of read/write or read-only.

• For random access volumes, the additional volumes must be online.

Examples

Task

Verify that the database information for storage pool volume PROG2 is consistent with the data stored on the volume. ADSM fixes any inconsistencies that are found.

Command:

audit volume prog2 fix=yes

Related Commands

Table 14. Commands Related to AUDIT VOLUME

Command	Description
CANCEL PROCESS	Cancels a background server process.
QUERY CONTENT	Displays information about one or more files currently residing in a storage pool volume.
QUERY PROCESS	Displays information about one or all background server processes.
QUERY VOLUME	Displays information about one or more storage pool volumes.