BE inventory on tape drive LTO 3

Hi,

Stop the BE services, and get hold of the diagnostic tool for your tape drive. Make sure you have no hardware issues with the drive.

You can also check and make sure that the RSM service has been stopped if running Windows Server 2003 as this causes issues with BE and controlling the drive.

Finally...make sure that BE is fully patched and that you're using the latest BE drivers for the drive.

Thanks!

Hello Selvun,

    You may want to refer to the following technotes depending on the version of Backup Exec that you are using.

http://www.symantec.com/docs/TECH63380 : The Utility jobs in Backup Exec will not run until the server is paused/unpaused in the Backup Exec console.

http://www.symantec.com/docs/TECH75749 : Inventory or Erase jobs run for 15 minutes and fail with "The Backup Exec Job Engine system service is not responding."

Regards,

-Sush...

The first Technote is for a media changer and you have a stand-alone tape drive. The unlock command mentioned by the Technote does not apply to stand-alone tape drives.

The second Technote mentions certains tape drives that do not have an auto-eject method. This would be applicable to your situation if you were running a DLT8000 tape drive or lower model. You have an LTO which will automatically eject the media when an UNLOAD command is sent to it.

Prior to running an inventory of the drive, start the Backup Exec tracer.exe utility. There is a green start button on top of the tool's UI...press it to start tracing. Run the inventory job and wait for the problem to occur. When/if it does stop the trace and save the output to a text file.

Post it to this thread.

Hi Selvum, 

  Stop the BE services and Restart your Libarary, Once it's online Start the BE services and do the Inventry. It should work...

Hi Moe.

Thanks for trying to assist me. I have followed your instructions........see attachment "test.txt".

The following screen shots are the events of what happens from the time I start the inventory till the error occurs........see file attachments.

Thanks

Selvum

...try removing the drive completely from Windows and BE before disconnecting it. Restart the server, then shut it donw once you verify the drive does not show in Device Manager. Once done, reconnect the drive and start it up. Once initialised, start up the server and then install tapeinst.exe to install the Symantec drivers.

Also make sure that BE is fully patched with the latest service pack for BE 12.5, and any subsequent patches. Push-install these to any remote servers for good measure.

Thanks!

The previous attachment contained garbled characters and sporadic text. Try tracing the activity again but save the output as a .bin file instead. At the top of the tracer.exe tool, there is a diskette icon. Click it to save the output in a .bin format.

Hello Selvum,

   As you are using BE 12 did you refer to the following tehcnote...??

http://www.symantec.com/docs/TECH75749

Regards,

-Sush...

Hi Sush.

I have looked at this technote and also tried this hotfix............does not solve my problem.

Regards

Selvum

...have you tried 1 of these:

1. Open up BEutility.exe and then run a comprehensive repair of the BEDB using the TN below:

http://www.symantec.com/docs/TECH67239

2. Run a repair of BE using Add/Remove Programs. If these don't work, then I would suggest that you log a call directly with Symantec support in order to get this sorted out. If you do get a solution, then post back here & close the thread.

Thanks!