Networker

Re: [Networker] Backup Over Fiber????

2009-08-05 16:16:52
Subject: Re: [Networker] Backup Over Fiber????
From: Chester Martin <cmartin AT SPP DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 5 Aug 2009 15:07:57 -0500
That worked like a charm, thank you..

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Chester Martin
Sent: Friday, July 31, 2009 1:57 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Backup Over Fiber????

Wow, I did type out setting the client name to curphyhost, but I meant
the storage node field in the client.. :)

Thank you for the explanation, that explains what I need to do
perfectly.  I'm glad there is a better solution that using the
individual client name to backup cluster drives.  My restores would've
been a nightmare if there wasn't..

Thanks.



-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Thierry FAIDHERBE
Sent: Friday, July 31, 2009 1:44 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Backup Over Fiber????

Client name is NOT curphyhost. Client name will be SERVER as per your
sample.

Let me clarify for sure :
curphyhost is a dynamic way to instruct networker to call MSCS API (in
this
case
but can be sun cluster, veritas cluster, hptru64/hpux, .... ) and
get cluster members list. Then networker compares it with nodes
configured
as
storage node and if selected pool may write on available device on that
SN.
It is ONLY used to select the storage node to use. 
For SN, For clone SN or for recovery SN Affinity, same logic.

Cluster-client Backups will be and MUST be registered using cluster
group
name.
(if not recognized correctly, force correct client name using backup
command

field from client SERVER (for sample : "save -c SERVER")
When you will have to perform recovers, select the client "SERVER".

If you do it differently (not assuming backups registered to SERVER
client)
the day you will have to recover, you will have to know which of ServerA
or
ServerB
had be used as client name. Needless to say it will make your recover
FAR
more complex 
and unexpected behaviours may occurs on your backup levels
(Full/Diffs/Incr). 
What about if you have to recover backup full from SERVERA then apply 
differential recover from SERVERB .... 

HTH

Thierry

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Chester Martin
Sent: vendredi 31 juillet 2009 17:40
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Backup Over Fiber????

Thanks for the reply.

Will setting the client as curphyhost allow restores to be done through
the
cluster name or the active node?

-----Original Message-----
From: Thierry FAIDHERBE [mailto:thierry.faidherbe AT forem DOT be]
Sent: Friday, July 31, 2009 8:48 AM
To: 'EMC NetWorker discussion'; Chester Martin
Subject: RE: [Networker] Backup Over Fiber????

Quite simple question : the solution is ....

Define a Networker client for each cluster node "ServerA" and "ServerB".
Define the tape devices as rd=ServerA:\\.\Tapex and rd=ServerB:\\.\Tapex
Set
ServerA's Storage Node Affinity as ServerA. (and for Clone/Recover SN
Affinity too) Set ServerB's Storage Node Affinity as ServerB. (and for
Clone/Recover SN Affinity too) So, ServerA will backup thru ServerA's
drive
and ServerB to ServerB's drive.
-> All locally attached cluster nodes data backuped over FC.

Now, about your MSCS cluster resource group :
What you have to do is create a networker client for the cluster
resource
"Server" and define storage node affinity as "CURPHYHOST"
(current
physical host)
Doing so, backup will be written by local cluster member that holds the
cluster group : When Server is assigned to ServerA, ServerA will backup
data.
When moved to ServerB, ServerB will process data. -> FC Based backup.

If you set your SN Affinity as "ServerA,ServerB", when Server is on
"ServerB", you have a LAN based backup as SN Affinity lists are
sequentially
processed.

HTH

Thierry

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Chester Martin
Sent: vendredi 31 juillet 2009 15:12
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Backup Over Fiber????

I'm running 7.4.4.  For the sake of example let's say ServerA and
ServerB in
a windows cluster.  The virtual name of the cluster is going to be
Server.  

 

The data I'm backing up will be at least a terabyte so I'm going to go
the
storage node or dedicated storage node route.  I also want to create
drives
dedicated to this cluster.  Both of these servers will be fiber
connected so
they can see my EDL.  

 

I understand the difference between a storage node and a dedicated
storage
node, and I know that I can't setup a drive dedicated to the
cluster using the virtual name of the cluster (Crap!!).   I can setup a
client for each node and backup the cluster drives through the active
client
(yuck!).

 

My question is this, if I setup a client with the name of the cluster
(Server) and NOT give it a dedicated drive will my backups still run
over
fiber?

 


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

<Prev in Thread] Current Thread [Next in Thread>