Hi,
I have six save sets that I need to backup (level=full) on a client:
/data/dir1/year1
/data/dir1/year2
....
/data/dir1/year6
These are available vis NIS as /web/year1, /web/year2 ... /web/year6.
I'd prefer to use these names as the save set names rather than the
local (/etc/fstab) mount point names as this would make it easier for us
to locate these in the media database in the future.
1. Can I do this from the nwadmin NW GUI, or will I need to use the save
command on the client?
2. If I have to use the save command, it would be like:
# save -s server -b pool -l full -N /web/year1 /data/dir1/year1
# save -s server -b pool -l full -N /web/year2 /data/dir1/year2
That correct?
3. Other than launching one save process for each one, is there any
other way that I can run several in parallel like what happens when I
list save sets in the NSR client resource in the GUI and then run the
group from there? I'd like to enable automatic cloning and just run the
group and have it take care of all six. We usually have client
parallelism set to 4 and device target sessions to 8. Of course, I can
manually clone later, though, but just asking.
If I enable cloning on the group, and I write a script that saves each
of the six paths as shown above but instead change the command to
something like:
save -s server -g group -b pool -l full -N /web/year1 /data/dir1/year1
then would that force cloning of each save set after it completes? This
would be OK as only the last save set is really that big.
Thanks.
--
George Sinclair
Voice: (301) 713-3284 x210
- The preceding message is personal and does not reflect any official or
unofficial position of the United States Department of Commerce -
- Any opinions expressed in this message are NOT those of the US Govt. -
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
|
