Database Mirroring for Disaster Recovery

How to leverage asynchronous mirroring

139794.zip Database mirroring is primarily an availability feature, but it has been gaining popularity as a disaster-recovery option. Asynchronous mirroring, in particular, is being leveraged for disaster recovery in scenarios where log shipping might have been used in the past. Asynchronous mirroring offers several enhancements over log shipping, making it an attractive option.   Asynchronous Mirroring vs. Log Shipping Asynchronous mirroring and log shipping share several ...

Buy This Project Plan Now!

This content is part of the Migrating to SQL Server 2012 Project Plan.

Purchase this Project Plan to receive:

  • Step-by-step guidance for managing your project, start to finish
  • Tested advice for preparing for and completing your project
  • Insights to help you avoid common pitfalls and traps

Already registered? here

Discuss this Article 4

ahoman@hw.com
on Oct 14, 2011
I am trying your failover.sql script and it is working well up until the last step where it has failed over and needs to set the mode back to asynchronous on the new principal server. I am seeing the following error and wonder if this last step is even possible since it is being initiated on the server that just became the mirror? The alter database for this partner config values may only be initiated on the current principal server for database 'dbname'. Do you have any ideas what might be happening here? Thanks.
ahoman@hw.com
on Oct 14, 2011
I am trying your failover.sql script and it is working well up until the last step where it has failed over and needs to set the mode back to asynchronous on the new principal server. I am seeing the following error and wonder if this last step is even possible since it is being initiated on the server that just became the mirror? The alter database for this partner config values may only be initiated on the current principal server for database 'dbname'. Do you have any ideas what might be happening here? Thanks.
ahoman@hw.com
on Oct 14, 2011
I am trying your failover.sql script and it is working well up until the last step where it has failed over and needs to set the mode back to asynchronous on the new principal server. I am seeing the following error and wonder if this last step is even possible since it is being initiated on the server that just became the mirror? The alter database for this partner config values may only be initiated on the current principal server for database 'dbname'. Do you have any ideas what might be happening here? Thanks.
danjam47
on Feb 6, 2012
While I found the info in this article informative and useful, it might have been better titled "Database Mirroriring for Maintenance Windows." All the activities described assume that both sides are available. Disaster recovery is ususally about cases where the principal has become unavailable. The article would have better fulfilled its title had it covered descriptions (including compare and contrast with log-shipping, particularly with regards to data loss) and instructions for making the secondary a primary when the primary is not available.

Please or Register to post comments.

Migrating to SQL Server 2012 Project Plan

<<< Back to the Project Plan

Planning


Welcome to SQL Server 2012

The Case to Upgrade to SQL Server 2012

SQL Server 2012 Editions

Microsoft SQL Server 2012's Editions and Licensing

SQL Server 2012 Virtual Labs

Microsoft SQL Server 2012 Licensing Options

Things You Might Not Know about SQL Server 2012

SQL Server 2012’s Hardware and Software Requirements

Visual Studio 2012 and SQL Server 2012 Reporting Services—Still Out of Sync


Migrating


Migrating to SQL Server 2012

Upgrade Assistant for SQL Server 2012 (UAFS) and SQL Server Upgrade Advisor


Implementing SQL Server 2012's New Features


High Availability

SQL Server 2012 High Availability

Microsoft SQL Server 2012: AlwaysOn Availability Groups Feature

Upgrading Clusters to SQL Server 2012 When AlwaysOn Availability Groups Will Be Used

Planning and Implementing a SQL Server Cluster

Be Invincible with AlwaysOn Availability Groups

Database Mirroring for Disaster Recovery

Power View

Introducing Microsoft Power View

Getting the Most Out of Microsoft Power View

Microsoft SQL Server 2012 Takes on Big Data with Hadoop

What's New in Microsoft SQL Server 2012 PowerPivot

Improve the Performance of Data Warehouse Queries with Columnstore Indexes

Master Data Services and Data Quality Services

SQL Server 2012 BI with SQL System Center Data Warehouse

Dive into SQL Server 2012 EIM Tools (DQS)

Contained Databases

SQL Server 2012 Contained Databases

Using SQL Server 2012 Contained Databases

T-SQL

T-SQL Join Types

How to Use Microsoft SQL Server 2012's Window Functions, Part 1

Microsoft SQL Server 2012: How to Write T-SQL Window Functions, Part 2

SQL Server 2012: How to Write T-SQL Window Functions, Part 3

Solving Gaps and Islands with Enhanced Window Functions

Using the New OFFSET and FETCH NEXT Options

Take Advantage of SQL Server 2012's Window Functionality

SQL Server 2012 Solutions for Median Calculation

Database Administration

SQL Server 2012 Keeps Your Data a Little More Secure

SQL Server 2012’s INDIRECT CHECKPOINTs

SQL Server 2012 Databases on File Shares

Introduction to SQL Server Data Tools

Cool New SQL Server 2012 Metadata

SQL Server’s Undocumented Changes

Using Solid State Disks in SQL Server Storage Solutions

SQL Server 2012 and Windows Server

Windows Server 2012 and SQL Server 2012: Better Together

Creating a SQL Server 2012 Installation for Windows Server Core

Development

New Features in SQL Server Data Tools