When performing Synthetic Backups using Microsoft Change Journal option, renamed files may not be available for restore

Problem

When performing Synthetic Backups using Microsoft Change Journal option, renamed files may not be available for restore.

Solution

Introduction:

In certain scenarios specific files can't be restored from Synthetic backups if the option "Use the Microsoft Change Journal if available" is selected in the Synthetic Backup templates.


What is Affected:
The issue outlined herein occurs only when the following conditions are met:

If the following versions are installed:

Backup Exec 2010 revision 2896

AND

1. The files in question were renamed
2. The Backup Template has the "Microsoft Change Journal" setting enabled for the volume in question (Option not on by default)
3. A Synthetic incremental job is being performed.

For example, a file named 123.txt is renamed to test123.txt on a server that is protected by a Synthetic backup job policy and has Microsoft Change Journal enabled. The file test123.txt would be missing from the restore selection list of the Synthetic backup set and unavailable for restore.



Determining Your Product Version
The installed version of Backup Exec can be verified by selecting the "About Backup Exec" option from the Help menu.

Severity: High
Probability: Medium
(For information on severity and probability levels, refer to TechNote 305269)

How to Determine if Affected
If a restore is attempted from Synthetic Backup sets and renamed files are missing from the restore selections.

WORKAROUND
Disable the Microsoft Change Journal on servers that are protected by synthetic backup job policy.


RESOLUTION

This issue has been addressed in Backup Exec 2010 Hotfix 355131 and is also included in the latest available service pack for Backup Exec 2010 too.

http://www.symantec.com/docs/TECH130777


NOTE: A synthetic baseline-full backup is required after installing this hotfix if Microsoft Change Journal is used.



Best Practices:


Symantec strongly recommends the following best practices:
1. Always perform a full backup prior to and after 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.
 


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)