SQL Server database log shipping disaster preparedness (PART1)

1. Overview

LOG Shipping The database backup process provided for SQL Server. It can replicate the entire database to another server. In this case, the transaction log is also periodically sent to the backup server for data recovery purposes, which keeps the server in a hot backup state and is updated as the data changes. It also provides monitoring servers (monitor server) that can be used to monitor shipping signals sent at specified intervals. If the signal is not received within the specified time, the Monitoring server logs the event to the event log. This mechanism makes log shipping often the scenario used in a disaster recovery plan.

2. Configuration Preparation

in order to configure the log shipping process, the following preparations are required.

Hardware Preparation

The Log shipping process involves two database (db) servers, one for the Working DB Server (hereinafter referred to as a machine) and the other for the Backup DB Server (hereinafter referred to as B-machine). The two machines must be in the same domain and connected to each other and accessible to each other.

Software Preparation

1. Before you perform the log shipping process configuration, you need to verify the following software environment and configuration:

Windows SQL Server Enterprise Edition is installed on both 2.A and B machines and SP3 patches (recommended) are required.

3. Configure the MSSQLServer service and the SQLServerAgent service for A and B machines to start the domain account and set the SQLServerAgent service startup mode to Automatic.

4. Set the database for which you want to configure the log shipping process to full recovery mode.

5. Create shared folders on both A and B machines, and ensure that the SQL Server service startup account for both A and B machines has permission to access both folders.

6. Confirm that there are no additional backup tasks and maintenance plans on the A-machine database that needs to be configured with log shipping.

SQL Server database log shipping disaster preparedness (PART1)