Networker

Re: [Networker] Virtual tapes get stuck in virtual tape drives

2010-09-22 17:56:57
Subject: Re: [Networker] Virtual tapes get stuck in virtual tape drives
From: Davina Treiber <Davina.Treiber AT PEEVRO.CO DOT UK>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 22 Sep 2010 22:54:58 +0100
On 09/22/10 21:56, A Darren Dunham wrote:
> On Wed, Sep 22, 2010 at 04:29:08PM -0400, rmumford wrote:
>> Running NW 7.5.2 with Data Domain DD880 in VTL mode. It has been
>> suggested by DD that we need to relabel tapes each day via a script in
>> order to keep the data stored on the DD880 trimmed down for
>> replication, and I will agree thats probably a good idea. I have a
>> script written that works pretty well. The problem comes in if that
>> script is running against a pool when a backup kicks off that wants to
>> use the same pool. Some of the relabel commands may fail, and then
>> that tape may be "stuck" in that drive, and that drive can't be used
>> until I can get that tape out. The only way I get the tape out is to
>> go to the DD880 and export those tapes, then import them back into the
>> library.
> 
> I would suggest adding some protection into the script.  Before
> relabeling the volume, you might consider making the volume read-only
> first.  If those succeed, it can't be used by a backup.  If it's being
> used by a backup, I suspect the read-only will fail.
> 
> At that point, you can relabel and the read-only designation will
> disappear.
> 

The volumes he is relabelling are already recyclable, so NetWorker is
not going to be writing to these volumes anyway. I don't think you
suggestion is going to make any difference.

I am scratching my head about this one. I can't see why another backup
starting should affect a label operation. The only thing I can think of
is that perhaps some of the timers in the jukebox resource could be
tweaked, but I'm not convinced about that. Unless he's done something
silly like DDS on a DD. Maybe this is still the persistent naming issue
I mentioned in my earlier posting - that definitely needs fixing anyway.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER