September 30, 2009 at 8:11 am
Hi
I am trying to set up log shipping on 2 databases which in production are on 2 separate instances and on DR they are on the same instance. When i set up one of them it is successful as soon as i set up the 2nd one it causes the first log shipping restore to fail with an out of sync error and if i try the other again the same thing happensl. The log ship folders are on the same drive in different folders. It appears to be a conflict of something i just dont know what and its driving me mad we have been working on it for a week and still no joy
Anyone help???
Thanks
September 30, 2009 at 8:35 am
Naming conflict somewhere? maybe with the job names? I assume the dbs are differently named?
September 30, 2009 at 8:37 am
Yes they are completely different names although i do tell it to go to the same Y drive but it seems to store them in different places but still on a Y drive - hope that makes sense
September 30, 2009 at 8:45 am
What are the errors?
A few things to check:
- Are the files written correctly to the different folders? Meaning they look like the correct log backups from the source systems
- Do the restore jobs fire?
- Are you setting different delays for restore?
- Are you offsetting the restores of the two dbs?
September 30, 2009 at 8:50 am
Hi yes the logs are being written correctly, only one of the restore jobs runs the other always fails as soon as i set it up, they have the same delays as they are restoring to different db's both are every 2mins at 2min intervals
September 30, 2009 at 10:08 am
Please post the error that it throws when
restore job fails?
October 5, 2009 at 2:27 am
Hi
There is no error unfortunately it just stops the other log shipping stating it is out of sync.
Thanks
October 5, 2009 at 3:46 am
What is your output if you run a RESTORE VERIFYONLY FROM <backup_device> against the TLog backup file to imported?
I use to administer a system which backed up its TLogs at 1 min intervals would occasionally write two files into one backup log. We would then get an LSN out of synch (or such) error.
If you have more that one file, check the LSNs for the files and the DB. If this looks like it is the problem, restore the TLog again with a WITH FILE=n into your RESTORE LOG command for each file > 1; then try the next log restore.
You may need to make a code change to your restore routine to pickup all files within a TLog backup. If you run a RESTORE LOG ... WITH VERTIFY_ONLY, an entry is written into msdb..restorehistory. If you pick out the entries for your database with restore_type = 'V'
Hope this helps as it's been a while since I last touched log shipping.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply