It may be possible that the tape in the drive is either not in the volume 
pool that is set in the policy or there is valid data on the tape of a 
different retention to the policy or schedule that is attempting to run.
The default setting is to not allow multiple retentions.

>From: "Zermeno, Brandon (Contractor)" <BZERMENO AT intersil DOT com>
>To: <veritas-bu AT mailman.eng.auburn DOT edu>
>Subject: [Veritas-bu] Stand-alone drives
>Date: Wed, 12 Jan 2005 10:13:17 -0500
>
>I have several stand alone, non-barcode reading, tape drives. They run
>on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
>backup starts it is looking for #6. Now tape #6 is not expired and can
>not be written over, Tape #2 IS expired. Why is it looking for that
>specific tape id? How can I circumvent this? The units in question are
>overseas and there is quite the language barrier, So I cant really ask
>them to keep changing out tapes every time the backup runs.
>
>Any ideas?
>