cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot read tape after eject and reload

Stuart_Sims
Level 2
Backup Exec 10.1d (SP3), Windows 2000 Server. DLT VS160

We run a full backup and successful verify. Tape shows properly on all displays. A restore job or jobs run properly. Once the tape has been ejected and reloaded it cannot be read again.

A catalog operation before ejecting the tape produces the following output:
-------------------------
Drive and media information from media mount: 2/23/2007 11:27:06 AM
Drive Name: QUANTUM 1
Media Label: DLTSS0110
Media GUID: {57066769-da71-4754-af86-4a2d111e4a6c}
Overwrite Protected Until: 2/23/2007 12:26:02 PM
Appendable Until: 12/30/9999 4:00:00 PM
--------------------------

However, once the tape is ejected it cannot be read again. An inventory operation runs and the tape shows as "unknown media". A catalog operation fails with the following message:
-----------------
Drive and media mount requested: 2/23/2007 12:24:16 PM
V-79-57344-33029 - Error - Mount failed.
Invalid Physical Volume Library Media Identifier.

Media GUID: {00000004-0000-0000-0000-000000000000}
Media Label:
V-79-57344-33029 - Unable to acquire device for the specified pool and media
Invalid Physical Volume Library Media Identifier.
------------------
We have uninstalled Backup Exec and re-installed it with a new database. The problem remains.

Note that Backups have been running night after night successfully. But each backup relabels the tape as if it were "new" instead of using the previously written label.

We have tried both Quantum and Veritas tape drivers....
4 REPLIES 4

Ken_Putnam
Level 6
Have you tried running a few passes of the manufacturer diagnostics for your tape drive?

Sounds kinda like one of the heads is out of alignment

Stuart_Sims
Level 2
Will try that and let everyone know the results....

Stuart_Sims
Level 2
OK... Ran full manufacturer diagnostics and drive and tape(s) pass all tests.

Ken_Putnam
Level 6
Dunno,

Guess you'll have to wait for a Symantec Tech to jump in.

It may be faster to open new thread and just reference this one in it. Sometime it seems that they don't enter a Peer-to-Peer thread that has been running a while