[Networker] savegrp -O
2008-06-11 16:14:15
As I have learned from this source, it is a good idea to create a separate
disabled group to contain a copy of all your clients to do a savegrp -O
via an external call to get a backup of the indexes and the bootstrap.
For a typical day, here is our order of legato tasks, single threaded:
1) run backups
2) Run clone scripts that clone savesets generated in the last day.
3) Eject the clone volumes.
4) FTP the bootstrap file to an offsite location for DR.
5) Generate recall/pick list
Would the recommendation be to incorporate a final backup of the NW
server, followed by a clone of the backup just taken, followed by the
savegrp -O between steps 3 and 4, to be fully protected?
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
|
|
|