1. Support
  2. Knowledge base
  3. 100016681
The error "The data being read from the media is inconsistent" (e00084ca HEX or a00084cd HEX) occurs when running a backup, restore, verify, set copy, or catalog.

The error "The data being read from the media is inconsistent" (e00084ca HEX or a00084cd HEX) occurs when running a backup, restore, verify, set copy, or catalog.

Article: 100016681
Last Published: 2020-11-13
Ratings: 0 4
Product(s): Backup Exec

Problem

The error "The data being read from the media is inconsistent" (e00084ca HEX or a00084cd HEX) occurs when running a backup, restore, verify, set copy, or catalog.

Error Message

Final Error Code: e00084ca HEX (0xe00084ca HEX) or a00084cd HEX (0xa00084cd HEX)
Final Error Description:   The data being read from the media is inconsistent.
Final Error Category:  Backup Media Errors

Error Text In Job Log: An inconsistency was encountered on the storage media in %s.

V-79-57344-33994 - The data being read from the media is inconsistent.

OR

Final Error:  0xe00084ca - The data being read from the media is inconsistent.

Error in the Event viewer Application log:

Event ID: 57612
Source: Backup Exec 
Type: Error
Description: A format inconsistency was encountered during a tape read operation on device "%device%".

Event ID: 57608
Source: Backup Exec 
Type: Error
Description: A format inconsistency was encountered while positioning to begin a tape read operation on device "%device%".

V-379-57612 Event ID: 57612 A format inconsistency was encountered during a tape read operation on device

Cause

The error occurs when Backup Exec is reading a tape or Backup to Disk (B2D) Folder prior to backup, during a Post Backup Verify, Catalog Job, or restore and encounters "end of data" marker unexpectedly.  Various things can cause this error , such as losing power to the tape drive or server, a system or engine service crash, or a tape drive failure , bad or corrupted tape or B2D folder.

Solution

A. If this error is encountered repeatedly, perform any or all of the following to resolve the issue with the tape /  hardware:
 
1. Clean the tape drive.
2. Attempt to use another tape, or attempt to use the same tape in a different drive.
3. Perform a quick or long erase on the tape.
4. Check the Event Viewer for additional errors, and resolve any Event IDs related to the hardware (tape drive or controller). Please refer to the Related Documents section of this article for more details.
5. Make sure the hardware devices are at the latest firmware and driver level.
6. Contact the Original Equipment Manufacturer (OEM) for additional troubleshooting, particularly if the same errors are encountered when using the native Windows Backup application.
 
Enable debugging through SGmon and review the SGmon log. Logging with device debug enabled may report following error in the logs:
[tpfmt] - RD_TranslateDBLK: Did not find a translator for block type 103. Returning 0xe00084cd.
 
In such situation, run the Tape Drive Utility tool to test read/write acess on the Tape drive/Library. If error is reported by the utility tool, contact the Tape Drive Vendor for further Diagnostics.
Workaround: Run the backup without Verify until the issue is fixed By the hardware vendor.
 
B. To isolate issues with a specific tape:
1. Go to the Media  tab in Backup Exec.
2. Right-click on the media that is causing the error.
3. Go to Properties and check statistics.
Multiple "hard" read or write errors indicate a problem with the tape and a new tape is recommended.
 
C. If this error occurs on a backup-to-disk (B2D) folder:
 
1. The job properties can be changed to overwrite from the 'general' option on job properties window.
2. Try the backup on a new B2D folder
3. Check the hard drive capacity.
4. Look for hardware event ids in the system logs of the event viewer. (5,7,9,11,15)
5. Defragment the hard drive.
6. Run 'Check Now' on the hard drive (Right click the drive and go to properties > go to 'tools' tab and click on 'Check now' under Error-Checking) Note - this can only be done at the startup.
 

D. If getting Event ID: 57612 and Event ID:57608 in the application log:

The event was reported in the Application Log because the Backup Exec Job Engine or the Backup Exec Remote Agent for Windows Servers encountered an inconsistency in the data format on the media during a read operation (restore, verify, set copy, or catalog without using media based catalogs). This may be the result of encountering End Of Data unexpectedly. This may be the result of losing power to a tape drive and/or the backup server during a backup operation. If this is the case, there is no more data available beyond that point, and the error during the read operation is expected. This may also be a problem with fast positioning, and may be resolved by setting "Use Fast File Restore" to zero in the Registry.

To change this value, do the following:

1. Stop all the Backup Exec services.

2. Run   REGEDT32.EXE.

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.

3. Browse to the following key:

For   Backup Exec Version   below   11D:

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Tape Format

For Backup Exec version 11D and above please refer to the registry key mentioned below : 

HKEY_LOCAL_MACHINE/Software/veritas/Backup Exec for Windows/Backup Exec/Engine/Tape Format/ Use Fast File Restore

4. In the right window, double-click  Use Fast File Restore.

5. In the DWORD Editor dialog, change the  Value Data to 0 (zero), and click  OK.

6. Quit  Regedt32.

7. Start all the Backup Exec services.

Note:  Performing a restore may significantly increase the time to complete the read operation.

Caution:  Do not leave "Use Fast File Restore" set to zero. As soon as the restore operation is complete, set the value back to one. Do not run backup jobs while the registry value is zero.

 

Please refer to the Related Documents section of this article for additional troubleshooting steps.
 

 

Was this content helpful?

Article Languages