On 2/8/12 8:10 AM, Nelson, Allan wrote:
> So, it seems that once you've actually tried to do a clone the -n switch will 
> flag up the error, but before you get an actual failure it merrily reports 
> that all is fine.
>
> Am I missing something here?  Sort of implies the -n switch is totally 
> useless to me.

Well, the -n switch has just as much usefulness to you now as it did before.  
It will report if
there are any existing problems with the savesets you are planning to clone.  
At the time you
tested, and because the -n doesn't actually mount and attempt to read the 
savesets it can't
test for you, NetWorker had not marked the saveset(s) as suspect and didn't 
until the read
attempt failed.

Has -n ever found any problems for you?  If not, then I would agree that it may 
be useless for
you.  However, for folks that send tapes away, it could be used to give you a 
list of the tapes
you need to retrieve to perform the action...

-- 
Frank Swasey                    | http://www.uvm.edu/~fcs
Sr Systems Administrator        | Always remember: You are UNIQUE,
University of Vermont           |    just like everyone else.
  "I am not young enough to know everything." - Oscar Wilde (1854-1900)

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