Configuring Tivoli Storage Manager policy to set automatic expiration and version control (VSS and legacy backups)

With Data Protection for SQL Server, you can use Tivoli® Storage Manager policy to set automatic expiration and version control.

About this task

You can set automatic policy for data backups by editing the Data Protection for SQL Server options file, or by specifying the policy statements in Microsoft Management Console (MMC). If you edit the options file, use INCLUDE and EXCLUDE statements to define the files that you want to automatically process, and to assign specific management classes to files by using object naming conventions.

Setting automatic expiration for VSS backups

Procedure

Complete one of the following steps:
- Specify the VSSPOLICY statement in your Data Protection for SQL Server configuration file
- Specify the VSSPOLICY statement in MMC (Properties > VSS Policy Binding).
You cannot specify VSSPOLICY statements by issuing the tdpsqlc set command.
Specify the following information in the VSSPOLICY statement:
```
VSSPOLICY srvname dbname backuptype backupdest mgmtcls
```
where:
srvname

Specify the name of the SQL Server or wildcard character (*)

dbname

Specify the name of the database or wildcard character (*)

backuptype

Specify the backup type as FULL or as a wildcard character (*). When you specify a wildcard character for backuptype, a FULL backup type is completed because you can run only full backup types.

backupdest

Specify the backup destination to be the Tivoli Storage Manager server, a local serve, or a wildcard character (*)

mgmtcls

Specify the management class name for the backup type.

Setting automatic expiration for legacy backups

About this task

Metadata is stored as a data object on the Tivoli Storage Manager server. You can migrate metadata to removable media if that action complies with Tivoli Storage Manager policy. A Data Protection for SQL Server backup object name comprises a series of qualifiers separated by \.

Procedure

Ensure that metadata is available to query without causing a volume mount.
Adhere to the INCLUDE and EXCLUDE syntax for object naming as follows:
```
include "objectNameSpecification" [ManagementClassName]
exclude "objectNameSpecification"
```
where:
objectNameSpecification is:
```
SqlServerName[\InstanceName]\dataType\...\DatabaseName
[\typeInfo]\backupType*
                    
```
dataType is:

meta | data

typeInfo is:

LogicalFileName (for file backup type)
GroupName (for group backup type)

... (for log and set backup types)

not used for full and diff backup types

backupType is:
```
full | copyfull | diff | log | group | file | set
```
The following are examples of individual objectNameSpecifications in INCLUDE and EXCLUDE statements:
SqlServerNames:

SQL2008, SQL2012, SQL2014

InstanceNames:

INST1, INST2

DatabaseNames:

Db1, Db2, Db3

GroupNames:

g1, g2, g3

LogicalFileNames:

f1, f2, f3