If a write on log shipping transaction backup gets corrupted on one of the transaction file due to network or media issue, and hence the log shipping chain gets broken, is there any other way to restore the database to the point in time ? I understand one could do full backup or diff backups but to restore to point in time, how can we get the consecutive tran logs to be restored?
Any pointers on this will be beneficial.
Thanks
(Even if the solution is to contact Microsoft or only God can help you, I will buy that :-))
Sql-server – Log-shipping : Broken Chain
log-shippingsql server
Related Question
- Sql-server – Transaction log rollback broke Log Shipping chain?
- 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 – How to Fix Slow Restore in SQL Log Shipping
- Sql-server – Log shipping always failing with NUL
- SQL Server Log Shipping Retention – Managing Log Shipping Retention in SQL Server
Best Answer
If you are saying your actual backup file is corrupted (the .trn file) but that the backup was successful from SQL Server's perspective, and the source DB is still online, I would take a full backup as soon as possible so you don't lose any data.
You will have to rebuild your log shipping if you've got a corrupt .trn, but your main concern should be having the ability to restore your source data at all if you've got a bad .trn in your chain.