> Jon Fraley 
> 
> In the past when recovering data during DR tests we would individually
> mark the SaveSets  as suspect that resided on the disk devices so
> Networker would request the cloned tape. Since we now take 90% of our
> backups to disk, individually marking the savesets will take longer than
> I would like.  In reading the man page to nsrmm there is a -o option
> that can be used to mark the volume as suspect.  I guess that I am
> looking for a little validation as to that will do what I need. 
> 
> And if it does, do I need to mark both the write and .RO volumes as
> suspect?

This is interesting to me as well, since we do something similar for DR. 
We're going to backup-to-disk (upgrade next year), but we're not there yet 
and our DR tests currently operate in a tape-only environment. We've 
always just looped through the relevant subset of our backup pool tapes, 
deleting them with "nsrmm -yd <volume>" in order to force the clone tape 
usage.

In a DR (test) environment, I see no reason to hang onto the entries for 
the actual backups themselves, since they ostensibly don't exist and would 
be regenrated/replaced anyway as soon as a valid backup environment was 
functional. I suspect deleting entire volumes is faster than savesets one 
by one, but is there any reason why this would need to be done any 
differently for disk volumes vs. tapes?

Thanks.

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