SQL Server Log Shipping & Disaster Recovery Install and Configuration -1

In this article, I will explain you about Log Shipping technology in SQL Server. Let’s review the SQL Server Log Shipping & Disaster Recovery Install. After explaining Log Shipping technology, I will show installation and testing of Log Shipping.


Log Shipping


SQL Server Log Shipping & Disaster Recovery Install.

Log Shipping technology was released with SQL Server 2000 and it is used now for SQL Server 2012, 2014, 2016, 2017, 2019 Log Shipping technology in SQL Server is also valid for both High Availability and Disaster Recovery. . A backup or secondary database, which is fed periodically from the transaction log of our main database, can serve immediately as a Master database in the event of a disaster. In addition, since our database is protected, it also provides Disaster Recovery solution.

If you want to keep a copy of a production database  in case of the disaster, or to use production database again in case of disaster with minimum data loss, we need to use Log Shipping technology. In this technology, the production database is kept as an exact copy on a different server, and this database called secondary database is continuously fed from the production database periodically. Thus, if there is no access to production database or data loss in case of disaster, our secondary database can be used as main database.



SQL Server Log Shipping Advantages & Disadvantages

we can list the advantages and disadvantages of Log Shipping as follows.


  1. Provides both Disaster Recovery and High Availability solution.
  2. It is a very inexpensive technology in terms of cost. From SQL Server 2008, this technology is available in all versions except the express version.
  3. Easy to install and maintain.
  4. It is possible to has a lots of logshipping for a database. This is an opportunity to minimize the data loss of an database.
  5. Secondary database, which is in Standby mode, allows reporting in read-only mode without any manual operation.
  6. User error can be solved by using old transaction log backups.




  1. Log Shipping does not have automatic failover , in this case when the failover needs, database administrator must perform manual failover immediately .
  2. Because of Manual Failover, Downtime is more than synchronous mirroring.
  3. It is possible to lose data when the main database is corrupt.



I will explain the installation and configuration of Log Shipping in the Next article.



Do you want to learn Microsoft SQL Server DBA Tutorials for Beginners, then Click This Link and read the articles.

About Mehmet Salih Deveci

I am Founder of SysDBASoft IT and IT Tutorial and Certified Expert about Oracle & SQL Server database, Goldengate, Exadata Machine, Oracle Database Appliance administrator with 10+years experience.I have OCA, OCP, OCE RAC Expert Certificates I have worked 100+ Banking, Insurance, Finance, Telco and etc. clients as a Consultant, Insource or Outsource.I have done 200+ Operations in this clients such as Exadata Installation & PoC & Migration & Upgrade, Oracle & SQL Server Database Upgrade, Oracle RAC Installation, SQL Server AlwaysOn Installation, Database Migration, Disaster Recovery, Backup Restore, Performance Tuning, Periodic Healthchecks.I have done 2000+ Table replication with Goldengate or SQL Server Replication tool for DWH Databases in many clients.If you need Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS Consultancy and Training you can send my email adress [email protected].-                                                                                                                                                                                                                                                 -Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS ve linux Danışmanlık ve Eğitim için  [email protected] a mail atabilirsiniz.

Leave a Reply

Your email address will not be published. Required fields are marked *