You can use a cluster in conjunction with DB mirroring. Since a mirror
failover is faster than a cluster failover, then the Mirror will become the
Principal when the cluster fails over (if you have a Witness and set up for
High Availability). Failback is not automatic. Consider using manual
failover for DB mirroring. This way, the cluster fails over from one node
to another. You can then manually failover to the mirror for disaster
recovery or for planned maintenance on the cluster.
You don't need a separate NIC for mirroring.
--
Tom
----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"Tim Murray" wrote in message
OK hopefully an easy question for the experts.
We are currently trying to design/test implement an SQL Solution to use DB
Mirroring with SQL 2005 Ent.
We have successfully built an SQL Cluster with 05' Ent SP1 x 64 on with
Windows 2k3 Ent 64bit MSCS. We also have an additional Server with SQL 2005
Ent x64 to be a mirror. Finally we a witness server built with SQL Express.
Can we use a clustered server as a Principal and Stand alone server for a
mirror? I am assuming if we can get this to work the mirror will take over
before the 2nd cluster node. But that is ok with us.
Do we need separate public nic for mirroring? That would be a Cluster
Resource?
>> Stay informed about: Database Mirroring Question/Issue