We are in the process of migrating a backup job and have hit a issue.
We have a 2 node Windows 2003 cluster. On this cluster we have 4 instances of SQL 2005 running. If all cluster resources reside on the one node - we can create/amend selection lists no problem. However, if we split the SQL instances between the two nodes - as soon as try and create/amend a selection list the backup exec console hangs.
The SQL instances have their storage allocated via mount points.
Anyone ever come across this? Ideally we'd like to have 2 SQL instances on each node rather than a active/passive setup.
