Networker

Re: [Networker] nsrclone problems

2003-08-06 07:32:34
Subject: Re: [Networker] nsrclone problems
From: "Willems, Tom" <Tom.Willems AT FUJITSU-SIEMENS DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Wed, 6 Aug 2003 13:29:25 +0200
Hi Frank,

I've seen this behavior before. In my case the problem came from the "Save 
Mount Timeout" and "Save Lockout" parameters from the cloning device. Putting 
these to 30 and 0 (should also be the default settings) solved the problem for 
me. You still might see "waiting 30 seconds" messages afterwards during cloning 
operations, but it should not abort anymore.

HTH,
Tom.


-----Original Message-----
From: Frank Altpeter [mailto:f.altpeter AT BROADNET-MEDIASCAPE DOT DE]
Sent: lundi 4 août 2003 17:42
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] nsrclone problems


hi there,

Perhaps i've overseen something, but this behaviour looks a little
bit strange to me:

I've written a little perl script that does generate a file with a
list of saveset ids that have to be copied to a clone pool.

Then it starts the cloning process as:

nsrclone -v -b 'Default Clone' -S -f /tmp/ssid.25271

which is running fine... until it finished the savesets from one
tape and should advance to the next one.

The saveset ids in the ssid file are sorted by volume and offset to
minimize tape positioning. So, for example, the list contains 167
saveset ids from tape 000004 and 158 saveset ids from tape 000005.
nsrwatch tells me, that cloing session for 167 savesets is running,
and after finishing this, nsrclone does quit from doing the rest of
the savesets with the error:

Starting cloning operation...
  ...from storage node: r2d2
nsrclone: error, busy
nsrclone: Cannot open nsrclone session with r2d2
nsrclone: Failed to clone any save sets

And, there's one of the above error for each volume that is missing.
Does anyone have an idea what's causing this?

I'm cloning from the server to a storage node which has a jukebox
with one tape device attached.

Automatic cloning directly from group control is no solution, since
we only clone the very last full backup of selected clients for
off-site storage.



With kind regards,

        Frank Altpeter

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>