Barracuda Backup offsite vaulting enables customers to archive up to 12 monthly and 7 yearly historical revisions to a supported offsite destination while deleting unneeded portions of these revisions from the local device. This allows organizations to meet compliance objectives by retaining data for longer periods of time, while freeing up some amount of disk space to protect operational data. Supported data types include all file data, VMware vSphere and Microsoft Hyper-V VMs, and Microsoft Exchange and SQL Server application data.
When to Use Offsite Vaulting
The Barracuda Backup offsite vaulting feature can be a useful tool for retaining long-term archival data while reclaiming some amount of disk space on the Barracuda Backup device. Before enabling this feature, verify you understand the implications to data recoverability. Additionally, it is important to understand the use case where this feature works best. Think of offsite vaulting as a similar offering to Amazon’s Glacier data storage service, or an offsite tape service, where data is considered archived and therefore quick recovery times are not expected. Offsite-vaulted data recovery time is longer because parts of, or all of, this data is only available offsite. To recover this data, it must first be transferred back to the local Barracuda Backup device and then recovered locally.
Operational data, or data that needs to be recovered quickly and/or frequently, should never be offsite vaulted. Only data that needs to be kept for long periods of time to meet organizational or compliance objectives, and where recovery time is not a priority, is a candidate for this feature. Offsite vaulted data recovery time expectations should be in hours or days rather than minutes, and it is largely based on the amount of data and available bandwidth between the local Barracuda Backup device and the offsite destination.
Offsite vaulted data is visible in the Restore Browser and appears the same way as data that has not been offsite vaulted. Initiating a restore of offsite-vaulted data works the same way as data stored locally, but takes an extended period of time to recover, as noted above.
How Offsite Vaulting Works
To understand how the offsite vaulting feature works, it is important to have a basic understanding of Barracuda’s deduplication methodology. Barracuda Backup deduplicates data globally, across all backed up data sources. To achieve deduplication, all files and other backed-up data are broken down into chunks or blocks of data as it is ingested into the local Barracuda Backup device. Redundant data blocks are replaced with a pointer to the unique data block.
When a restore is initiated, Barracuda uses the pointers to reassemble the data with the unique data blocks that were written to disk on the Barracuda Backup device. Data retention works in a similar manner, as the pointers tell Barracuda which unique data blocks are required to rebuild each recovery point.
By enabling offsite vaulting, only the unique data blocks that are no longer required locally to rebuild data are removed from the local Barracuda Backup device and kept offsite. Since data is deduplicated globally across all data sources, and most of the data is kept locally to rebuild daily or weekly historical revisions, the number of unique data blocks to be removed by offsite vaulting is usually low. Customers may experience the most benefit from offsite vaulting when the source data is frequently changing between backups. A high change rate creates a greater disparity between the data needed to rebuild a monthly or yearly historical revision and a more current revision, and, in turn, increases the number of unique data blocks that may be eligible for offsite vaulting.
Figure 1 illustrates how data is deduplicated and replicated offsite. Without offsite vaulting, data retention is the same for the data stored both locally and at the offsite destination.
Figure 1. Data is Deduplicated and Replicated Offsite.
Figure 2 illustrates what happens to the same dataset when offsite vaulting is enabled. Only the blocks that are part of the monthly or yearly historical revision that are no longer needed on-premises for other datasets are removed from the local Barracuda Backup device.
Figure 2. Unique Data Blocks Removed Locally Due to Offsite Vaulting.
Configure Offsite Vaulting
Offsite vaulting only applies to historical data that has been replicated offsite. If you are already replicating data offsite and you enable offsite vaulting, the data chunks to which offsite vaulting applies are purged from the local Barracuda Backup device; no data is transferred since it is already present in the offsite destination. If you are not replicating data offsite and you enable offsite vaulting, the data is not purged from the local Barracuda Backup device. Once replication is enabled and the data is successfully transferred offsite, the offsite vaulted data is purged from the local Barracuda Backup device. Note that purging of offsite vaulted data from the local device may take between 24 and 72 hours.
Use the following steps to configure offsite vaulting:
- Log in to Barracuda Backup and select the associated Barracuda Backup device in the left pane or in the devices table (for customers with multiple Barracuda Backup devices).
- Go to the Backup > Retention Policies page.
- Click Add a Retention Policy to create a new retention policy, or click Edit to the right of an existing retention policy.
- In the Items to Retain section, choose or verify the data sources to which the retention policy applies.
- In the Retention Timeline section, specify how long the all (hourly), daily, weekly, monthly, and yearly historical revisions need to be kept.
If monthly revisions do not exceed 12 months, and yearly revisions do not exceed 7 years, select offsite only:
- Click Save to apply your changes.
Yes, I can take care of this and will publish it when I’m done, unless there’s a reason for me to hold it from publication.