APAR status
Closed as program error.
Error description
There is a design limitation in the current release of Tivoli Storage Manager for Mail: Data Protection for Exchange which has to do with management of the backup objects in Exchange 2010 DAG environments. . An Exchange 2010 DAG environment is a high-availability solution where databases are replicated to multiple Exchange servers. There is always one "active" database and from 0 to 15 "passive" copies of that database on various servers within the DAG. The "active" database is the one that is providing mail services to the end users. The "passive" copies are in standby mode ready to become active at any point in time. Exchange 2010 backups for any given database can be performed on any server in the DAG. . The Data Protection for Exchange limitation has to do with way that the Data Protection for Exchange uses the VSS name space to create the object names on the TSM Server. The object naming has the Exchange server name in it. The object naming also has an indicator that it was from an "active" or "passive" copy. Since both the Exchange server name and the "active" or "passive" indicator is in the object naming, DAG environment backups are being managed as "different" objects on the Tivoli Storage Manager (TSM) Server rather than managed as the same database backup regardless of: - which Exchange Server they were backed up from - whether they were backed up from the passive or the active copy of the database. . Because backups are being managed as separate objects, there could be too many backups retained for any given Exchange server. This also results in the utilization of more storage space than would otherwise be required if a fewer number of backups were retained. . Platforms affected: All Windows Initial Impact:Medium
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Users of Data Protection for Exchange * * 6.1.3.x with Exchange 2010. * **************************************************************** * PROBLEM DESCRIPTION: SEE ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: Apply fixing level when available. This fix * * is projected to be available in 6.1.3.3. * ****************************************************************
Problem conclusion
A new option has been added to the TDPEXCC DELETE BACKUP command that will allow customers to delete backups "older than" the specified number of days. It will be a command-line only option and will not have a GUI equivalent option. . This new option will enable the customer to manually delete their Exchange VSS backup objects based on the age of the backup. This action is an "on demand" activity that is used in addition to the TSM backup retention policies defined by the defined by the management class. The customer could schedule these deletions on a regular basis to remove databases that are older than their desired retention period. . The new option name is /OLDERTHAN an is used in this way: TDPEXCC DELETE BACKUP /OLDerthan=value . /OLDerthan=value is used to indicate that backups older than the number of days specified should be deleted. A day is defined by calendar date and not by a 24 hour period of time. . The parameters for this option are: . 0: A value of 0 will delete all selected backups regardless of the creation date. 1-9999: A value of 1 - 9999 will delete all backups older than the number of days specified. . Examples: . If today is July 26, 2011.... . #1: TDPEXCC DELETE BACKUP maildb1 FULL /OLDERTHAN=1 then, all FULL backups of maildb1 created on July 25, 2011, and before, are deleted. . #2: TDPEXCC DELETE BACKUP maildb1 FULL /OLDERTHAN=21 then, all FULL backups of maildb1 created on July 5, 2011, and before, are deleted. . #3 TDPEXCC DELETE BACKUP maildb1 INCREMENTAL /OLDERTHAN=21 then, all INCREMENTAL backups of maildb1 created on July 5, 2011, and before, are deleted. . #4 TDPEXCC DELETE BACKUP * FULL /OLDERTHAN=5 then, all FULL backups created on July 21, 2011, and before, are deleted. . #5 TDPEXCC DELETE BACKUP * DIFFERENTIAL /OLDERTHAN=5 then, all DIFFERENTIAL backups created on July 21, 2011, and and before, are deleted.
Temporary fix
Comments
APAR Information
APAR number
IC78938
Reported component name
TDP EXCHANGE WI
Reported component ID
5698DPXAP
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-27
Closed date
2011-09-27
Last modified date
2011-09-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
TDPEXCC
Fix information
Fixed component name
TDP EXCHANGE WI
Fixed component ID
5698DPXAP
Applicable component levels
R61W PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSTG2D","label":"Tivoli Storage Manager for Mail"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"61W","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
27 September 2011