Barracuda Backup allows you to create several copies of your backup data in different locations, whether onsite or offsite. Barracuda Backup offers the following offsite replication options:
- Barracuda Cloud Storage
- Amazon Web Services (AWS)
- Another Barracuda Backup Device (site-to-site)
- Barracuda Backup Appliances 490 and greater
- Barracuda Backup Virtual Appliance (Vx)
- Barracuda Backup Receiver Virtual Appliance (Receiver-only, not capable of backup)
While Barracuda Backup supports multiple offsite replication destinations, only a single cloud destination is supported at this time. A cloud destination is either Barracuda Cloud Storage or AWS.
Table 1 lists all available Barracuda Backup replication options.
Table 1. Barracuda Backup Replication Options.
Barracuda Cloud Storage (1) | Amazon Web Services(2) | Barracuda Backup Appliance(3) | Barracuda Backup Virtual Appliance | Barracuda Backup Receiver Vx(4) | |
---|---|---|---|---|---|
Barracuda Backup Appliance (SOURCE) | |||||
Barracuda Backup Virtual Appliance (SOURCE) | |||||
Notes: (2) Requires a Barracuda AWS Replication subscription on each Barracuda Backup device. (3) Requires a Barracuda Backup model 490 or higher to receive data. (4) Requires a Barracuda Receiver Vx subscription for physical appliances. A dedicated Receiver Vx is included with every Barracuda Backup Virtual Appliance license. |
For multisite deployments where data is replicated offsite to other Barracuda Backup devices or multiple replication destinations, Barracuda Backup supports a number of replication configurations, including one-to-many, many-to-one, and one to both a cloud destination and receiving Barracuda Backup device.
Figure 1. One-to-Many Replication Scenarios.
Figure 2. Many-to-One Replication Scenario.
When using a many-to-one replication model, it is important to understand that data cannot make two hops when being replicated offsite. Data from the originating Barracuda Backup device can only be replicated to another destination with a single hop. It cannot be replicated once, then re-replicated from the replication destination to another replication destination.