Final error: 0xe00084f2 - An attempt to write database end of media has failed. Backup Exec returns an error in the backup job log stating "Tape access reached a file mark."
Tape access reached a file mark.
- Worn or Used media - Replace the media. Tape alert technology checks for the worn out media and the alert is displayed in the job log. (Please refer to related documents for more information on Tape Alert messages.)
- Contaminated read/write heads of the tape device - Run three/four consecutive cleaning cycles to clean the tape drive heads.
- Retension the media - Primarily for mini-cartridge and quarter-inch cartridges (Travan technology). Use retension to run the tape in the tape drive from beginning to end at a fast speed. In this manner the tape winds evenly and runs more smoothly past the tape drive heads.
- Tape head alignment problems - Replace the tape drive or have the tape drive serviced.
- Tape driver - Load the appropriate Backup Exec (tm) tape driver, or switch to another driver (native NT or original equipment manufacturer (OEM)) if a Symantec driver is already in use.
- SCSI Configurations - Please refer to the Related Articles section below.
- Incorrect termination or bad cables
- Long erase a tape in a drive
Change registry entry for HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Tape Format\Use Fast Append from 1 to 0 (value is hexadecimal)
Change registry entry for HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Backup Engine\NTFS\FsUseAsyncIO from 1 to 0 (value is hexadecimal)
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. A complete backup of the registry and workstation should be made before making any registry changes.
Running test operations with the native Windows backup utility is recommended for further help in identifying the source of the behavior. If both applications are experiencing errors, contacting Microsoft or the device manufacturer for further support may be necessary.