> Preston de Guise
>
>> George, Brett,
>> However, if you instead run separate nsrclone commands for each ssid
>> then that will force it to clone each one separately. It has to. And I
>
> To be more accurate, I'd describe this as being hideously longer/
> inefficient. The reason for this is that at the end of each write
I agree. The only time I've seen any improvement of any kind using "per
SSID" cloning was in a rare instances where I needed to run two clone jobs
simultaneously, reading from tapes where the potential for device
contention existed (due to overlapping savesets between tape "groups"). I
carefully ordered the SSIDs to avoid tape unnecessary load/unloads, as
much as I could. And, any improvement realized was solely from reducing
volume contention, not due to anything else.
Plus, it was a HIGHLY manual process (i.e., figuring out the best order)
for a specific condition... not something I'd do normally. :-)
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
|