Sander Stad wraps up his series on log shipping:
Initially log shipping was meant to be used as a warm standby. You have your data on another instance but you still have some human intervention to get it all back up.
Imagine the following situation. You have setup log shipping using either the GUI or the commands in dbatools. You have about 15 databases and everything is working fine.
Until one day the primary instance goes down and is not recoverable. For the production to continue you have to bring the log shipped databases online fast.
You have to figure what the last transaction log backup was. You have to check if it was copied to the secondary instance and if it’s restored.
To do this by running a couple of queries, copying the files if needed and run the log shipping jobs takes time. I’d rather run a command and recover one or more databases and get back to the problem of the primary instance.
Read on to see how to use dbatools to recover a log shipped database.