February 28, 2006 at 7:20 pm
Greetings, I have set up log shipping. The transaction logs are being shipped from the primary to the standby server as verified by checking the backup directory. However changes to the primary are not bein applied to the standby. Using the Enterprise Manager I see that on the standby server the database is shown to be read-only. When I look at the log shipping monitor, it is on the standby server, the log shipping pair has a red 'X'. WHen I view the properties it says backup is not occurring. WHen attempting to view the copy/restore history it tells me the server must be registered. WHen I attempt to register it it tells me a server with this name already exists, which in fact it does. I am puzzled, any suggestions would be greatly appreciated. Thanks.
March 1, 2006 at 4:19 pm
In my experience the log shipping monitor has been so unreliable that I rarely even look at it anymore. If you wee the log backups at the standby server, then obviously the backup and copy are working correctly. Have you checked the job status for the restore job on the standby? You may find that the restores have been failing. If so, check the job's output for a clue.
Instead of the log shipping monitor, I have sometimes created a LAG table with one row and one column to store the current date. A job on the source periodically updates the table, and another job on the standby checks the date and raises an error if it gets too old.
March 1, 2006 at 5:11 pm
I figured out my problem. I did not check the Log Users Off Server box when setting up the maintenance plan. Checking that seems to have resolved the issue.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply