Connection timeout expired failed a log shipping restore job at a client. The pre-login handshake alone took about 33 seconds, past the 30 second default. Staggering the jobs and adding -logintimeout 60 to the job step fixed it.
Could Not Log History: Log Shipping Copy and Restore Jobs Fail
The Could not log history error stopped the Copy and Restore jobs of a client’s log shipping. The Agent account was a sysadmin on the primary and secondary, but not on the monitor server. A third Profiler trace showed it.
Error 21089: Log Shipping Jobs Need Sysadmin on the Monitor Server
Error 21089 failed the Copy and Restore jobs of a log shipping setup. A Profiler trace showed the jobs raising the error on the monitor server. The SQL Server Agent startup account was not a sysadmin there.
What are Ports Needed to Configure Log Shipping? – Interview Question of the Week #169
What are ports needed to configure log shipping? A client in a locked-down network asked me, and here is the list of ports to open on the firewall.
SQL SERVER – Log Shipping Monitor Not Getting Updated
The log shipping monitor stopped updating last_backup_file and last_backup_date for the primary, while every job ran fine. Here is how I traced it.
SQL SERVER – Msg 32055 – sp_refresh_log_shipping_monitor – There Was an Error Configuring the Remote Monitor Server
Msg 32055, error configuring the remote monitor server, hides the real error. Read from the procedure on SQL Server 2025, with a safer fix than sa.
Log Shipping Alternative for Databases in Simple Recovery Model
A log shipping alternative for a database in the simple recovery model is a second copy that restores the newest full backup and the newest differential backup. This post finds those two files from the backup history in msdb, restores them with MOVE and RECOVERY, and repeats the cycle on a schedule. It also states what you lose compared with real log shipping.