[Veritas-bu] Backing up a Microsoft Cluster

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C47A27.30D4C942
Content-Type: text/plain

I am reading the High Availability document and am a bit confused.  It seems
to focus on the media server being clustered not backing up a client that is
a cluster.

I have a file cluster I am working with.  One of the things I am trying to
avoid is redundant data backup like we had with a previous product.
Basically you configured the backup software on both nodes as if they were
separate machines. 

If all resources were on A node then a node and all of the shared stuff got
backed up by the A node client and the B node client backed up that server.
Subsequent incremental backups would work properly.  If the resources failed
over between full backups then all of the shared data would appear to be new
and would get backed up during the incremental.  I need to have Netbackup be
'aware' of that failover.

What am I missing?

Thanks!


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, 
is for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise protected by law.  Any unauthorized
review, use, disclosure or distribution is prohibited.  If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.
------_=_NextPart_001_01C47A27.30D4C942
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3DUS-ASCI=
I">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2657.7=
3">
<TITLE>Backing up a Microsoft Cluster</TITLE>
</HEAD>
<BODY>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I am read=
ing the High Availability document and am a bit confused.&nbsp; It seems =
to focus on the media server being clustered not backing up a client that=
 is a cluster.</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I have a =
file cluster I am working with.&nbsp; One of the things I am trying to av=
oid is redundant data backup like we had with a previous product.&nbsp; B=
asically you configured the backup software on both nodes as if they were=
 separate machines. </FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">If all re=
sources were on A node then a node and all of the shared stuff got backed=
 up by the A node client</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"A=
rial"> and the B node client backed up that server</FONT><FONT COLOR=3D"#=
000080" SIZE=3D2 FACE=3D"Arial">.&nbsp; Subsequent</FONT> <FONT COLOR=3D"=
#000080" SIZE=3D2 FACE=3D"Arial">incremental backups would work properly.=
&nbsp; If the resources failed over between full backups</FONT><FONT COLO=
R=3D"#000080" SIZE=3D2 FACE=3D"Arial"></FONT> <FONT COLOR=3D"#000080" SIZ=
E=3D2 FACE=3D"Arial">then all of the shared data would appear to be new a=
nd would get backed up during the incremental.&nbsp; I need to have</FONT=
> <FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Netbackup</FONT><FONT C=
OLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> be</FONT> <FONT COLOR=3D"#00008=
0" SIZE=3D2 FACE=3D"Arial">'</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D=
"Arial">aware</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">'</FO=
NT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> of that failover.</FO=
NT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">What am I=
 missing?</FONT></P>
<BR>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Thanks!</=
FONT></P>

</BODY>
</HTML>

<BR>
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,=20
is for the sole use of the intended recipient(s) and may contain confiden=
tial
and privileged information or otherwise be protected by law.  Any unautho=
rized
review, use, disclosure or distribution is prohibited.  If you are not th=
e
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.


------_=_NextPart_001_01C47A27.30D4C942--