Networker

Re: [Networker] Limit on number of savesets in an nsrclone?

2008-03-07 13:51:54
Subject: Re: [Networker] Limit on number of savesets in an nsrclone?
From: "Cox, Shawn" <Shawn.Cox AT PCCA DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 7 Mar 2008 12:47:53 -0600
Definitely want to be carful parsing the ssid list and staging via -S as it 
will *significantly* slow your staging times.  In my environment I only use -S 
for savesets over 5 GB so that I can reclaim space after each ss is staged.

--S

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Reed, Ted G II [IT]
Sent: Friday, March 07, 2008 12:13 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Limit on number of savesets in an nsrclone?

I ran into this problem with directives.  Since directives are loaded into the 
command line savegrp/save command set, if it's too long you break the 
1024/2048/other character limit for UNIX command line...but it's not actually 
YOU, the end user, typing in the command; it's the legato server generating the 
process to INCLUDE the directive details which results in a too long command 
string.  I agree the same could be happening here...but I regularly use 
"nsrclone -b '$ClonePool' -S -f $SSID_List" with over 500 entries (same as the 
other response w/ AFD to tape clones, but mine are tape-to-tape).

If you suspect this is the case, you could use a simple FOR-LOOP based script 
to read over your -f entries and run a separate nsrclone per entry.  Something 
along the lines of:
        for ssid in `cat /file/name`
          do
            nsrclone -S $ssid
          done

The drawback is no intelligence on the ordering of the SSIDs, the benefit is 
the lack of any long nsrclone process commands.....and the ability to see a 
'bad' SSID more easily.  I'd only recommend using this as a troubleshooting 
technique; the -f $SSID_List really is the best practices method for feeding 
nsrclone in this type of setup.  YMMV.
--Ted


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Werth, Dave
Sent: Friday, March 07, 2008 11:37 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Limit on number of savesets in an nsrclone?

I don't know if this applies but often there is a limit on the length of a 
command line.  In Solaris I believe it is 2048 bytes.  So even though you're 
putting the savesets to be cloned in a file it may be parsing it into a command 
line as if you had tried to write it all without the savesets file.  So it's 
not so much the number of savesets you can clone but the total length of the 
command line that results.  For instance if your savesets were name a, b, c, 
etc. you might be able to clone well over 1000 savesets.

Dave

Dave Werth
Garmin AT, Inc.
Salem, Oregon
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Ian G Batten
Sent: Friday, March 07, 2008 8:35 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Limit on number of savesets in an nsrclone?

I'm in the process of binary chopping to find the limit, but it appears that 
there is a limit to the number of savesets I can reference in an nsrclone -S -f 
/file/name (Networker 7.3.3 on Solaris 10).  175 is OK, while 250 is too many.

I have a script which implements a policy of writing a daily tape of activity 
in a given pool, but not deleting the files until a week has passed.  Recently 
we wrote a lot of savesets during one day, taking the amount of activity to go 
to tape at night over the magic threshold, from which there is no return.  
nsrwatch shows the clone job start (cloning session: XXX save sets  reading 
from...) but then immediately reports completion, while the client sees the 
messages below.

/etc/tools/clonetotape.test: saving 313 savesets from 
IncrementalsStaging.003.RO to Incrementals...
+ nsrclone -b Incrementals -s backup-srv.ftel.co.uk -S -f /tmp/
clonetotape.test.25004
nsrclone: RPC error: RPC receive operation failed.  A network connection could 
not be established with the host.
nsrclone: Cannot open nsrclone session with backup-srv.ftel.co.uk
nsrclone: Cannot open nsrclone session with backup-srv.ftel.co.uk.
Error is 'RPC receive operation failed.  A network connection could not be 
established with the host.'
nsrclone: Failed to clone any save sets

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

-------------------------
This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.
Thank you for your cooperation

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

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

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