High Availability in SQL Server 2008 - Log Shipping

Log shipping provides a means of providing a secondary server that can be used for data access in case the primary database server becomes unavailable. log shipping is used to send transaction logs from one database (the primary database) to another (the secondary database) on a regular basis. Log shipping keeps the secondary database nearly synchronized with the primary database by constantly backing up the transaction logs from a primary database and then copying and restoring them to a secondary database.

LogShipping Operations:

Logshipping consists of three basic operations. A log can be shipped multiple times, essentially creating multiple secondary servers.

• The three steps in log shipping include: taking a backup of the transaction log on the primary server instance, copy the backup to the secondary server and restore the transaction log on the secondary server.

• You can configure log shipping to produce alerts when certain events have taken place or failed.

• Secondary servers can server other purposes in order to relieve the load on the primary server (such as reporting).

Primary, Secondary and Monitor Servers:

Log shipping requires at least two servers with an optional third.

• The primary server serves as the production server. This is the instance that backups will be created from.

• The secondary server is the recipient of the transaction logs from the primary server instance and is capable of serving as the production server should the primary server instance become unavailable.

• The optional, monitor server tracks the details of log shipping operations that take place and is capable of producing alerts upon completion or failure of events or jobs.

Log Shipping Jobs:

There are four primary jobs that occur when log shipping is implemented as a high-availability solution. These jobs are handled by the SQL Server Agent. You will control the frequency of these jobs.

• The backup job, located on the primary server, performs the backup of the transaction logs, logs history to the local server and the monitor server, and deletes old backup files.

• The copy job is created on the secondary server. This job handles the copying of the transactions log from the primary server instance to the secondary server instance.

• The restore job entails the restoration of the transaction log on the secondary server instance.

• An optional alert job can be implemented on a monitor server.The Job raises alerts for the primary and secondary databases when backup and restore operations have not completed successfully.

Log Compression:

Log compression is dependant on the state of backup compression on the SQL Server instance.

• If backup compression is enabled, transaction log backups will be compressed.

• You can use the sp_configure stored procedure to enable log compression during log shipping operations.

Enabling Log Shipping:

Enabling log shipping consists of several steps that take place on each SQL Server instance. There are also several requirements that must be met in order for log shipping to function properly.

• Choose servers for your primary server,secondary server,and optional monitor server. • A file share must be created between the primary and secondary server instances for transaction log backups to be copied to. • Choose a backup schedule for the primary database. • Create a folder for each secondaty server into which the transaction log backup files will be copied. • Configure one or more secondary server. • Optionally configure a monitor server.

• Several stored procedures can be used to implement log shipping effectively allowing them to be saved for later use.

• SQL Server Management studio can also be used to enable log shipping and the same generic steps can be used as those used when enabling log shipping through stored procedures.

Requirements:

1. The servers involved in Log shipping should have the same case sentivity settings.

2. The databases in log shipping configuration must use the full recovery model or bulk-logged recovery model

Benefits of Log shipping:

1. High Availability --->If primary is down we have the standby server hence it provides high availability of data 2. Cost ---> It is the least expensive as it is available even with Workgroup edition 3. Multiple Secondary ---> This provides higher redundancy of data by providing multiple standby servers

TO Learn More about "LOG Shipping using SQL Server 2008" please check out our website

Related Articles

• Take Me To The Cloud
• Figuring Out The Best Vps Hosting Providers Online
• Quick Tips With Choosing A Domain Name
• Top Reasons A Toshiba Laptop Won't Charge The Battery
• What's A Website Without A Domain Or Hosting?

HTML Ready Article. Click on the "Copy" button to copy into your clipboard.

<!DOCTYPE HTML PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'><html><head><title>Articles Back Link | High Availability in SQL Server 2008 - Log Shipping</title></head><body><h3>High Availability in SQL Server 2008 - Log Shipping</h3><br><br> By: Dbatag Dbatag<br><br><p><p>Log shipping provides a means of providing a secondary server that can be used for data access in case the primary database server becomes unavailable. log shipping is used to send transaction logs from one database (the primary database) to another (the secondary database) on a regular basis. Log shipping keeps the secondary database nearly synchronized with the primary database by constantly backing up the transaction logs from a primary database and then copying and restoring them to a secondary database.</P><p>LogShipping Operations:</P><p>Logshipping consists of three basic operations. A log can be shipped multiple times, essentially creating multiple secondary servers.</P><p>• The three steps in log shipping include: taking a backup of the transaction log on the primary server instance, copy the backup to the secondary server and restore the transaction log on the secondary server.</P><p>• You can configure log shipping to produce alerts when certain events have taken place or failed.</P><p>• Secondary servers can server other purposes in order to relieve the load on the primary server (such as reporting).</P><p>Primary, Secondary and Monitor Servers:</P><p>Log shipping requires at least two servers with an optional third.</P><p>• The primary server serves as the production server. This is the instance that backups will be created from.</P><p>• The secondary server is the recipient of the transaction logs from the primary server instance and is capable of serving as the production server should the primary server instance become unavailable.</P><p>• The optional, monitor server tracks the details of log shipping operations that take place and is capable of producing alerts upon completion or failure of events or jobs.</P><p>Log Shipping Jobs:</P><p>There are four primary jobs that occur when log shipping is implemented as a high-availability solution. These jobs are handled by the SQL Server Agent. You will control the frequency of these jobs.</P><p>• The backup job, located on the primary server, performs the backup of the transaction logs, logs history to the local server and the monitor server, and deletes old backup files.</P><p>• The copy job is created on the secondary server. This job handles the copying of the transactions log from the primary server instance to the secondary server instance.</P><p>• The restore job entails the restoration of the transaction log on the secondary server instance.</P><p>• An optional alert job can be implemented on a monitor server.The Job raises alerts for the primary and secondary databases when backup and restore operations have not completed successfully.</P><p>Log Compression:</P><p>Log compression is dependant on the state of backup compression on the SQL Server instance.</P><p>• If backup compression is enabled, transaction log backups will be compressed.</P><p>• You can use the sp_configure stored procedure to enable log compression during log shipping operations.</P><p>Enabling Log Shipping:</P><p>Enabling log shipping consists of several steps that take place on each SQL Server instance. There are also several requirements that must be met in order for log shipping to function properly.</P><p>• Choose servers for your primary server,secondary server,and optional monitor server. • A file share must be created between the primary and secondary server instances for transaction log backups to be copied to. • Choose a backup schedule for the primary database. • Create a folder for each secondaty server into which the transaction log backup files will be copied. • Configure one or more secondary server. • Optionally configure a monitor server.</P><p>• Several stored procedures can be used to implement log shipping effectively allowing them to be saved for later use.</P><p>• SQL Server Management studio can also be used to enable log shipping and the same generic steps can be used as those used when enabling log shipping through stored procedures.</P><p>Requirements:</P><p>1. The servers involved in Log shipping should have the same case sentivity settings.</P><p>2. The databases in log shipping configuration must use the full recovery model or bulk-logged recovery model</P><p>Benefits of Log shipping:</P><p>1. High Availability --->If primary is down we have the standby server hence it provides high availability of data 2. Cost ---> It is the least expensive as it is available even with Workgroup edition 3. Multiple Secondary ---> This provides higher redundancy of data by providing multiple standby servers</P><p>TO Learn More about "LOG Shipping using SQL Server 2008" please check out our website<br></P></p> <br><br> <b>Author Resource:-></b>  <br><br><b>Article From</b> <a href='http://www.articlesbacklink.com/'>Articles Back Link</a><br></body></html>