I recently had a server that normally does not have many scratch tapes start
to run out of tapes.

I discovered 1 tape that was erroring doing the "Move Drmedia" and found
(When I did the individual move) that ADSM reported "Data Segments" still on
the tape.

After much investigation and many attempts to move the data off the tape, I
halted and restarted the ADSM server and I then could issue the "Move
DRMedia" and all was well.

I ran out of scratch tapes because the tape with Data segments (D1003) was
near the top of the sort order. If D1001 or D1002 were available they would
get a proper DR status update. If D1004 was in VaultRetrieve it would not
get moved due to the Failure.



> -----Original Message-----
> From: Daniel Swan/TM [SMTP:Daniel.Swan AT TELUS DOT COM]
> Sent: Friday, July 14, 2000 6:40 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Does my ADSM server have a tapeworm ??
>
> Thank you everyone for your replies.  The problem has been solved, but the
> information you have all provided is invaluable to me
> in understanding other potential issues I should investigate, or may
> encounter, with ADSM.  I am keeping it on hand.
>
> The problem is that when tapes are being checked in, they are not being
> properly changed from vaultretrieve to onsiteretrieve
> status.  Oddly, it seems to do a few, but not all.  I'm still
> investigating
> this.
>
> I have recovered almost 100 tapes now with:
>
> move drmedia "*" wherestate=vaultretrieve tostate=onsiteretrieve
> checkin libv libname search=yes status=scr
>
> Thanks again folks,
> Dan.