Backup job fails with error 0xe000fe36 - Corrupt data encountered (a000fe36 HEX or e000fe36 HEX)
Final Error Code: a000fe36 HEX (0xa000fe36 HEX) or e000fe36 HEX (0xe000fe36 HEX)
Final Error Description: "Corrupt data encountered. See the job log for details."
Final Error Category: Resource Errors
Error Text In Job Log: "Warning: %File% is a corrupt file. This file cannot verify."
For additional information regarding this error refer to link V-79-57344-65078
Source : Backup Exec
Type : Error
Error : 57476
The operating system returned an unusual error while backing up the following file:
It is possible that this file is incomplete and therefore should not be restored.
Source : Backup Exec
Type : Error
Error : 57481
An unusual error (<error number>) was encountered while enumerating the contents of the directory: \\*****\**\. It is possible that files or subdirectories have not been backed up. Please examine your log file or catalogs to ensure this directory tree was backed up in its entirety.
Error querying extended attributes (EAs) for the following file...
If the file referenced by the error does not exist on the system, the backup job log may display additional errors similar to the following:
- "Directory not found. Cannot backup directory <\directory> and its subdirectories."
- "Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again."
This error occurs when Backup Exec attempts to back up a file affected by one of the following conditions:
- The file is in use by another application or user. Backup Exec may back up partial data from such a file, but when it is not able to continue the backup of the file, Backup Exec marks the file on the tape as corrupt.
- The file mentioned in the job log does not exist in the given location.
- The file is being scanned by Anti-Virus software, or any other file protection or data replication process is occurring during the backup. This would include another backup running against the same resource at the same time as a problematic job.
- More files are open than the memory cache manager can handle. As a result, the cache manager has exhausted the available paged pool memory. For details, please refer to http://support.microsoft.com/kb/304101
- The backup program has tried to back up a file whose size is larger than the backup API can access on that version of the operating system. This has the same result (that is, the paged pool is exhausted).
For details, please refer to http://support.microsoft.com/kb/304101
The error refers to the instance of the file on the tape or backup to disk file. The original file on the hard disk drive may be intact.
a. In Backup Exec, go to Tools, Options, Advanced Open File
b. Select Use Advanced Open File Option
c. Select "Automatically Select open file technology".
d. If this setting has already been tried, change the option to 'System - Use Microsoft Software Shadow Copy Provider' under 'Microsoft Volume Shadow Copy Service (Windows 2003 and later)'. This is a "paid for" option in BE 11d and earlier versions.
2. Deselecting Use Advanced Open File Option is a better option for some jobs. If the job is failing even when AOFO is not used, try any of the following:
- Open the Job properties under Advanced and select the "Never" radio button.
- Ensure the respective files are closed during the backup.
- This may entail stopping the services associated with the given files
- This is often called a "flat file" backup.
- Remove non-existent files from a backup selection list:
- BE 9x and 10.x: From the Job Setup tab, right-click on the job, Select Properties. Select the Selections tab and under the View format option, Select Text. Locate and delete all entries referring to the concerned file.
- BE 11d, 12.x, and 2010: From the Job Setup tab, right-click on the backup job and select Properties | Selections. Click on "View Selection Details." Locate and delete all the entries that are not required.
- If the file exists, verify that the file is accessible through the UNC path (i.e: Start > Run > \\servername\filename) from the media server.
- If the file is present and accessible at its location, try to copy the file from the target server to the media server
- Verify that the file is not corrupt on disk, or being blocked by a firewall or protected by Anti-Virus or other software if there are errors
3. If the jobs fail with or without AOFO, the following additional steps can be performed:
- Raise the priority of the job
- Create a new selection list for the backup job.
- Run CHKDSK on the volume where the data resides.
- Defragment the volume where the data resides.
- Try taking a backup using NTBackup (Windows 2003) or Windows Server Backup (Windows 2008) for the same file or volume.
- If the Windows backup is successful, Backup Exec should be able to follow it with a successful backup.
- If the Windows backup fails, Backup Exec will likely fail as well.
- Check if VSS (Volume Shadow Copy) writers are in a stable state using the "vssadmin list writers" cmd.
- Ensure the writers are not in any other state than "stable"
- This error may arise if the VSS service is being restarted on the target server while the backup is in progress. Restarting VSS will delete the snapshot created at the start of the backup job and cause the failure. Make sure no other application is restarting the VSS service on the target server during the backup job in progress.
- To increase the available paged pool memory on Windows 2003, configure PagedPoolSize and PoolUsageMaximum settings. For complete details on creating and configuring these registry keys, review Microsoft Knowledge Base Article below: