I would create 2 or more separate policies for each host.
·
One policy that is configured backing
up the static drives (C:, etc) in the file list using the actual hostname of
the backup client
·
The other policies are configured backing
up the virtual failover drives in the file list using the virtual hostname(s)
of the backup client.
C
-----Original Message-----
From: X_S [mailto:netbackup-forum AT backupcentral DOT com]
Sent: Thursday, December
13, 2007 12:56 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] backing up MS cluster
We have 4 MS 2003 servers with MS multi-node cluster configurations for
SQL 2005. What is the best way to configure the policies? We have
tried using both the All Local Drives directive and specifying each individual
drive letters (pain when resources fail over). But what concerns us how
NB reacts when resources are moved or failed over. we have had instances
where resources were moved but NB didn't pick the drive up on the new
owner-node.
+----------------------------------------------------------------------
|This was sent by xspak1 AT yahoo DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
