Skip to main content
SnapManager Oracle

The smo backup verify command

Contributors
PDFs

You can run the backup verify command to see if the backup is in a valid format for Oracle.

Syntax

        smo backup verify
-profile profile_name
[-label backup_name \| \[-id guid\]
\[-retain \{-hourly \| -daily \| -weekly \| -monthly \| -unlimited\}\]
\[-force\]
\[-dump\]
\[-quiet \| -verbose\]

Parameters

  • -profile profile_name

    Specifies the profile for which you want to verify a backup. The profile contains the identifier of the database and other database information.

  • -id guid

    Verifies the backup with the specified GUID. The GUID is generated by SnapManager when you create a backup. You can use the smo backup list command to display the GUID for each backup.

  • -label label_name

    Verifies the backup with the specified label.

  • -dump

    Collects the dump files after the successful or failed backup verify operation.

  • -force

    Forces the database into the necessary state to perform the verify operation.

  • -quiet

    Displays only error messages in the console. The default is to display error and warning messages.

  • -verbose

    Displays error, warning, and informational messages in the console.

Example

The following is an example of verifying the backup:

smo backup verify -profile SALES1 -label full_backup_sales_May -quiet
DBVERIFY - Verification starting : FILE = +SMO_1_1161675083835/smo/datafile/data.277.582482539 ...

Related information

Verifying database backups