We have 2 clustered instances of SQL that can shares nodes. Normally instance A runs on node 1 and instance B runs on node 2. Both have their own Redgate SQL Backup Agent services set up and running as clustered resouces, SQL Backup Agent-A (on node 1) and SQL Backup Agent-B (on node 2) . However we have noticed that when an instance fails over - both SQL Backup Agents seem to start/restart on the active node - we would have expected just one to start - there are no disk dependencies etc. This also happens when we manually fail back.