Professional Documents
Culture Documents
All About Disaster Recovery Features in SQL Server 2005
All About Disaster Recovery Features in SQL Server 2005
Server failovers
Greg Robidoux, Edgewood Solutions
05.25.2006
In the first part of this tips series, Edgewood Solutions' Greg Robidoux discusses
hardware considerations for simpler failovers. In future tips, he'll discuss software
and other supporting data needed for failover.
Failing over to another system in a disaster recovery situation is the last thing you
want to do. Although you won't have to do this often, you may need to eventually --
and it's better to be prepared than not.
You may assume that the simpler the implementation the simpler the failover
process will be. From a hardware perspective that may be the case, but from a SQL
Server performance and high availability standpoint, simple is probably not the way
to go.
In the following tip I'll describe what a simple SQL Server hardware implementation
would look like and why that may be an ideal configuration for failover but not for
performance and availability. I'll also discuss failover methods. Use the following
table of contents to navigate this tip.
TABLE OF CONTENTS
Simple hardware implementation for simple failover
Hardware and performance
Hardware and high availability
Primary hardware components for failover
Additional failover considerations
Database mirroring
Summary
In this article we've looked at some technologies included in SQL Server 2005 that
can be integrated into a Disaster Recovery plan. Each technology has its own
strengths and limitations, and one technology may be a better fit for your DR goals.
Log shipping
The log shipping option also includes all database objects and is easily
understood by DBAs. The exposure to data loss, when scheduled, is roughly a
minimal five minutes. On the downside, you are vulnerable to events that
break the log shipping chain, such as changing the database recovery model.
Log shipping is also not scalable, and you cannot back up the transaction log
while the database itself is being backed up.
Database mirroring
The low latency and automatic redirection of clients to the standby site is a
plus, but database mirroring is practical only for workloads that use the high-
performance mode that is available only in SQL Server's Enterprise Edition.
The success of your mirroring technology therefore depends on the speed
and available bandwidth of your network.
Database mirroring also requires your database to remain in full recovery
mode. Those using SQL Server 2008, however, can compress their database
mirroring traffic, resulting in less bandwidth consumption for your mirroring
sessions.
Replication
The replication option can selectively replicate a subset of the data or
objects. With bi-directional transactional replication or peer-to-peer
replication, failover and failback are also unproblematic. Latency, however,
can be very high during batch operations, and not all database objects are
replicated.
With SQL Server 2005 using bi-directional transactional replication or peer-to-
peer replication, you may need to disconnect users from your database as
you make schema changes, although SQL Server 2008 does not require this.
peer-to-peer replication is an Enterprise Edition-only feature, and bi-
directional transactional replication can be set up only using stored
procedures.