Re: Using SQL Server Database mirroring between Primary and DR clu
- From: Linchi Shea <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 2 Jun 2009 09:15:03 -0700
If it's what I have had experience with, it is a file system level tool and
can replicate any database files. In fact, I don't think it cares what
database it's replicating. You specify what NTFS folders to replicate, and
have some options to exclude folders/files.
Linchi
"Geoff N. Hiten" wrote:
I have used it as well. It doesn't replicate system databases such as msdb.
or distribution. You can see where that can cause problems.
Much like mirroring, it is a database-level failover mechanism.
--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Linchi Shea" <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:98C7A096-4963-4208-9F70-0904A0F009EE@xxxxxxxxxxxxxxxx
Have you tried it under a real disaster scenario rather than a planned
one?
Does it ever hang from time to time?
Linchi
"briantn54203" wrote:
I was faced with the same problem that you are having here. I have been
demoing a software called CA XOsoft Replication and High Availability.
This works just like mirroring does without the witness server. It works
through DNS redirection so your virtual server Name in DNS will change
its IP
Address so your SQL Instance will be up with the same name on either side
of
your DR Plan.
This can be used for Exchange too, but that is for the Network guys. I
have
tested this thoroughly and it is a very solid product.
I have this running on my production side with a 5 instance, 5 node,
active/active cluster with virtual servers and physical servers on SQL
Server
2008 and Server 2008. I have it failing to my other DR site which is a
standalone box (could be clustered though) and it fails within a minute.
You
can custom set your failover times to whatever you want.
The only thing that I do not like about the product is the drive letters
and
locations have to match from one server to your DR server. This acts just
like a microsoft cluster with the services stopping and starting on one
side
or the other.
It is work checking out.
http://www.arcserve.com/products/product.aspx?id=8282
xyberdobs wrote:
Hi all.
Any assistance regarding this would be greatly appreciated.
We have configured two sql server 2005 clustered environments - one will
be
hosted at our local datacenter and the other at our DR site. These two
clusters are geographically dispersed.
The clusters will be configured as active/passive and I would like to
incorporate sql server 2005 database mirroring between the two clusters
for
redundancy. Both clusters have the same domain names
My questions are:
can I configure both sql clustered instances to have the same sql
virtual
server and instance name, so that in the event that the datacenter goes
down,
we can initiate a manual failover between principal and mirror and the
front-end applications would still be able to connect using the same
server
and instance name at the DR site?
If we cant have the same server and instance names, how can I configure
the
cluster at DR site assume the identity of the primary virtual sql server
and
instance name so that no code changes are required to point to the
databases?
Many thanks.
- Follow-Ups:
- Re: Using SQL Server Database mirroring between Primary and DR clu
- From: Geoff N. Hiten
- Re: Using SQL Server Database mirroring between Primary and DR clu
- References:
- Re: Using SQL Server Database mirroring between Primary and DR clu
- From: Linchi Shea
- Re: Using SQL Server Database mirroring between Primary and DR clu
- From: Geoff N. Hiten
- Re: Using SQL Server Database mirroring between Primary and DR clu
- Prev by Date: RE: How to change from Dynamic Ports to Static Ports on SQL Cluste
- Next by Date: Re: Using SQL Server Database mirroring between Primary and DR clu
- Previous by thread: Re: Using SQL Server Database mirroring between Primary and DR clu
- Next by thread: Re: Using SQL Server Database mirroring between Primary and DR clu
- Index(es):
Relevant Pages
|