I have setup transaction log shipping between two servers every 15 minutes, this is on SQL Server 2008 R2. The problem is that when the logs are being restored on the secondary server, it always uses the second-most-recent log file rather than the most recent one available. I suspect this is because the restore happens at the same time the backup occurs on the primary server. I thought I could use the "delay" option to get around this, but it doesn't seem to do the trick. What am I missing?
SQL Server – Transaction Log Shipping Not Using Latest Log
log-shippingsql-server-2008-r2transaction-log
Related Question
- Sql-server – Strange Log Shipping Error Message
- SQL Server 2016 Backup – Full Backup and Log Shipping Guide
- Sql-server – Configuring log shipping with one primary and two secondary instances
- SQL Server Log Shipping – Bulk Remove Alerts for Deleted Databases
- Sql-server – Log Shipping Standby mode
- Sql-server – SQL server log shipping – dry-run data modification script on secondary then resume log shipping
- SQL Server – Log Shipping and Daily Backup
- Sql-server – what is the impact of changing log shipping schedule timing jobs
Best Answer
Converting my comment to answer:
can change the restore frequency to be more frequent on secondary server, but then it wont keep up with the 15 min frequency of backups on primary server. Logshipping will pick up the logs (.trn and not the .wrk files) to restore