May 15, 2012 at 1:37 pm
I have a very small window for server maintenance on 1 server. If for some reason I need to reboot a server while a t-log backup is running, how does SQL handle that when the server is back up ? Does it regard the log backup as not having occured, so the next backup will maintain the log chain ?
Perhaps cancelling the job manually before rebooting would be a better option so SQL can rollback ?
May 29, 2012 at 4:31 am
Can the t-log backup be scheduled so that its complete in time for the server reboot?
Your transaction log should not truncate until it is backed up
May 30, 2012 at 2:09 am
Will not be a problem
You will see a .trn backup file but it will not be visible in the backup history because the backup was interrupted. You can try restoring it, it will not work. Only what's recorded in the backup history can be considered valid.
So you can even safely delete the partial backup file if need be
And of course the next successful trn log backup will include all the necessary info to maintain the log chain
May 30, 2012 at 2:10 am
The only thing I can find about this says the backup can be resumed from where it was interrupted, but it doesn't actually say how you do this:
http://msdn.microsoft.com/en-us/library/aa213840%28v=sql.80%29
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply