It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Backup

How do I backup my SQL Server databases with the Barracuda Backup Service?

  • Type: Knowledgebase
  • Date changed: 2 years ago

Solution #4125

Barracuda Backup Servers, firmware 3.2. and above, and associated Microsoft SQL Server running the Barracuda Backup Agent.

The Barracuda Backup Agent provides a complete backup of the Microsoft SQL Server including the Master, Model, MSDB and Pubs databases. The purpose of creating SQL Server backups is to enable you to recover a damaged database. A well planned backup strategy should be put into place to ensure a quick and reliable recovery of your database in the event of data loss.


SQL Server has three backup and recovery modes that can be set for databases - Simple, Full, and Bulk-Logged. The simple recovery model, which is the default model, supports database backups, but does not support transaction log backups. The Full Recovery and Bulk-Logged Recovery models provide the greatest protection for data. These models rely on the transaction log to provide full recovery and to prevent data loss in the broadest range of failure scenarios. Refer to MSDN Article on SQL Recovery Models for additional details. 


The transaction log is a critical component of your backup and restore strategy as it records all of the transactions and database modifications. For best practices, we recommend that you set your 'user' database to Full Recovery Mode, the system databases ('master', 'model', 'msdb', and 'tempdb') can be set to either Simple or Full Recovery Mode. Full Recovery Mode ensures you are taking advantage of log backups to restore a database to any point of time that is contained within a transaction log backup.

Follow the steps below to configure the computer and data source using the Barracuda Backup Agent:

  1. Open the Settings > Backup Management page on the Barracuda Backup Service Web interface.
  2. Click Add Computer, and then define the field values as follows:
    Assigned Backup Server. The Backup Server that you want the computer to be added to.
    - Computer Description. A name to identify the computer.
    - Computer Hostname. The name or IP address of the computer on the network.
    - Computer Type. The operating system on the computer to be backed up.
    - Windows Version. The OS version that the computer to be backed up is running.
    - Username / Password. The credentials to access password-protected servers on your network.
  3. Click Save Changes to save the computer configuration.
  4. Click Add Backup Data, then define the field values as follows:
    - Computer Name. The computer that the data is located on.
    - Data Description. A name to identify the data that is being backed up.
    - Data Type. Select SQL Server as the type of data to be backed up.
    - Send Data Offsite. Whether to send the data offsite to be backed up.
      When left unchecked, the data will only be stored on the local Backup Server.
    - SQL Authentication. This is an optional SQL login account to use in the event
      the one specified on the server does not have access to the SQL database. The
      user must be a member of the MS SQL SysAdmin server role.
    - Database Selection. Specify which databases should be backed up on the SQL Server.
  5. Click Save Changes.

Now that you have configured the data source, you should create a schedule which defines how often the data is backed up and a policy that specifies how long the data is retained. When you create a schedule for data that is being backed up using the Barracuda Backup Agent you need to specify the type of backup to run ? Full, Log, or Smart.

Refer to Solution #00003876 for details on the Agent backup types and creating a backup schedule.
Refer to Solution #00003877 for details on creating retention policies.

Additional Notes:

Shared Memory must be an enabled protocol within MS SQL. This is required for backing up MS SQL from the Barracuda Backup Agent. Having this disabled will cause backups to fail.

Link to this Page: