Deactivating legacy backups of SQL Server databases
IBM Storage Protect deactivates an SQL database backup as a part of IBM Storage Protect policy management. Data backups are typically deactivated when an SQL database is deleted from the SQL Server as part of the scheduled backup processing.
Before you begin
The SQL database that you want to deactivate must be
a legacy backup. You cannot use this procedure to deactivate VSS backups. The Delete action is
available in the Actions pane when you select a VSS backup from the Recover view.About this
task
For legacy backups, you can deactivate any or all of the following backup object
types: full, differential, copyfull, log, file, group, or set. You can also deactivate any object or
object type that is older than a specified number of days. When you deactivate
database backups, all copy group parameters, which control how backup versions are generated,
located, and expired, are inspected. Any existing backups on IBM Storage Protect server are subject
to deletion, as specified by relevant policy settings.
Tip: After a full
SQL backup, all preceding copy-only full, file, group and differential backups stop adhering to the
VERExists and RETExtra settings, even if the databases still exist on the Data Protection for SQL
Server client system. In the management class for these backup objects, set the VERDeleted and
VERExists parameters to the same value and also set the RETExtra and RETOnly parameters to the same
value to maintain consistent version-expiration behavior.
When automatic processing is insufficient, the inactivate function explicitly deactivates one or more active data backups on the IBM Storage Protect server.
Procedure