How to prevent Backup Exec from failing a backup operation when encountering corrupt files (excluding Microsoft Exchange files)

Article:TECH5633  |  Created: 2000-01-20  |  Updated: 2014-05-08  |  Article URL http://www.symantec.com/docs/TECH5633
Article Type
Technical Solution

Product(s)

Issue



How to prevent Backup Exec from failing a backup operation when encountering corrupt files (excluding Microsoft Exchange files)


Error



WARNING: "" is a corrupt file.
This file cannot verify.

When Backup Exec (tm) encounters a corrupt file, the job will fail. Following is observed in the failed backup job log:
 
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. 
  
Details:
Final Error Code: a000fe2d HEX (0xa000fe2d HEX) or e000fe2d HEX (0xe000fe2d HEX)
Final Error Description: "The backup of the item is bad"
Final Error Category: Resource Errors
Error Text In Job Log: "Warning: %Email message% is a corrupt file. The file cannot verify" or "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."
 

 


Solution



By adding or modifying the registry key mentioned below, Backup Exec can be configured not to fail the job when a corrupt file is encountered. Please note, this solution is not intended for use with Microsoft Exchange files such as .EDB, .STM and .LOG files. Corrupt Microsoft Exchange files may be indicative of another problem with the Exchange store.

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.


[ I ]. Creating the Registry key:

1. Run REGEDT32.EXE

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. 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.
 
 2. Highlight the following registry key:

   
     
   HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\Backup Exec for Windows\Backup Exec\Engine\Backup
 
3. On the menu bar, select Edit | Add Value

4. In the Value name field, type in "Fail Jobs On Corrupt Files"

5. For the Data Type, select REG_DWORD (Figure 1) 
 
Figure 1
  
  
6. When prompted for the Data, type in "0" (without the quotes)

7. Click OK

8. Close REGEDT32


II. Registry Key Already Exists:

If the key already exists, the following dialog (Figure 2) will be displayed.

Figure 2
 
   
In this case, the key must be modified. To modify the registry key:

1. Run REGEDT32.EXE

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. 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.

2. Browse to the following key:

 
 HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\Backup Exec for Windows\Backup Exec\Engine\Backup [For versions  11x and above]

 
3. In the right window, double-click Fail Jobs on Corrupt Files 
 
4. In the DWORD Editor dialog box change the Value Data to 0 (zero) (Figure 4)
 

Figure 4 
 

5. Click OK

6. Exit Regedit32

 

Supplemental Materials

SourceError Code
Value0xe000fe2d
Description

The backup of the item is bad.



SourceUMI
ValueV-79-40960-65069
Description

The backup of the item is bad



Legacy ID



193940


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


Terms of use for this information are found in Legal Notices