Jump to content

No log truncate with Full backup?


Recommended Posts

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.



Link to comment
Share on other sites

A full SQL backup does not truncate the transactional log. This is by design.










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.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...