March 19, 2007 at 10:41 am
All,
Apologies if this is posted in the wrong place. I've setup log shipping between two servers. The destination database did not exist and the wizard seemed to creat it fine. I've tried it several times and each time I get an error on the log shipping monitor saying that the log file in the first_file is too early to upload.
I would guess that is because I asked the wizard to create a new backup to create the new database and the log is actually older than the new database?
The problem is that I think it's stopping any subsequent log shipping from working because the monitor shows the last copy/upload to be the time of the initial backup.
Also, perhaps someone could explain the difference between standby mode and no recovery as I am strugging to understand the difference in terms of log shipping. Both modes must be able to receive logs and become the primary server?
Thank you
Andrew
March 20, 2007 at 6:31 am
Good morning, Andrew. As for getting your log-shipping back on track. Stop (disable) all log-shipping jobs (transaction log backups and transaction log restores). Next, take a full backup of the primary and online database. Apply this database to the standby copy, in standby mode, allowing restores of additional transaction logs. Then re-enable the jobs disabled above and run the transaction log back-up job, followed by the transaction log restore job and your log-shipping should be back on track. I hope that this helps. Thanks.
Chris
March 21, 2007 at 7:08 am
Chris,
Many thanks for your reply. I did as you suggested and now the backup job on the source is telling me that it failed and the source db has not been backed up for 7096 (for example) minutes. I'm not sure if it's referring to a full backup or a transaction log backup. If it's a full backup then I've just done it and if it's a transaction log then that's the job that should create them?!
Sorry I feel like I'm missing the obvious somewhere but I don't know where.
Thanks
Andrew
March 21, 2007 at 7:35 am
Andrew, was the first part successful -- the full backup and restore?
If so, the worst case scenario is to just re-create the log-shipping job.
Thanks...Chris
March 21, 2007 at 7:35 am
Andrew, was the first part successful -- the full backup and restore?
If so, the worst case scenario is to just re-create the log-shipping job.
Thanks...Chris
March 21, 2007 at 8:59 am
Chris,
The first part was successful. The problem is that this happens every time I recreate the log shipping maintenance plan.
Thanks again
Andrew
March 21, 2007 at 9:05 am
Andrew, just be sure -- double check the schedule -- that your restore job runs after your backup job. Other than that, I don't know what else to tell you. Sorry! Perhaps someone else will have a better solution. Thanks.
Chris
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply