When I set the clone storage node attribute on the client, the cloning
still didn't work. Although after reading the documentation that's what
I thought that field was for.. :-?
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Fazil Saiyed
Sent: Wednesday, February 25, 2009 1:00 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Cloning storage node data
Hello,
I would prefer to set clone SN attribute as you indicated to restrict
the
SN to use it's own drives, i have seen clone data flowing over network
to
other SN in some configuration scenarios, prolonging clone time.
Restricting devices via Pool Tab to achieve the same is error prone and
very clumsy & it poses unconfigure\reconfigure issues in DR.
Hope Legato will have some further enhancement in regards to Device
management, i do believe the GUI has improved functionality now vs
jbconfig\jbedit & i do understand some admins may still rely on
jbconfig\nsradmin for speed & automation it can provide.
Thanks
Chester Martin <cmartin AT SPP DOT ORG>
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
02/25/2009 12:52 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond
to
Chester Martin <cmartin AT SPP DOT ORG>
To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc
Subject
Re: Cloning storage node data
Just for an update in case anyone else has the same problem.....
Since we have multiple storage nodes and dedicated storage nodes. I had
set the storage nodes to use only their dedicated drives and no others.
If I would've been cloning from one storage node only I could've put
that storage node name in the "Read Hostname" field of the properties of
the edl library, that worked when I did that. The only problem is that
this field only accepts ONE hostname. Tech support said there is an
enhancement request already in to be able to add more servers into it.
So what we ended up doing was in the properties of the media pool adding
the non-dedicated edl drives to the pool. Since the client properties
"storage node" field points to itself when I ran a backup it used its
dedicated drive. By doing it this way you don't have to have anything
inside of the "Read Hostname" field of the jukebox.
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Chester Martin
Sent: Wednesday, February 18, 2009 9:28 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Cloning storage node data
I don't think I have the "Clone Storage Node" field set up on the
clients. I'll read up on it and try it again.
Thanks.
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Terry Lemons
Sent: Wednesday, February 18, 2009 8:56 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Cloning storage node data
Hi Chester
I'm not understanding what you mean by your question, "Is there
something
special that I have to put in the cloning script to make it clone from a
storage node?" Have you set the 'Clone storage node' field on your
clients? The NetWorker Administrator Guide has important information on
storage node affinity that you may want/need to review.
Hope this helps.
tl
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Chester Martin
Sent: Wednesday, February 18, 2009 9:50 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Cloning storage node data
Hello,
I have just set up new cloning jobs, but I'm running into issues with it
cloning data that is on storage nodes. Because we have different
retention times for keeping our data (full backups are kept longer than
incrementals) it's easier for me to break up the backups by creating a
group for incremental, a group for fulls, etc...
I'm cloning by group name with the following:
/usr/sbin/nsrclone -v -b "Destination Clone Media Pool" -g "Source
Group" -S -t "1 days ago" &
After cloning finishes I run the command:
mminfo -t "yesterday" -q copies=1
What shows up is all the backups that are done on storage nodes and
dedicated storage nodes. I've doublechecked to make sure that all of my
groups are accounted for in the cloning script. Is there something
special that I have to put in the cloning script to make it clone from a
storage node?
Thanks in advance.
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
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
|
