Now do you have your environment set to require a backup prior to HSM
migrating data off to TSM ?
If you do and you have in fact lost the HSM data, then you may restore the
client's data from backups (and then migrate it off again) long process but
works.
All HSM data here has to have a valid backup prior to migration since TSM
will be keeping the only valid copies of the data.
Now for the tape volume...
have you tried a "move data" ?
I don't know if that would get you past the label problem or not...
also an audit volume on it might be worth a try...
For a price, IBM can pull data off a destroyed tape.
Dwight
-----Original Message-----
From: Richard Bates [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 28, 2001 6:56 AM
To: [EMAIL PROTECTED]
Subject: can't read tape label.
Help! We have a customer problem.
Config:
AIX 4.3.3
TSM 4.1.1
2 x 3494 library
FC SAN
Problem:
A disk primary storage pool which migrates to tape very infrequently has
been corrupted. Basically the files in the JFS filesystem have been
deleted by a root user. No one admits responsibility. Therefore the
primary storage pool volumes have been lost. A new disk volume has been
created and defined to the storage pool. We have copy storage pools so we
attempted a restore of the "destroyed" volumes.
Guess what? Tape errors! The message is
ANR8355E I/O error reading label for volume 030171 in drive F5180
(/dev/rmt4).
They have tried reading the tape in other drives but they still get the
same error. However mtlib mounts the tape OK.
Any ideas? Is there anyway they can recreate the tape label? Without this
tape the customer has lost a lof of HSM data!
Thanks
Richard.
