01-26-2005 07:57 AM
We have a problem when a "poor quality" tape is found. Dataprotector will just stop the backup and wait with a mount request instead of labelling that tape poor or unuseable and then moving on to the next tape. Is this a bug, or is there something that can be done to fix this problem?
Solved! Go to Solution.
01-26-2005 08:35 AM
When does the tape becomes Poor ? A media, already marked as Poor in the Media database is not selected for backup. If a media becomes poor when a backup is running (DP encounters problem when writing to the media), the session normally fails and the media is marked as Poor.
Is there any error messages from a such session ?
01-26-2005 08:56 AM
So if a tape is found to be "poor" during the backups it will not abort the writing to that tape and move on to another tape...it just aborts the whole backup instead?
01-26-2005 01:00 PM
Wow it is quite complicated, but here are some of the rules DP uses.
With a new backup DP will, if the pool is appendable, try to use the last tape it was writing to.
If on a previous backup DP was told by the OS/SAN/Storage systems that there was an I/O error between the device file and the tape DP will mark the tape as poor. In these circumstances DP will not try to do any more backups to this tape.
When doing a backup DP will first try to use the last tape it was writing to (assuming the policy is the default - appendable).
After using that first tape, DP will require tapes that all the next tapes are 100% available eg. Status:- Expired, New, Unprotected. If there the no tapes in the library at a 100% free status DP will issue a mount request.
If a library has, for example, 6 tapes partially used with protected data, it will use the first tape OK, but then will need 100% available tapes and will not use the other partailly used/protected 5 tapes.
If you are continually finding DP marks tapes as poor, this is usually (29 times out of 30) because of some OS/SAN/Storage problem in the chain between the device file and the drive. From a DP point of view 1. ensure your DP patching is up to date especially Core and MA. 2. Make sure these patch binaries are distributed to all MA systems in the SAN. 3. Contact your OS/SAN/Storage support for help identifying the problem.
Suppose you had a hardware problem with the SAN/storage that was fixed, but DP had previously marked many of the tapes as Poor:- before DP 5.1 you had to run a Verify (taking hours) on each tapes to make them Good again. On 5.1 there is a command to resets the tape Status.