IC68608: FLASHCOPY MANAGER FOR EXCHANGE DIFFERENTIAL AND INCREMENTAL BACKUPS ARE NOT MARKED AS INACTIVE AFTER A FULL BACKUP

Version 2.2 IBM Tivoli Storage FlashCopy Manager
IBM Tivoli Storage Manager (TSM) Client 6.2.2 Downloads and READMEs

APAR status

• Closed as fixed if next.

Error description

• FlashCopy Manager for Exchange Differential and Incremental
  backups are not marked as inactive after a FULL backup when
  /BACKUPDESTination=BOTH is used.
  .
  Backup objects may not be marked as inactive when using
  /BACKUPDESTination=BOTH for Differential and Incremental backups
  after a FULL Backup is performed. The steps to recreate this
  scenario are:
  .
  1) Perform a FULL VSS backup of an Exchange storage group
  (Exchange 2003, 2007) or Exchange Database (Exchange 2010)
  .
  2) Perform Differential VSS backup of the same Exchange storage
  group/Database with the Backup Destination defined as BOTH
  .
  3) Perform another Differential VSS backup of the same Exchange
  storage group/Database  with the Backup Destination defined as
  BOTH
       --> At this point: #2 should be marked as Inactive
  .
  4) Perform a FULL VSS backup of the same Exchange storage
  group/Database
      --> At this point: #1, #2, and #3 should be marked as
  Inactive
  .
  Platforms affected:  All FlashCopy Manager for Exchange
  and Data Protection for Exchange environments.
  .
  Initial Impact: Medium
  .
  Local Fix: None.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  .
  All FlashCopy for Exchange 2.1 and 2.2.0 customers
  and
  All Data Protection for Exchange 6.1.1 and 6.1.2 customers
  .
  that perform Differential and/or Incremental backups with the
  /BACKUPDESTination=BOTH option.
  .
  ****************************************************************
  PROBLEM DESCRIPTION:
  .
  See the ERROR DESCRIPTION section of this APAR.
  ****************************************************************
  RECOMMENDATION:
  .
  Apply fixing level when available. The fix for this APAR is
  expected to be fixed by the following delivery vehicles:
  .
  - The V6.2.1 TSM Backup-Archive Client
  - The V2.2.1 VSS Requestor component of Tivoli Storage FlashCopy
  Manager
  .
  Note: the the fixing delivery vehicles and levels are subject to
  change at the discretion of IBM.
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

• ****************************************************************
  PROBLEM CONCLUSION:
  Before applying this fix, Incremental and / or Differential
  backups created using the /BACKUPDESTination=BOTH option are not
  properly versioned after a FULL backup because the backups older
  than the most recent backup are not marked as inactive.
  Therefore over time, it is possible to run out of storage space
  in the location designated for storing backups (TSM or local)
  because inactive backup versions are never expired / deleted
  once reaching the retention values defined for your environment.
  .
  The fix for this APAR has modified the code so that Incremental
  and Differential backups are correctly marked as inactive and
  processed for deletion from storage.
  .
  After applying the fix, any Differential and / or Incremental
  backups that were incorrectly left in the active state will be
  inactivated correctly once a new FULL backup is performed.
  .
  Depending on the number of inactive backups, the first
  expiration performed could take longer than what is usually
  seen for your environment.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IC68555

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R61W PSN

     UP