Is it possible to force SQL Log Shipping to run from a given .trn file onward?
I have two databases, where one ships to another this was working fine. However I had to restore the primary database and in the interim another .trn file was created. (This would be rubbish given the DB was restored and so couldn't be applied anywhere.) For the next transaction I manually backed up the whole database, and could manually restore it to the logship destination. (13.trn below)
The next transaction file that was created could also be manually restored. However the jobs are stuck on the transaction before the full backup, (12.trn below) and of course the job is failing as it is behind the destination db.
If I can set it to try 15.trn, it should (probably) work! I've tried changing msdb..log_shipping_secondary_databases to no avail.
So, is it possible to set which file sqllogship.exe uses next?
Basic example below!
10.trn 11.trn <DB Was Restored> 12.trn 13.trn (contains full backup) 14.trn 15.trn