ron.grout (12/18/2013)
I have log shipping set up to update two secondary databases, one on our backup server here in the UK and one on a server in our US office.I have just noticed that the restore job on the UK one failed since the 6th of December. The US database is fine and up to date.
The database is very large and takes an eternity to copy across, I am talking maybe 24 hours, especially to the US.
I wondered whether, to avoid that copy, I could switch off log shipping, wait until the restore jobs in the US are up to date, then use that database as the secondary on that server as it should be identical to the live one, when I restart log shipping.
I know that I will have to backup the live database and restore it to the backup server here but that does not take quite so long.
Any thoughts would be appreciated.
regards
Ron
Presumably you have regular full backups in force? If so it will not be possible at this late stage to repair log shipping using a differential backup as the differential base LSN will have moved on with each full backup.
If you can locate any t-log backups and apply these through the last full backup you would be fine, only problem is at this late stage the file retention will have kicked in and purged the log backup files.
You may have to re init from the beginning otherwise.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉