July 11, 2006 at 11:08 am
Greetings, I have configured log shipping using SQL Server 2000 SP4 running on Windows Server 2003. My question concerns rebooting the members of the pair. If I reboot either member of the pair will SQL Server recover gracefully, figure out where it is and proceed accordingly or will the log shipping then be broken. For example, if the primary is down for maintenance at a time when the transaction log is scheduled to be backed up will SQL Server be aware that it missed a backup and recover correctly? By the same token if the standby server is down for maintenance and thus the primary is unable to connect to it will it fail or will it keep trying until the standby is back and not lose anything? I have been unable to find any information on how this works. Thanks.
July 11, 2006 at 2:51 pm
You should not have a problem if either partner goes off radar for a while, as long as they come back online before the log backups start aging out.
July 11, 2006 at 3:52 pm
Thank you. One additional question is what if the machine is rebooted while the backup or copy process is occurring? Will SQL Server be aware of this and rollback the inprocess backup or copy? Thanks.
July 12, 2006 at 2:29 pm
Here too you should not have a problem. If the source is rebooted while doing a log backup, then the backup will fail, and the transactions that would have been in the backup will be part of the first backup after the reboot. If the destination server is rebooted during copy or restore operations, then it will wuccessfully redo the missed work with the next run.
July 12, 2006 at 3:32 pm
Thank you.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply