January 7, 2005 at 8:58 am
Sorry, Yes it is. Unfortantly, the log shipping has failed again so i am back to square one. However, you did bring up a good point that might be causing the problem. When I do the back up am doing it through my loggin connection. When the restore is done it is using the administrators loggin to restore. Perhaps, this is the problem. In this go around I am logged in and actually doing the back up from using the same loggin id as the standby or restore. I am going to also backup from that database server and then restore logged in to the restore server for the restore. Hopefully, I made since. Before I was backup the database from my machine logged in as me.
January 7, 2005 at 9:37 am
Are you using MS logshipping or a homegrown version?
January 7, 2005 at 9:47 am
Its a modifed version of MS. It has been working.
January 7, 2005 at 12:19 pm
If you're having trouble with the restore you could always do the db backup/copy/restore through the maintenance plan gui.
The other thing that can screw up logshipping is having more than one logshipping monitor server within the same subnet. If you logship to more than one place, check that this is not the case.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply