When changing from legacy backups to VSS backups add the correct VSSPOLICY statements to the configuration file or the default management class for the policy domain is used

Technote (troubleshooting)


Problem(Abstract)

If you change from legacy backups to VSS backups, but do not add the correct VSSPOLICY statements to the configuration file, the default management class for the policy domain is used. This default management class is specific to the node's domain. The default management class specifies expiration parameters, including number of days and number of versions.

Symptom

This problem can affect any user of Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange, Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL, Tivoli Storage FlashCopy Manager: FlashCopy Manager for Microsoft Exchange, and Tivoli Storage FlashCopy Manager: FlashCopy Manager for Microsoft SQL Server.

VSS backups expire according to the parameters set in the VSSPOLICY statements. If there are no VSSPOLICY statements, the default management class for the node's domain is used. Expiration parameters are specified in the default management class. These parameters might differ from the preexisting legacy backup expiration parameters. For example, backups might be set to expire at an earlier date.


Cause

The problem can occur when changing from legacy backup type to VSS backup type and not correctly entering the VSSPOLICY statements in the configuration file. Legacy backups are bound to management classes through the INCLUDE statements specified in the options file. VSS backups are bound to policies through the VSSPOLICY statements in the configuration file.

The following scenario gives you a specific example when this problem is likely to occur: For customers moving from a Microsoft Exchange 2003 to a Microsoft Exchange 2007 environment, and using the Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server software to protect data, when changing the type of backup, verify the backup expiration date is correct.


Resolving the problem

When you change from legacy backups to VSS backups, pay attention to the VSSPOLICY statements set for the backup.


For VSS backups, VSSPOLICY statements are used to associate VSS backups with management classes. These VSSPOLICY statements are entered in the configuration file (for example, tdpexc.cfg, tdpsql.cfg, and fcmcfg.xml).

A configuration file can include multiple VSSPOLICY statements. The configuration file is read from the bottom up. If you are familiar with the Tivoli Storage Manager backup-archive client configuration file, the VSSPOLICY statements in the tdpexc.cfg / tdpsql.cfg / fcmcfg.xml file are read like the INCLUDE statements configured in the dsm.opt file.

If there are no VSSPOLICY statements included in the configuration file, or if the VSSPOLICY statements do not match the type of backup that is set up, the default management class for the policy domain is used. Backup expiration parameters for the default management class might differ from the settings used for preexisting legacy backups. For example, the backup expiration period might be set to 30 days. This setting means that after 30 days, the backup is deleted. Check the parameters to verify the backups expire according to the business needs of your environment.

Any policy changes entered in the tdpexc.cfg / tdpsql.cfg / fcmcfg.xml file require that you restart the Tivoli Storage Manager Client Acceptor Daemon (CAD), Tivoli Storage Manager Remote Client Agent (DSMAgent), and the Tivoli Storage Manager Scheduler Service for Exchange. If the DSMAgent service state is set to Manual (Started), stop the service. The DSMAgent service starts when a VSS backup is initiated, but if the service is started and you change the policy settings, the policy settings do not take effect until you restart the service.

Sample VSSPOLICY statements

The following code sample presents the syntax of a VSSPOLICY statement:

VSSPOLICY srv-name "stg-grp-name" backup-type backup-dest mgmtclass

The Exchange / SQL server name is defined by the srv-name variable. You can enter the wildcard character (*) to match all Microsoft Exchange or Microsoft SQL servers.

The storage group name is defined by the stg-grp-namevariable. You can enter the wildcard character (*) to match all Microsoft Exchange or Microsoft SQL server groups. Because the name can include a space, use the quotation marks to encapsulate the storage group name.

The backup-typevariable specifies the backup type. For example, FULL or COPY or the wildcard character (*) to match all backup types.

The backup-dest variable specifies the backup destination. The options are TSM to backup to Tivoli Storage Manager or LOCAL for a backup to a local disk or the wildcard character (*) to match both backup types.

The mgmtclassvariable specifies the Tivoli Storage Manager management class that is used to bind the types of specified backups.

The following code sample presents an example of a VSSPOLICY statement. This code sample is part of the sample configuration file that is included with the software that you installed. In this example the VSSPOLICY statement is commented out. To make the VSSPOLICY statement effective, uncomment the VSSPOLICY statement by removing the initial asterisk character (*).

----------------------------------------------------------------------------
* Sample VSSPOLICY Statements

* ---------------------------

* These statements are used to bind VSS backups to specific TSM

* Server management classes. Adjust the statements to meet your needs

* and remove the leading asterisks to make them operational.

* Note: Matching of these policy bindings are from the bottom up.

**********************************************************************

* Server Storage Group Name BU Type BU Dest. Mgmt Class

* ------ ------------------ ------- ------- ----------

VSSPOLICY * * FULL TSM REDBOOK_TSM

VSSPOLICY * * COPY TSM REDBOOK_TSM_COPY
VSSPOLICY * * COPY LOCAL REDBOOK_COPY

VSSPOLICY * * FULL LOCAL REDBOOK_LOCAL

VSSPOLICY * "Human Resources" FULL LOCAL MCLASS3

VSSPOLICY SERVER1 "Accounting" * LOCAL MCLASS2

VSSPOLICY SERVER1 "SG1 " * TSM REDBOOK1

----------------------------------------------------------------------------

In this example, the following policy rules are specified:

  • Any VSS backups of the SG1 storage group on the Exchange server SERVER1 to Tivoli
    Storage Manager are bound to the management class REDBOOK1.
  • Any VSS backups of the Accounting storage group on the Exchange server SERVER1 to
    LOCAL are bound to the management class MCLASS2.
  • Full VSS backups of the Human Resources storage group on any Exchange server to
    LOCAL are bound to the management class MCLASS3.
  • Full VSS backups of any other storage group on any other Exchange server to LOCAL
    are bound to the management class REDBOOK_LOCAL.
  • Copy VSS backups of any other storage group on any other Exchange server to LOCAL
    are bound to the management class REDBOOK_COPY.
  • Copy VSS backups of any other storage group on any other Exchange server to Tivoli
    Storage Manager are bound to the management class REDBOOK_TSM_COPY.
  • Full VSS backups of any other storage group on any other Exchange server to Tivoli
    Storage Manager are bound to the management class REDBOOK_TSM.
  • This policy is complete. Any type of backup matches a rule because of the
    wildcard VSSPOLICY statements at the top of the file. Use these types
    of statements so that you explicitly state what management class is used.


Cross reference information
Segment Product Component Platform Version Edition
Storage Management Tivoli Storage FlashCopy Manager FlashCopy Manager for Microsoft Exchange Windows
Storage Management Tivoli Storage Manager for Databases Data Protection for MS SQL Windows Version Independent
Storage Management Tivoli Storage FlashCopy Manager FlashCopy Manager for Microsoft SQL Server Windows

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager for Mail
Data Protection for MS Exchange

Software version:

Version Independent

Operating system(s):

Windows

Reference #:

1622249

Modified date:

2013-12-12

Translate my page

Machine Translation

Content navigation