May 2, 2006 at 12:57 pm
Hello, I have just set up log shipping and it is functioning properly. Now I want to set up backups of the primary. I have seen some discussions that indicate there are certain steps which need to be followed when backing up the primary due to the way SQL Server does backups of transaction logs. I am looking for guidelines on how to do this. Do I set up a maintenance plan to back up the primary and then rely on the transaction logs left on the primary server in the event I need to restore the primary? Any suggestions would be greatly appreciated. Thanks.
May 3, 2006 at 3:29 am
never had any problems making database backups of ( ms ) log shipping databases, scheduled nightly backups of databases, log shipping continued unaffected.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
May 3, 2006 at 8:46 am
Don't take log backups of the database which is getting shipped because this will break the LSN chain of the logs getting applied on secondary.
as indicated by "colin Leversuch-Roberts" Full backup is not a problem.
May 3, 2006 at 10:47 am
Thank you both for your responses. Is timing an issue? For example, if my log shipping is scheduled to run every 30 minutes on the hour and on the half hour can I schedule the backup at the same time or should I stagger it? Thank you both for your replies.
May 3, 2006 at 12:38 pm
The database backup will block the log backups. (And vice versa, I believe.) I would schedule the database backup to start just after a log backup. That gives you the maximum window to complete the db backup before the next log backup occurs. If one starts while the other is running, it will wait until the locks are released.
May 3, 2006 at 2:03 pm
Thanks again for the replies. Does anyone know if there is documentaiton available which discusses this issue? Thanks.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply