Thanks for the feedback. I expected as much with 7.3.
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Stuart Whitby
Sent: March 8, 2006 11:59 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Networker 7.3 - Staging and Cloning
Well, it's improved, but the functionality is limited.
The only reference I can find via the GUI to administration of clones is
a "clones" checkbox under the group configuration. Tick this and
specify a clone pool, and the savesets from that group will be cloned as
soon as the group is otherwise finished. There's no further option in
there to say "clone during business hours", "specify retention period
for clone" or similar. You can specify the retention period for the
clone under its pool resource, but that seems to override the retention
period of the client. So my group with 1 week's browse & retention and
a clone pool with a retention period of 60 days will give me....
D:\>mminfo -av -q ssid=1494157957 -r
volume,ssbrowse,ssretent,ssid,cloneid
volume browse retent ssid clone id
CDLC002R 15/03/2006 08/05/2006 1494157957 1141836420
CDLC002S 15/03/2006 08/05/2006 1494157957 1141837566
...with the clone option checked in the group resource.
So while it looks like things are heading the right way, cloning still
requires some home-grown in order for you to feel good. This will only
work for one copy anyway, so your VTL to tape to DR is definitely going
to require some scripting if you're looking at different retention
policies.
Cheers,
Stuart.
-----Original Message-----
From: Legato NetWorker discussion on behalf of Neild, Jim
Sent: Wed 08-Mar-06 15:33
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Networker 7.3 - Staging and Cloning
This is a question positioned at people running 7.3 in production or
test. I have heard and read that Staging and Cloning has been improved
in terms of functionality (better source and destination support,
scheduling, retention periods, etc.) and integration with the GUI. I
know that clones can have different retentions, but that is about all I
can see as changed. I personally have always thought that creating home
grown scripts to perform all my staging and cloning needs has been a
band-aid on an open sore in NetWorker. I was wondering what they have
really done to improve this aspect of the product.
The angle I am coming from is the ability to perform my primary backup
to my VTL, then make a secondary copy via saveset cloning to tape, then
make a third copy via saveset cloning to our DR site. In 7.2.1 this
would require me to put together a bunch of scripts, is 7.3 able to
create staging and cloning entities to deal with this type of
conifiguration?
TIA
Cheers,
Jim
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 wit 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 wit 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
wit 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
|
