Specifications

the page. Data sources that can be backed up using the Agent are automatically detected after the computer isSYSTEM > Software Downloads
identified on the pageBACKUP > Sources
The Agent searches the NTFS change journal to track modified, added, or deleted files rather than searching the entire volume to improve Agent
backup speed.
Microsoft Exchange Storage Group Backup
The Barracuda Backup Agent (Windows) provides a full backup of the for Exchange Server 2003 and 2007. AnExchange storage group
Exchange storage group is a container for your email database and its associated system and transaction log files.
Microsoft Exchange uses transaction logging to commit new and changed data to the database, and to ensure that records of the transactions
exist if a store is damaged between backups. The Exchange storage group, and its associated transaction logs, is the most important data to back
up on your Exchange Server to ensure your email database is available in the event it becomes damaged or unrecoverable. If you must rebuild a
server, you can use the latest transaction log files plus the last full backup to recover your database.
The Barracuda Backup Agent (Windows) backs up and restores the entire storage group; it allows for the storage group to be restored to a
storage group or to an alternate Microsoft Exchange Server.
Microsoft Exchange Server Message-Level Backups
Message-level backup provides a quick way to restore single email messages to the original location or to an alternate mailbox. Message-level
backup is not intended to be a disaster recovery option for your Microsoft Exchange environment. The allowsBarracuda Backup Agent (Windows)
you to back up the entire Exchange Information Store and should be used for disaster protection.
Novell GroupWise Message-Level Backup
Barracuda Backup connects directly to to back up individual emails stored within user mailboxes.Novell GroupWise
®
Microsoft SQL Server Backup
The Barracuda Backup Agent (Windows) provides a complete backup of the including the master, user, model, msdb, andMicrosoft SQL Server
pubs databases.
Barracuda Networks recommends that all of the Microsoft SQL Server user databases be configured for full recovery model so that transaction
logs can be backed up. This allows you to restore a user database to any point of time that is contained within a transaction log backup.
Some versions of the Microsoft SQL Server, such as SQL Express database, do not support full recovery model. If the full recovery model cannot
be used, the Barracuda Backup Agent (Windows) performs full backups of the database each time a backup runs.
The Microsoft article , provides more information about the Microsoft SQL Server and its three database recoveryRecovery Models (SQL Server)
models, and how to change the recovery model of a database.
Barracuda Networks recommends that you back up the master database each time it is changed. The master database contains configuration
information that is required to restore an instance of SQL Server.
Microsoft Hyper-V Virtual Machines
The Barracuda Backup Agent (Windows) provides application-aware backups for hypervisor-based virtualization systems, andMicrosoft Hyper-V
provides support for open file backups, file attributes, and permissions as well as automatic data source detection.
Windows System State Backup
The Barracuda Backup Agent (Windows) can back up and restore the Microsoft Windows System State. Microsoft Windows System State
backups allow backup of critical system related components, including the local Registry, COM+ Class Registration Database, the System Boot
Files, Active Directory Database Files (NTDS.DIT) for Domain Controllers, and the SYSVOL folder. A System State backup can be used to
recover to a known good system state after a hardware or software crash.
Important
Do not use other methods to back up Microsoft SQL Server databases, such as Microsoft or third-party utilities, when using the
Barracuda Backup Agent (Windows). If you use more than one back up method on the same database, one or more of those methods
causes the Microsoft SQL Server to truncate the transaction logs. This forces a full backup of the database every time, and can result in
data that cannot be restored.