Wednesday, November 30, 2011

Prerequisites for Log Shipping In SQL Server

About Log-Shipping:
Log shipping is a form of high availability that continuously restores transaction log backups created on a primary (source) server to a standby (target) server. It involves two copies of a single database that typically reside on different computers/servers. At any given time, only one copy of the database is currently available to clients. This copy is known as the primary database and the other copy of the database is known as the secondary database. 

Here are the prerequisites for configuring Log Shipping in SQL Server 2008.

SQL Server Edition:  SQL Server 2008 Enterprise Edition, or SQL Server 2008 Work-group Edition, or SQL Server 2005 Standard Edition must be installed on all server instances involved in log shipping.

Case Sensitivity: The servers involved in log shipping should have the same case sensitivity settings.

Network Configuration: Enable Remote connection protocol TCP/IP and Named Pipes or else you can enable only TCP/IP protocol by using Configuration manager from start menu.

Login: The SQL Services in both the primary and secondary server should be the same with same password preferably a domain account.

Recovery Mode: Log shipping must be setup at the database level. The log Shipped database should be in Full Recovery or Bulk logged recovery model,  so that T-logs can be applied, else you cannot configure log shipping.  If you want to provide high availability for multiple databases on a single instance of SQL Server, you must setup log-shipping separately for each database.

Use the below command to change the recovery model or else you can change in the SSMS by right clicking the DB properties.

Use Master
Alter Database [DatabaseName] Set Recovery 'Recovery Model Name'

Shared Folder: Shared folder should be created in Primary server to hold the tran log backups.

SQL Server Agent: SQL Server Agent service must be running on both source and destination servers. Log shipping is implemented as a collection of jobs like backup, copy, and restore. If SQL Server Agent service isn’t running, none of the jobs will execute.

Permission: You must be a sysadmin on each server instance to enable log shipping. The backup and restore directories in your log shipping configuration must Read/Write permission required for SQL Service account of Primary and Secondary servers so that transaction log backup, Copy and restore to be successful.

Prerequisites for Log Shipping. Log Shipping Deployment. Log Shipping Requirements . Log Shipping 'skipping' all logs and not restoring. An Overview of Log Shipping in SQL Server 2005. An Overview of Log Shipping in SQL Server 2008 r2. An Overview of Log Shipping in SQL Server 2012. sql server 2000 log shipping multiple servers. prerequisites for replication. SQL Server Log Shipping to a Different Domain or Workgroup. Ship's Log Requirements. Prerequisites for Migrating from Log Shipping to AlwaysOn, step by step tutorial. step by step guide. Step by Step Installation. Step-by-step procedure. log shipping step by step. Step by Step Guide to. sql server step by step. sql server step by step ebook. microsoft sql server step by step ebook. sql server step by step tutorial. step by step installation guide. microsoft sql server 2008 step by step


Post a Comment