Backup exec 2010 failed today ......

Hi Dave,

SureStore 24? Don't you mean MSL 2024? The SureStore was a DAT drive and a single slot at that, unless you can provide more info?

You can try deleting the tape library from Windows Device Manager and BE itself, and then disconnecting it from the server. Restart the media server and make sure it doesn;t show up in either.

Once done, shut the server down, reconnect the unit and start up the server before running the Symantec driver installation for the tape drive itself.

Then run an inventory again.

Thanks!

Yep !  Sorry - yes it is a 2024 .......

So can you provide a few more details on how to deletre the library from Windows and the from the BE software itself?

Once that's done - you are saying, power off teh server, unhook the tape library from the server, and then restart the server again!  

After booting (make sure the server can't see the 2024 library)  Then shut the server down once more and then re-hook up the 2024

and then re-run the driver install right?    Should I power up the 2024 first THEN power up the server or does it matter at that point?

Thanks for the advice BTW !

Cheers'

Dave

Hi,

No worries...Go into Devices in Backup Exec and right-click both the robotics and the drive and delete them.

Then in Windows Device Manager, delete the robotics (should show as 'Unknown Medium Changer') as well as the drive itself.

Disconnect from the server and shut it as well as the server down. Start up the server and make sure the library doesn't show up in either of Windows or BE. Shut it down, connect the library and start up the server again.

Once it boots into Windows, start up the library again and run tapeinst.exe to install the Symantec drivers for the drive, and make sure the robotics shows up as 'Unknown Medium Changer'. In BE, you might have to recreate the partitions, but run an Inventory.

If this doesn't work, then stop the BE services and log onto the Command View for Tape Libraries app via a browser to check whether or not the library sees the tapes. If it doesn't, then HP Library and Tape Tools should be downloaded. I normally would upgrade the firmware if a newer version was available, but you can run a device diagnostic test to make sure all is well with the actual library.

Thanks!

Hey Craig .....

Thanks for the help but no joy .....

- I went in and removed all the 2024 stuff from back up exec and windows.  (1.no lib attached)

- Ran tapeinst and it found it just fine. (2.new drv inst) 

- Ran it tapeinst and it finished OK. (3.new drv after)

- Went in to backup exec and re-created the partition. (4.partitions)

- Started a new inventory job on all slots. (5.invt run)

- It finished ok according to the logs, but it was quick. (6.invt fail)

What do you suggest I try?  the one thing I didn't see was where you said it'll show up as "unknown medium changer" what woudl that show up?

Cheers'
Dave

This is the procedure you should follow to re-install the tape library and tape drive.

1) Go to the BE installation directory and use tapeinst.exe to delete all occurances of both the old and the new tape drives and tape libraries

2) Stop the media server and the library

3) Start the tape library

4) Start the media server

5) Ensure that the library and tape drive is recognised and functioning correctly in the Windows Device Manager. The library should appear as an Unknown Medium Changer with a Microsoft driver and the tape drive should have a Symantec driver.

6) In BE, install the library if necessary.  Go to Tools --> Wizards ---> Device Configuration Wizard to do so.

7) Target your jobs to some other device, save it and then target it to the tape library again.

8) Try again.

Step 5 is critical.  If the tape library and tape drive does not show in the Windows Device Manager then BE cannot use them.

After re-installing the library, run an inventory job on the entire library to update the status.  I would suggest that you do not partition the library until everything is functioning correctly.

I noticed from your screenshots that you are using a mixture of barcode labels and physical labels.  I have a lot of problems when I did this with a MSL2024.  The problems only go away when I use barcode labels on all my tapes.

OK, I'll give it a shot again .... and yep I am using a mixture of labels .....

I can always try to find new barcodes and label the off-site tapes - there are only 6.

To me it seems like the barcode reader has failed but I'm  just wildly guessing.

I'll try the delete and add again today and we'll see if I have any luck!

THANKS again!

Cheers'

Dave

Hi Guys,

OK so step 1 was use tapeinst to pull everything off the server for drivers and delete the library in BE.   (1. no drv_vautl attach)  So I did that and powered down the server and 2024 and disconnected the 2024 from the server and brought it back up - theres the screen shot.  So the vault is unattached and the server and BE see nothing.

Next I reattached the vault and then powered up the 2024 and then the server.  (2. new found )   So now Windows server sees a device called "Unknown Media Changer" and BE has pciked up a two devices one as HP 0001 and a second called HP 0002 as you can see in the screenshot the MS driver seems to be right but I don't know if BE is using the Symantec driver.

I'll wait till you have a look at this before I start the wizard.

Cheers'

Dave

You did not attach any screenshots.

Read my instructions carefully, in particular Step 5.

I think you have partitioned your library on a hardware level which is why BE is picking up 2 devices.  You should always use BE to partition the library.

Ah .... damm site ... I'll try to attach them again ...... my bad!

Cheers'

Dave

There we go ....... (damm technology)   :-)