ProblemBackup Exec 11d for Windows Servers (BEWS) Microsoft Exchange or SQL Server backups performed in conjunction with Backup Exec System Recovery 7.0 renders successful BEWS Exchange or SQL differential or incremental backups unrecoverable.
SolutionWhen BESR 7.0 is used to perform volume-level backups of Exchange or SQL Servers in conjunction with BEWS 11d, it may render the Exchange or SQL Server differential or incremental backups unrecoverable, even though the differential or incremental backups showed that they completed successfully in the job log.
This issue occurs because the Log Sequence Number (LSN) for Exchange or SQL is reset by the BESR 7.0 Full VSS (Volume Shadow Copy) Backup Job. The Exchange Transaction Log or LSN for SQL Databases is reset by the BESR Recovery Point Job, so subsequent differential or incremental backups performed by BEWS are relative to the BESR recovery point instead of the original BEWS Full backup. The subsequent differential or incremental backups are thus rendered unrecoverable by BEWS, because it is unable to use the recovery point defined by the BESR Option.
This issue occurs only if ALL of the following conditions are met:
1. Backup Exec 11d for Windows Servers is installed with the Agent for Microsoft SQL and/or Exchange
2. Backup Exec System Recovery (BESR) 7.0 is also being used to perform volume level backups of the SQL and/or Exchange volume
3. A BESR backup occurred between a BEWS Full backup and the next differential or incremental backup
Note: Open Backup Exec and go to Help/About Backup Exec to verify the installed product version.
There are two options provided in the resolution section, and one or both may be applied depending on the desired outcome.
I. (Optional) A Full VSS Backup is not enabled by default in BESR 8.0 and because of this, it does not affect the BEWS Exchange/SQL Differential Backups. If the optional upgrade to BESR 8.0 is performed, the SQL and Exchange restore operations will be successful and recoverable, but the BEWS software will not receive the update it needs for SQL and Exchange differential and incremental backups to fail when they are required to do so. Therefore if BESR is upgraded to version 8.0, BESR jobs will not need to be reconfigured, but BEWS must still be patched or upgraded.
For more information on upgrading the Backup Exec System Recovery to 8.0, review the following document:
How to get the installation source and license keys for Backup Exec System Recovery
II. (Mandatory) Apply Hotfix 38 or upgrade to Backup Exec 12.0 to resolve the issue with the BEWS differential or incremental backup not showing a failure in the job log to indicate that the BESR operation interfered with proper backup operation. If only the BEWS software is patched or upgraded, there will still remain a conflict with BESR 7.0 backups running in between BEWS backup sets. The BESR 7.0 jobs will need to be reconfigured so that they do not run in between a BEWS Full and differential or incremental backup of SQL or Exchange accordingly. The patch or upgrade only results in the appropriate failing of SQL or Exchange differential or incremental backup operations, and is limited to the resolution of the issue of operations that incorrectly report as being successful when in fact they were not.
For more information on applying the Hotfix or upgrading, review any of the following upgrade methods:
Symantec Backup Exec 11d (11.0) for Windows Servers revision 7170
Hotfix 38 (32 Bit and x64 Bit) - Install Notes
How to manually run LiveUpdate in Backup Exec 11d for Windows Servers
How to upgrade to Backup Exec 12.0 for Windows Servers
To avoid this issue, do not perform any BESR 7.0 backups between a BEWS Full and incremental or Full and differential set of backups. Change the times and/or dates of the BESR 7.0 backup operations as necessary to ensure they are not run between the BEWS backup sets as described in this article.
If an upgrade to BESR 8.0 is performed, this workaround is no longer necessary.