Sorry, no offense taken (maybe a little bit). I put a lot of work in
what I have in place now, and your comment/question might have caught me
the wrong way.
I apologize as well.
It sounds like neither one of us is sure about knowing if we are doing
things optimally. That certainly does not imply anything good about the
product, tools, support, and documentation we have to work with to make
those decisions, does it?
I am not exactly certain with what you mean by a backup clone job. I
thought I was doing that, but in a more manual form as opposed to all
gui driven.
I was also looking to get an opinion on my original question.
I would by happy to share more details about my solution if you are
interested, or if you think I could help you in any way.
Thanks.
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of MIchael Leone
Sent: Wednesday, June 11, 2008 4:52 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] savegrp -O
Bruce Breidall" <Bruce.Breidall AT concur DOT com> wrote on 06/11/2008 05:35:24
PM:
> Because I am cloning by group,
Me. as well.
> and we have a very limited number of
> drives to work with so I have to carefully pick the cloning window.
The
> script does several things besides cloning.
I (now) have 4 drives dedicated to be cloning drives, with 4 others for
non-clones. Previously, I had only 4 drives, and the clones and
non-clones
shared the same 4 drives.
> Plus, have you ever tried getting input from EMC on the subject of DR
> and putting together a DR strategy with cloning? I put together
> something that I understand and can support. I asked for help and they
> offered it at $240/hr, which I'm sure I would have redone anyways,
just
> like everything else.
I have not, no.
> Plus, with controllable scripts you can generate the auditing
> information you need much easier by creating your own logs.
>
> I chose to do it this way, getting help and ideas from my peers.
>
> Isn't the end result the same?
You seem to have taken offense at my question. I meant it merely as
information, since I do otherwise. If there is a better way, that might
be
easily adaptable to my location, it would be a help to me to find out.
Sorry if it seemed otherwise.
>
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On
> Behalf Of MIchael Leone
> Sent: Wednesday, June 11, 2008 3:57 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] savegrp -O
>
> EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
> 06/11/2008 04:09:44 PM:
>
> > 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.
>
> Why a script, rather than a backup clone job?
>
>
> 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
|
