December 17, 2012 at 5:21 am
I'm getting the above error on my DR server.
The logs are shipped from live to DR & I now get this error every time. I've checked:
permissions & file location of the backup directory
version - i believe there was a bug in earlier editions but I'm on: 2005, SP4 + SU = 9.0.5069
checked the registry settings for the backup directory point to the correct & accessible dir.
I've re-log shipped twice now but still get the error.
I have log shipped this db for 2 years without the error & I'm unsure why I am only now getting the error / what has changed.
Any ideas on what else to check or do gratefully accepted.
December 17, 2012 at 6:42 am
I don't think this has to do with the log files from the production system. Is the DR database in STANDBY mode (i.e. readonly) between log files being received from the production system? The error message to me indicates that this is the case and that the file used to support standby mode can't be found to applly the next log file.
December 17, 2012 at 9:50 am
Thanks for the response.
The DR db is in standby / readonly.
The log shipping is set up for 'standby mode', 'disconnect users when restoring backups'.
I have a few dbs log shipping in the same fashion, with the same settings. That's what's puzzling me for this one.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply