Deleting backups

Contributors Download PDF of this page

You must delete backups when you no longer need them, which frees the space those backups occupy. If you remove backups, you reduce the chance of reaching the limit of 255 Snapshot copies per volume.

  • You must ensure that the backup was not used to create a clone.

When you delete a protected backup, SnapManager deletes the backup from secondary storage and the SnapManager repository. The following table shows the actions taken on both the primary and secondary storage when you delete a local backup:

Protection state Local status Action on primary storage Action on secondary storage Explanation

Not requested (to be protected)

Exists

Deletes the Snapshot copies

No action required

SnapManager deletes the local backup.

Freed

No action required

No action required

The local backup is already freed. If you delete a freed backup, the backup metadata is removed from the repository.

Not protected

Exists

Deletes the Snapshot copies

No action required

SnapManager deletes the local backup whether or not it has been protected.

Freed

No action required

No action required

The local backup is already freed. If you delete a freed backup, the backup metadata is removed from the repository.

Protected

Exists

Deletes the Snapshot copies

SnapManager deletes the backup on secondary storage

SnapManager deletes the local backup and secondary copies.

Freed

No action required

If you attempt to delete a backup that is protected by secondary storage, the Snapshot copies might be marked for deletion and are deleted later by Protection Manager.

You can delete backups retained on an unlimited basis without changing the retention class.

You can optionally collect the dump files after the successful or failed backup delete operation.

If you want to delete the archive log backups, you need to check for the retention duration set for the archive log backup. If the archive log backup is within the retention duration and the archive log files are required for recovery of a restored database, you cannot delete the archive log backup.

  1. Verify that the operations are complete by entering the following command: smo operation list -profileprofile_name-quiet-verbose

  2. To delete a backup, enter the following command:smo backup delete -profile profile_name [-label label [data | -archivelogs] | -idid | -all] [-force] [ -dump] [-quiet | -verbose]

    Use the -force option to force the removal of the backup. Forcing the removal of a backup that has incomplete operations might leave the backup in an inconsistent state.