“The backup of the item is bad” (a000fe2d HEX or e000fe2d HEX) is reported during a failed Legacy Microsoft Exchange mailbox backup.
The backup of the item is bad
Warning: %Email message% is a corrupt file. The file cannot verify
Unable to backup the attachment data associated with one or more messages. Some messages and their attachments may have been deleted while the backup was already in progress.
The suggested backup method is to use Granular Restore (GRT) backup methods instead of Legacy (Brick Level) backup methods. The Legacy method is only supported for Exchange 2003 using BE 11 to 2010. BE 2012 no longer supports the Legacy method. The GRT method uses only the backup of the Information store with the backup job selected to enable GRT. Thus the Legacy selection can be removed from the selection list.
For the Legacy Method: To potentially resolve this issue, perform the following steps:
1. Verify if any emails are quarantined. If so, those e-mails need to be excluded from the backup.
2. If any users are selected for backup whose mailboxes no longer exist, deselect these users from the backup job.
3. Make sure the Antivirus Application is not improperly scanning the file system on the Exchange Server and that the Spam Filter is configured properly. For more information on this, review the following document:
Microsoft Exchange mailboxes backed up via the Microsoft Exchange Agent hang in random locations within the backup set if Anti-virus and/or Spam Filtering Applications are not configured properly. http://www.symantec.com/docs/TECH31648
4. If using Advance Open File Option (AOFO), backup just Exchange in a separate job without AOFO.
5. Verify if the option “Enable single instance backup for message attachments (for mailbox and public folder backups only)” is enabled. If yes, uncheck and verify the results. For more information, refer to the Related Documents Section below.
If the issue still occurs after performing the steps above, the registry can be modified per the following steps, to prevent jobs from failing on files which Backup Exec believes to be corrupt:
Warning: Use of this registry key will result in the successful status of job operations that otherwise would have qualified as being failed operations. Ordinarily, successful job status indicates that 100% of the targeted data has been protected and recorded to media. After this registry key has been enabled, a successful job status will indicate a primarily successful backup operation with exceptions. When this key has been enabled, Symantec recommends that an inspection of job log files is performed to make note of any possible exceptions that may have occurred during a backup operation.
Warning: Incorrect use of the Windows registry editor can have disastrous results on a server operating system. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
1. Run REGEDT32.EXE
2. Browse to the following key:
Backup Exec 9.x and 10.x: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Backup
Backup Exec 11d and 12.x: HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\Backup Exec\Engine\Backup
3. In the right window, double-click Fail Jobs on Corrupt Files (Figure 2)
4. In the DWORD Editor dialog box, change the Value Data to 0 (zero) (Figure 3)
5. Click OK
6. Exit Regedt32
7. Recycle Backup Exec services.
Posted in: Backup