Log Shipping Copy Just Stops

Question

Log Shipping Copy Just Stops

tmarfori

Valued Member

Points: 61
More actions
April 15, 2003 at 12:05 pm

#159483

I've set up a Maintenance Plan to take a Transaction Log Backup and to Log Ship to a warm server standby for each of my 12 production databases. I've set all of them up exactly the same. The strange thing is that they all work for a couple days, meaning they Backup the transaction logs every hour, Copy the logs to the destination server directory and Load the logs.
Then, without any error messages anywhere, the Copy just stops. And it's not on all the Log Shipping databases, only some of them. So I do have some databases that are still successfully being log shipped. When I view the Copy/Restore History, both the copy and load appear to still be executing because it's status is Succeeded but the # Files is always zero.
If I manually copy the logs to the destination server directory, log shipping will load them. I haven't had any luck trying to restart the copy, which has forced me to remove log shipping, restore a backup and then reestablish log shipping.
So why does the Copy just stop?
I think I've ruled out permissions because they do run for a couple days. Same with the shared directory. Has this happened to anyone else? HELP !!

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

dgermundson Hall of Fame Points: 3175 More actions · Answer 1

Are you running out of disk space? Are you running the logs with the NOINIT option so it's appending the logs and taking up excess space? Have you monitored the server processes while it's running to see if the server is running out of memory possibly?

Darren

tmarfori Valued Member Points: 61 More actions · Answer 2

Thanks for your reply Darren.

I've checked space and I have over 20 Gig free on all servers in question (way more than enough). Also, I do have databases successfully log shipping from the same source server to the same destination server as the databases that are failing, so I believe both source and destination servers have sufficient resources like memory etc.

Can you think of anything else?

Thanks.

dgermundson Hall of Fame Points: 3175 More actions · Answer 3

The only other suggestion is to run system monitor while this is running next time and look for any outliers. Like CPU and memory usage on SQL Server.

Darren