Jump to content


SQL 2008 R2 - How to shrink transaction logs via BB?

SQL transaction logs shrink

This topic has been archived. This means that you cannot reply to this topic.
1 reply to this topic

#1 Christian Scholz

Christian Scholz
  • Members
  • 9 posts

Posted 19 July 2016 - 03:41 AM

Hi all,


I'm a bit confused because I can't manange to shrink my transaction logs automatically via Barracuda Backup.


Can some1 be very kind and post a manual what I need to do on my SQL Server 2008 R2?



1. What database model shall I use?

2. Do I need 2 backup jobs?

3. ...



The https://campus.barra...LBestPractices/ and the https://campus.barra...wToBackupMSSQL/ won't help me enough.


With our former backup technology - Symantec Backup Exec - it was so easy and now I don't have a clue what do do.


Thnx in advance!


#2 Shawn Lubahn

Shawn Lubahn
  • Barracuda Team Members
  • 126 posts

Posted 26 July 2016 - 08:49 AM

Hi Christian,


Do you know which recovery model your databases are using right now? I'm guessing you are using the Full recovery model since you referenced transaction logs. If that is the case, we will use VDI to perform those backups. This is the default and you don't need to configure anything. Transaction logs are only truncated on a full backup in SQL and are never "shrunken". Once a log grows to a certain size, you will need to perform a shrink operation within SQL.




Let me know if you have any other questions.