One of the secondary's is failing log shipping restore due to insufficient drive space. This might not be looked at by IT for several days. Can log shipping primary server purge transaction log backup before secondary has a chance to restore in this scenario? Or does Log shipping primary just hold onto transaction log backups until all secondary's have restored it?
SQL Server Log Shipping Retention – Managing Log Shipping Retention in SQL Server
log-shippingsql serversql server 2014
Related Question
- SQL Server Log Shipping – Monitor Server Down, Copying but Not Restoring
- SQL Server – Log Shipping Large Databases and Log Management
- Sql-server – Problem Configuring Log Shipping for DR Server
- Sql-server – Log Shipping always fails, after a while
- Sql-server – SQL server log shipping – dry-run data modification script on secondary then resume log shipping
- Sql-server – Adding another Secondary Log Shipping location
- Log Shipping – Backup Grey in Transaction Log Shipping Status
Best Answer
The primary server must retain all transactions until the secondary restores them and acknowledges to the primary.
You must constantly monitor both the primary and secondary servers to avoid this situation.