Backups of Microsoft Exchange 2013 may not be restorable with roll-forward of transaction logs due to invalid metadata accompanying the Exchange snapshot. In Backup Exec 2012, this invalid metadata is not detected at backup time, which means that backups may appear to succeed but not be restorable.
The following restore operations fail:
- Restoring a database from a FULL backup with the roll-forward option
- Restoring a database from a FULL backup plus either a cumulative incremental backup or one or more differential backups - in this case, Backup Exec fails when it applies the incremental backups as roll-forward restores based on the restored FULL image
Future Backup Exec releases will avoid these potential data loss conditions by failing the backups after detecting the flaw in the snapshot.
When the snapshot is taken, the Microsoft Exchange VSS Writer produces a Backup Components Document that lacks the LOG_SIGNATURE_XXXX information needed to apply the transaction logs to the database at restore time. This has been seen to occur after the Exchange server was restarted and on other occasions.
Symantec expects that a forthcoming Microsoft Knowledge Base article will be published containing more information on this Exchange issue and how to correct it. A hyperlink will be attached to this article when it is available.
The formal resolution for this issue is included in the following releases: Backup Exec 2012 Rev 1798 Service Pack 3 (TECH205351).
Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.
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.
This issue only affects Microsoft Exchange 2013 CU1 or CU2 (Cumulative Update 1 or Cumulative Update 2) backups taken under Backup Exec 2012.