Clusters are a bit tricky, they require:

-> client resource for each node, local drives only.

-> client resource for the virtual host, with a few extras:
1) remote access for system/root/whatever on both nodes
2) backup command set to 'save -c VIRTUAL' etc

This is how I successfully backed up a virtual host on Windows MSCS.  Note that 
I don't specify 'ALL' anywhere; Though it probably can work, we've had 
headaches with it here.

We also have a Veritas cluster on Solaris/sparc boxen.  After watching the 
behavior in how the filesystems failed over, we decided to set their backup as 
if they were standalone (again, not using ALL).  We understand the tradeoffs 
involved in not using ALL here, and it has worked fine (I've personally done 
recovers that were good).

Having the cluster be in active/passive mode also helps with a configuration 
like this; The MSCS cluster is active/active (sort of) so we did the 'normal' 
setup.

--TSK
-----=====-----
Tim Kimball, Sungard/BRASS

+----------------------------------------------------------------------
|This was sent by t.s.kimball AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

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