In the second part of the series we discussed the way to test the log shipping status using the command “Test-DbaLogShippingStatus”.
This blog will be about how to get log shipping errors to analyze why your log shipping isn’t working.
There are several options to get the log shipping errors right out of the box. One of them is using queries and the other one is the event viewer.
In the first part of the series I described the command Invoke-DbaLogShipping.
This makes it possible to set up log shipping. This blog post will be about the command to test log shipping status. Before I describe the command, I want to discuss the options that are available in the SQL Server Management Studio (SSMS) and SQL Server.
Microsoft has made it possible to check the log shipping using SSMS. This can be done using queries or by using the “Transaction Log Shipping Status” report.
This post is the first one of a series of four describing all the different commands. We’ll discuss the commands to set up log shipping with dbatools, how to check the status, to check for errors, and to recover in case of an emergency.
Before we go into the why I want you to know what log shipping is. Log shipping dates back to the early versions of SQL Server. The first article that I could find dates back to the year 2000 and explains how to setup log shipping with SQL Server version 7.