The solution to backing up a SQL Cluster remotely requires the following:
Remote Agents for each server in the cluster
SQL Agent for each server in the cluster
Install the remote agent on to each cluster node, and restart each node.
Configure a job for each cluster group presented by the cluster.
To illustrate this, let's say we have 2 physical servers: SERVER1 and SERVER2.
Both SERVER1 and SERVER2 has got just one local drive letter to be backed up of C:.
These servers present 3 virtual nodes, each node being represented as Cluster Group within Cluster Administrator. Let's call these three virtual nodes VIRTUALQUORUM, VIRTUALSQL1 and VIRTUALSQL2.
VIRTUALQUORUM has an assigned drive letter of Q:
VIRTUALSQL1 has an assigned drive letter of S: and a SQL Instance VIRTUALSQL1/SQL1
VIRTUALSQL2 has an assigned drive letter of T: and a SQL Instance VIRTUALSQL2/SQL2
To fully backup the cluster from a seperate server using backup exec, the jobs that will be required are:
SERVER1 Job
\\SERVER1\C$
SERVER2 Job
\\SERVER2\C$
VIRTUALQUORUM Job
\\VIRTUALQUORUM\Q$
VIRTUALSQL1 Job
\\VIRTUALSQL1\S$
VIRTUALSQL1/SQL1
VIRTUALSQL2 Job
\\VIRTUALSQL2\T$
VIRTUALSQL2/SQL2
So long as these jobs are configured, the credentials provided have the right to backup the resources in the jobs and the server names (including virtual nodes) are resolvable by the backup server (as well as all usual caveates, such as access through firewalls etc), this will work, no matter where the virtual nodes are presented from.
Hope that helps,
Steve