Can I backup a 2 node MS Cluster as clients?

[Anonymous]

I am trying to scope out the requirements for implementing NetBackup 5.1 in a 2 node Microsoft Cluster running Windows 2003 on both nodes.
The high availability guide references installing media servers as a option or a failover server setup.
My question is can these nodes just be clients?
It appears Clients are a NetBackup Component that are supported in a Cluster configuration for MSCS from the Veritas Support matrix.

My method would be install client software on both nodes and backup as normal.
What are the possible implications of doing it this way?
Open for your comments.
Thanks

[Carlos_Santos_T]

yes,
you should to install the client in both nodes, and create two policies, one to backup the shared devices using the logical name and another to backup the local devices using phisical names.

T+

[Anonymous]

Thanks Carlos,

Can you also confirm from this setup that my Quorum disk (Q: drive) would be backed up in the logical cluster backup policy?

And for both policies I cannot use ALL_LOCAL_DRIVES
but need to specify the actual Backup Selections

So the policy for my logical cluster and its drives would be e.g.

Q:\
F:\
G:\

and for my 2 nodes there selection would be

C:\
E:\
Shadow Copy Components:\

Would this be a fair assumption?

[patrickkuah]

Hi,

As Carlos mentioned, you should have two policies at least.
One will be backup up the shared drives which are Q:\ F:\ G:\ and backup via the cluster name

Note. If you have to create addtional policy if there is drive under another cluster name.

For the phyical node, remeber to add in the system state.
By backing the system state, it will backup the cluster config automaticaly.

patrick

[Anonymous]

Patrick, these are Windows 2003 boxes, the directive choices for this model of server/client is only

Shadow Copy Components:\

as this replaced System_State:\ from Windows 2000 server directive options.

[patrickkuah]

sorry about that... shadow copy components will do ;)

patirckkuah