Official Mafiree Blogs

Keeping you informed about Databases

Scaling Databases Horizontally: A Solution for High-Concurrency Systems
By Sukan   |   September 20, 2023   |   Posted in : TiDB
Blog post on how TiDB handles the OLAP requests without compromising OLTP

6 Interesting Features In MongoDB 6.0
By Thivakar   |   June 19, 2023   |   Posted in : MongoDB
Upgrade to MongoDB 6.0 for improved index management, error handling, powerful aggregation, replicaset enhancements, time series collection improvements, and embedded field exclusion. Experience efficient database management.

Access Control & Account Management In MySQL 8
By Sukan   |   June 08, 2023   |   Posted in : MySQL
Discover how MySQL 8 enhances security through features like password expiry, password validation, account lock/unlock, privilege management, and dual passwords. Safeguard your valuable data and streamline access control in your MySQL environment.

Significance of using Invisible Primary key (GIPK) with MySQL 8.0
By Sukan   |   February 21, 2023   |   Posted in : MySQL
How Generated Invisible Primary Keys (GIPK) Can Boost Your Database Efficiency

Achieving High Availability Using Log Shipping
By Sujith   |   February 21, 2018   |   Posted in : SQL Server
Here we will get the detailed explanation of how we can achieve HA using Log Shipping.

 Home  /  SQL Server  
Achieving High Availability Using Log Shipping
By Sujith   |   February 21, 2018   |   Posted in : SQL Server

To simplify, log shipping gets a transaction from the source server and applies the same transaction to destination server instantly or at a scheduled time frame. This feature can be deployed for high availability. Say, if the source servers goes down, the destination server can be promoted as primary.

Work flow: Every SQL Server instance would have a transaction log which would log all the changes occurring in a database. A SQL Server Agent on the primary collects all the transactional log and stores as backup log at the configured location. All the log history details, log retention will be monitored and maintained by monitoring server.Copy job on the primary server copies those backup files to the secondary at the configured location. Again, all the details will get monitored by monitoring server. Restore job restores the copied backup files to the secondary databases. Restored information and log history will be maintained locally on the secondary and the monitoring servers.

Hope you understand the basic workflow of log shipping. There are two modes of secondary servers.

  • Standby mode – the database is available for querying and users can access but in read-only mode.

  • Restore mode – the database is not accessible while restoring the transactional log backup.

We can configure more than one secondary server instance for a primary instance. Mix and match of standby and restore modes are also possible. Backups logs can be compressed, but that requires additional CPU time. Most common configurations use network locations, for storing the backups in order to, access the backup folder from multiple instances.


  1. SQL Server log shipping is primarily used as a disaster recovery solution for a primary database.

  2. Log shipping can be combined with other disaster recovery options such as AlwaysOn Availability Groups, database mirroring (deprecated from SQL Server 2016), and database replication.


  1. Failover must be manually initiated on the secondary server.

  2. Secondary server databases are not readable while the restore process is running.


Log shipping is preferable for DR, analytics and reporting applications.


Leave a Comment

Name *

Email *

Comment *

Search All Blogs

Need Support?

Solutions      Services      Resources      About Mafiree

More than 3000 servers monitored

Certified database Administrators

24X7X365 Support

Happy Clients

For Sales Related Queries, Please Call Our Sales Experts at


Meet Mafiree on social networks!


PCI Certificate

Copyright © 2019 - All Rights Reserved - Mafiree