BackupExec - Event viewer errors

[Edu-IT]

Anyone got any ideas on this? I've tried the Symantec support articles but to no success.

 

Backup jobs are failing, common errors seem to be:

 

An error occurred while processing a B2D command.

Changer: MoveMedium() Attempt to Lock Slot Failed (T:\VERITAS\B2D\Folder.lck). Error=3

 

An error occurred while processing a B2D command.

Changer: SetUpProperties() GetDiskFreeSpace failed (T:\VERITAS\B2D\). Error=87

 

An error occurred while processing a B2D command.

Changer: MoveMedium() Attempt to Mount Non-Empty Drive (B2DDrv1.1). Error=1

 

An error occurred while processing a B2D command.

Changer: LockAndRefreshChangerConfig() Unable to Lock Changer.cfg (T:\VERITAS\B2D\Changer.cfg). Error=87

Edited April 11, 2011 by Edu-IT

[bossman]

@Edu-IT:

 

Found this: Enterprise Support - Symantec Corp. - Backups fail with the error "An error occurred while processing a B2D command. Changer: MoveMedium() Attempt to Lock Slot Failed (X:\VERITAS\B2D\Folder.lck). Error=3" in the Microsoft Windows Application Log

 

Hope this is of help

[Edu-IT]

Cross your fingers for me! Just tried that again.

 

I HATE BE with a passion lately.

[Edu-IT]

An error occurred while processing a B2D command.

Changer: LockAndRefreshChangerConfig() Unable to Lock Changer.cfg (T:\VERITAS\B2D\Changer.cfg). Error=87

 

An error occurred while processing a B2D command.

Drive: OpenPosMTF() CreateFile failed (T:\VERITAS\B2D\B2D000140.bkf). Error=87

 

An error occurred while processing a B2D command.

Changer: LockAndRefreshChangerConfig() Unable to Lock Changer.cfg (T:\VERITAS\B2D\Changer.cfg). Error=87

 

Storage device "Removable Backup-to-Disk Folder 1" reported an error on a request to read data from media.

Error reported:

The parameter is incorrect.

.

 

An error occurred while processing a B2D command.

Drive: OpenPosMTF() CreateFile failed (T:\VERITAS\B2D\B2D000140.bkf). Error=87

 

Storage device "Removable Backup-to-Disk Folder 1" reported an error on a request to write data to media.

Error reported:

The parameter is incorrect.

.

 

 

 

Job ended: 11 April 2011 at 12:05:28

Completed status: Failed

Final error: 0xe00084ee - An invalid command was sent to the storage device.

Final error category: Backup Device Errors

 

 

[bossman]

I HATE BE with a passion lately.

 

Yeah well it has to BE said it can BE a right PITA (sorry for the puns)

[bossman]

@Edu-IT:

 

Found this: Final error: 0xe00084ee - An invalid command was sent to the storage device. | Symantec Connect Community

 

Seems it could be something to do with either your SCSI device (Adapter Card) or corrupted drivers or in this case as he has stated unistall of BE on the server and re-install without using any updates from Symantec.

 

Which version of BE you using BTW?

[Edu-IT]

In the System log:

 

Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file T:\VERITAS\B2D\B2D000242.bkf. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

 

{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

 

The device, \Device\Harddisk0, has a bad block.

 

Sounds like perhaps the drive is at fault!

Edited April 11, 2011 by Edu-IT

[bossman]

In the System log:

 

Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file T:\VERITAS\B2D\B2D000242.bkf. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

 

{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

 

The device, \Device\Harddisk0, has a bad block.

 

Sounds like perhaps the drive is at fault!

 

It looks that way