Re: Replication with failover clustering??
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Wed, 12 Apr 2006 08:14:31 -0400
This question should be posed to EMC to see if their product is a good fit
with what you are trying to do.
From what I read it sounds like you are trying to do geospatial clusteringwith the requirements of no data loss, mirrored copies and automatic
failover.
Microsoft SQL Server clustering is not a good fit for geospatial clustering
because of the distance limitation (150 ms ping response), but it can be
made to work. Database mirroring does not have the stringent distance
limitation that geospatial clustering does, but the exposure for data loss
can be higher than with clustering depending on which mode you run it in.
Both clustering and database mirroring do do automatic failover, however
they are not scalable to more than 2 or 3 "subscribers". Replication does
not do automatic failover, its latency is low (a function of bandwidth and
throughput), and is scalable to many subscribers, and is way cheaper than
clustering, especially geospatial clustering. Replication can have a greater
exposure to data loss however with the added latency.
If you can manage the automatic failover - you might want to look at
replication.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rishi Khullar" <Rishi Khullar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E4BAF8B5-51B5-4F44-B7E6-3640BAB29C08@xxxxxxxxxxxxxxxx
We have multiple SQL Server 2K DB servers which are geographically
distributed and are expected to have same data at particular instance of
time for ensuring same result for same set of inputs. For this set up -
data
consistency at all distributed DB servers, we are replicating the DB
servers
after particular time intervals. We are using EMC Legato AUTOMATED
AVAILABILITY MANAGER for achieving the failover clustering support i.e. if
one DB servers fails the other servers becomes active and starts serving
as
the DB server for our application and also as Publisher for other DB
servers.
However the product is excellent for providing failover support to stand
alone database but it is not meeting our requirements for replication
failover support also.
-- In setting up SQL server clustering, the installation starts with
registering the server as 'Virtual server' but that option was not enabled
by
the SQL installer (as it didn't recognize clustering support on that
system)
though the EMC Legato AAM was started and running successfully. It didn't
detect the clustering services were on that system.
--registering and running the server as common IP only. But however in
this
case the distributor was unable to be set - the first step in replication
process failed. We also tried all the other possible combinations of name
and
virtual IP but it didn't work either.
.
- Follow-Ups:
- Re: Replication with failover clustering??
- From: Rishi Khullar
- Re: Replication with failover clustering??
- Prev by Date: Error: existing subscription already contains table included in the new subscription
- Next by Date: Re: Error: existing subscription already contains table included in the new subscription
- Previous by thread: Error: existing subscription already contains table included in the new subscription
- Next by thread: Re: Replication with failover clustering??
- Index(es):
Relevant Pages
|
