In regard to: Re: [Networker] savegrp -O, Bruce Breidall said (at 9:29am on...:

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Bruce Breidall
Sent: Wednesday, June 11, 2008 3:10 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] savegrp -O

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?

You don't really need a "final backup of the NetWorker server", assuming
it got backed up at some point in step 1.  You just need a bootstrap, and
the bootstrap should be done after any other steps that would modify the
media database.

Basically, I would insert the savegrp -O and the bootstrap between 2 and
3, but between 3 and 4 would also be OK.

Tim
--
Tim Mooney                                        Tim.Mooney AT ndsu DOT edu
Information Technology Services                   (701) 231-1076 (Voice)
Room 242-J6, IACC Building                        (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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