Re: Database Mirror in a SQL cluster

Tech-Archive recommends: Speed Up your PC by fixing your registry

I think what they mean is that you can not use database mirroring in
place of shared storage when creating a MSCS SQL Cluster. You can
however set up database mirroring as an additional level of protection
to mirror from your SQL cluster to another SQL server outside of the
cluster for a extra level of redundancy - possible as a DR solution.

David A. Bermingham, MCSE, MCSA:Messaging
Senior Systems Engineer
www.steeleye.com

SAM wrote:
I found this

Database Mirroring and Clustering
The most important contrast between database mirroring and failover
clustering is the level at which each provides its redundancy. Database
mirroring provides protection at the database level, whereas clustering
provides protection at the server instance level. Another important
difference is that in database mirroring, the principal and mirror servers
are separate SQL Server instances with distinct names, whereas a SQL Server
instance on a cluster gets one virtual server name and IP address that
remains the same no matter what node of the cluster is hosting the instance.

If you need database protection at the server level (for example, your
application requires access to many databases on the same database server
simultaneously), failover clustering may be a more appropriate choice.
However, if you are concerned to provide availability for one database at a
time, database mirroring has a number of advantages.

Unlike clustering, database mirroring does not require proprietary hardware
and does not have a potential failure point with shared storage. Database
mirroring brings the standby database into service much faster than any other
high availability technology, and works well with new capabilities in ADO.NET
and SQL Native Access Client for client-side failover.

You cannot use database mirroring within a cluster, but you may consider
using database mirroring as a method for creating a hot standby for a cluster
instance database. If you do, be forewarned that because a cluster failover
is longer than the timeout value on database mirroring, a High Availability
mode mirroring session will react to a cluster failover as a failure of the
principal server. It would then put the cluster node into a mirroring state.

So the above answers my question. Since we have implemented SQL cluster
already, there is really no need to implement DB mirroring. Also since we
cannot have DB mirroring in a cluster.

"SAM" wrote:

I read that you can implement DB mirror in a cluster. However, someone else
said that you cannot. Does anyone have any ideas which is correct?

.

Relevant Pages

  • SP2 Database Mirroring - "The remote copy of database "ABC" has not been rolled forward..."
    ... I have 2 SQL Enterprise Editions running SP2 and same collation. ... When i try to start database mirroring I get the following error ... Both SQL Server services are running under account ...
    (microsoft.public.sqlserver.replication)
  • Re: Clustering VS Replication
    ... > We have a SQL 2000 server that we are about to upgrade to SQL 2005. ... Well clustering is a shared-disk solution. ... Database Mirroring are all options, ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL 2005 Server auf W2K3 R2 ???
    ... Edition) R2 Cluster? ... Es handelt sich momentan um einen 2 Node ... Wo Du auch die Alternative Database Mirroring findest, ... mit SP1 offiziell verfügbar ist (was die Dokumentation noch ...
    (microsoft.public.de.sqlserver)
  • Re: N+1 Configuration
    ... Jasper Smith (SQL Server MVP) ... But looking in the cluster admin tool, ... mounting all other drives under that drive ...
    (microsoft.public.sqlserver.clustering)
  • Re: Clustering Question
    ... I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. ... Do you want to cluster SQL? ... > you cannot install Cluster on a Small Business Edition, ...
    (microsoft.public.windows.server.clustering)