I'm not ready to upgrade just yet. I think 7.2.2 is the last release
before NetWorker got all EMC'ized ;-) I'm going to give the 'clone pool
unique to a storage node' a go and see how it works. I know we loose the
throughput but it gets the second copy into another location without me
having to take it there.
Thanks for your help... I'll follow up with the results.
-----Original Message-----
From: Howard Martin [mailto:howard.martin AT EDS DOT COM]
Sent: Thursday, May 15, 2008 5:56 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Scripting clones from one storage node to
another
Or use pools that can only be mounted on a specific storage node.
eg. define Default1 pool to only be able to use drives on storage node 1
back up a server to Default1, set up a pool Clone2 that only uses drives
on Storage node 2.
Then in your script (via script params) look for ssid on either pool
Default1 or with location storage node 1 and clone to pool Clone2.
this works with 6.x.x upwards.
On Wed, 14 May 2008 11:42:20 -0700, Bruce Breidall
<Bruce.Breidall AT CONCUR DOT COM> wrote:
>I just went through that whole exercise. Everybody's cloning is
>scripted, NW doesn't have any DR module to manage that very important
>aspect of backups.
>
>To force cloning on a specific media server will require the following:
>Read host setting in the library properties.
>Possibly selecting specifc devices in the clone media pool.
>Upgrade to 7.3.4 to get the REC_AFFINITY environmental variable to
>force cloning to honor the read host setting in the library.
>
>There is a situation that if a cloning session asks for a read volume,
>and it is already mounted, it will use it no matter what SN it is
>mounted on. This can be undesirable because it would mean your cloning
>data might travel across the network and take much longer to complete.
>
>I would also consider setting up a common scratch pool so you have one
>media pool to manage when tapes come back in, using the from and to
>media pool settings in the media pool. You can also set up an automatic
>injection process that deposits incoming tapes, relables to scratch,
>and sets recycle mode.
>
>There are other problems as well, core dump on mminfos using clretent,
>hanging groups, many others. You should be planning an upgrade no
>matter what, there are a LOT of problems in 7.3.2 that are fixed at
7.3.4.
>
>-----Original Message-----
>From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
>On Behalf Of Yamnicky, Mark S
>Sent: Wednesday, May 14, 2008 1:13 PM
>To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>Subject: [Networker] Scripting clones from one storage node to another
>
>Networkers....
>
>I'm running 7.2.2 on Solaris 10. Today all my cloning is scripted. I've
>recently added a second storage node. Using the NetWorker interface I
>can clone from one storage node to another however I would like to put
>this functionality into my script. The nsrclone man page doesn't show
>any options for selecting a particular storage node. In your
>experience, can this be done?
>
>Your input would be greatly appreciated.
>Thanks
>/Mark
>
>=============
>Mark Yamnicky
>Infrastructure Versatilist
>Boeing Satellite Development Center
>===================================
>
>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
|
