The smo backup delete command
Contributors Download PDF of this page
You can run the backup delete command to remove backups that are not automatically removed, such as backups that were used to create a clone or backups that failed. You can delete backups retained on an unlimited basis without changing the retention class.
smo backup delete -profile profile_name [-label label \[-data \| -archivelogs\] \| \[-id guid \| -all\] -force \[-dump\] \[-quiet \| -verbose\]
Specifies the database associated with the backup you want to remove. The profile contains the identifier of the database and other database information.
Specifies 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.
Specifies the backup with the specified label. Optionally, specify the scope of the backup as data file or archive log.
Specifies the data files.
Specifies the archive log files.
Specifies all backups. To delete only specified backups instead, use the -id or -label option.
Collects the dump files after a successful or failed backup delete operation.
Forces the removal of the backup. SnapManager removes the backup even if there are problems in freeing the resources associated with the backup. For example, if the backup was cataloged with Oracle Recovery Manager (RMAN), but the RMAN database no longer exists, including -force deletes the backup even though it cannot connect with RMAN.
Displays only error messages in the console. The default is to display error and warning messages.
Displays error, warning, and informational messages in the console.