After duplicating full VMware images, block-level incremental backups based on full backups may expire earlier than expected when Copy 1 of the full backup expires.

Article:TECH159482  |  Created: 2011-05-05  |  Updated: 2011-12-20  |  Article URL http://www.symantec.com/docs/TECH159482
Article Type
Technical Solution

Product(s)

Subject

Issue



Document History:

December 20, 2011: This document was updated with a fix announcement.  See Solution below.

 

Introduction:

When performing block-level incremental backups (BLIBs) for VMware backups, incremental images are tied to "Copy 1" of a full backup and expire when that copy expires.  This means that there is a potential for still valid incremental images to be expired after Copy 1 of their associated full backup is duplicated and then expired, but before the duplicated full backup(s) ("Copy 2" and above) have expired.

 

 


Error



When attempting to restore from a block level incremental backup, it is discovered that the image no longer exists, even though duplicate full backups exist which have not reached their respective retention levels.  This may lead to results where the only available means for restoration of a VMware backup are at an earlier point in time than expected because the restoration must be taken from a previous full backup.

 

 


Environment



What is Affected:

This issue affects all released versions of NetBackup for VMware through version 7.1.0.2 on all supported platforms.

 

How to Determine if Affected:

If Perform block level incremental backups is enabled on a VMware policy and duplications are being performed against images in that policy, this issue may be experienced.


Cause




Solution



The formal resolution to this issue (Etrack 2245805) is included in the following release:

  • NetBackup for VMware 7.1 Release Update 3 (7.1.0.3)

More information on the NetBackup 7.1.0.3 release is available in the Related Article below. 

Workaround:

Reconfigure affected policies to either not perform block level incremental backups, or not perform duplication of the full backups.

 

If this workaround is unfeasible, please contact Symantec technical support, referencing this document ID and Etrack 2245805 to determine if an Emergency Engineering Binary (EEB) replacement for bpdbm may be available.

 

Best Practices:
Symantec strongly recommends the following best practices:
1. Always perform a full DR backup prior to making any changes to your environment.
2. Always make sure that your environment is running the latest version and patch level.
3. Perform periodic "test" restores.
4. Subscribe to technical articles.

How to Subscribe to Email Notification:
Directly to this Article:
Subscribe to this article by clicking on the Subscribe via email link on this page to receive notification when this article is updated with Release Information.

Software Alerts:
If you have not received this TechNote from the Symantec Email Notification Service as a Software Alert, you may subscribe via email and/or RSS using the links provided at the following page:
 http://www.symantec.com/business/support/index?page=content&key=15143&channel=ALERTS 


Supplemental Materials

SourceETrack
Value2245805
Description

Incrmental backups are expired early.




Article URL http://www.symantec.com/docs/TECH159482


Terms of use for this information are found in Legal Notices