Hello,
I agree in general that cloning via script is more versatile, the key is 
to build in the failure recovery, verification of clone completion and 
finally shipment of tapes and bootstrap.
I would be particularly interested in what means other admins  are using 
to verify the clone process.
Index backups via savegrp- O is a straightforward process and i  like the 
approach to do it via a single or multiple group with index only backups.
Thanks



Bruce Breidall <Bruce.Breidall AT CONCUR DOT COM> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
06/12/2008 11:29 AM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
Bruce Breidall <Bruce.Breidall AT CONCUR DOT COM>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: [Networker] savegrp -O






Does anyone have an opinion on the original scenario proposed?

Thanks.

-----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?

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

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



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