Book Image

Professional SQL Server High Availability and Disaster Recovery

By : Ahmad Osama
Book Image

Professional SQL Server High Availability and Disaster Recovery

By: Ahmad Osama

Overview of this book

Professional SQL Server High Availability and Disaster Recovery explains the high availability and disaster recovery technologies available in SQL Server: Replication, AlwaysOn, and Log Shipping. You’ll learn what they are, how to monitor them, and how to troubleshoot any related problems. You will be introduced to the availability groups of AlwaysOn and learn how to configure them to extend your database mirroring. Through this book, you will be able to explore the technical implementations of high availability and disaster recovery technologies that you can use when you create a highly available infrastructure, including hybrid topologies. Note that this course does not cover SQL Server Failover Cluster Installation with shared storage. By the end of the book, you’ll be equipped with all that you need to know to develop robust and high performance infrastructure.
Table of Contents (9 chapters)
Professional SQL Server High Availability and Disaster Recovery
Preface

Comparing AlwaysOn, Replication, and Log Shipping


The following table compares the three HA and DR solutions:

Figure 6.44: Comparison table

Figure 6.45: Comparison table - continued

Activity 7: Adding a New Data File to a Log Shipped Database

The Sales database is growing and the business has decided to add a new data file to the Sales database on a new hard drive. You need to add the new data file and make sure that the log shipping is not affected by this change.

To do this, follow these steps:

  1. Create a new folder named NewDataFile in the C drive on both the primary and secondary instances.

  2. Add the new data file to the Sales database on the primary instance and verify that it is created on the secondary instance as well.

Note

The solution for this activity can be found on page 448.

Activity 8: Troubleshooting a Problem – Could Not Find a Log Backup File that Could be Applied to Secondary Database 'Sales'

Consider the following error:

*** Error: Could not find a log backup file that could be applied...