Sburk Posted January 29, 2010 Report Share Posted January 29, 2010 Why does Retrospect not truncate the log when performing a full MSSQL backup? This is pretty standard and is the default in which the local sql agent operates. Is this by design? If so, how can I make the log truncate kick off immediately after performing a full backup? I know the obvious is to schedule a log truncate job right after the Full backup, but that proves tricky since the backups run at a variable duration. Thanks! Quote Link to comment Share on other sites More sharing options...
emulator Posted February 1, 2010 Report Share Posted February 1, 2010 A full SQL backup does not truncate the transactional log. This is by design. http://technet.microsoft.com/en-us/magazine/2009.02.logging.aspx http://www.sqlservercentral.com/Forums/Topic567010-357-1.aspx http://serverfault.com/questions/54958/sql-server-2005-2008-does-full-backup-truncate-the-log-in-full-recovery-mode http://www.sqlskills.com/BLOGS/PAUL/post/Misconceptions-around-the-log-and-log-backups-how-to-convince-yourself.aspx What we do is the following: 1. perform Full backups every 48 hours 2. perform log/no truncate backups every hour 3. perform log/truncate backups once a week This schedule keeps our transactional logs from growing too large. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.