Bacula delivers natively integrated AWS S3 backup solutions for the enterprise cloud-based backup and recovery. It delivers native integration with public and private clouds via the Amazon S3 interface, with transparent support for S3-IA. AWS S3 backup is available for Linux, Windows and other platforms. But there’s something else your company needs to know about Amazon S3 backup with Bacula Enterprise: the ability to bring significant cloud cost reduction for AWS backup solutions.
First of all, if you don’t know the process of adding new storage to Bacula Enterprise – you can fix that by watching a video about it on our website. This part will mostly skip everything about that process and focus on the demonstration of adding S3 cloud backup storage to the system through BWeb.
To begin the process of adding the new AWS backup storage, you’ll have to enter configuration mode first.
After that you will be able to see several new options available. You need the one titled “Add a New Storage Resource”.
In this specific example we’re adding Amazon S3 backup storage to an existing storage daemon. We’ll also choose the “Cloud Virtual Disk Changer” under the “Device Type” – this device type allows for several simultaneous backups to the same cloud storage.
Since our storage daemon already exists – all of the information at step 2 (Configuring a new storage resource) can be taken from the previously created devices.
A third step of this process is the AWS backup storage information configuration. In this example we’ll be storing our backup volumes in the cloud cache, which is usually used as a small temporary area in-between loading a backup to a cloud, but it can still hold a week or more’s worth of the data to allow local backups for that period, and cloud backups if the time period is longer than a week. You can always contact Bacula support to know more about cloud cache’s storage size, cache retention policy and cloud upload behavior.
One more part of step 3 is choosing your future cloud driver from a list of supported ones.
As you can see, at the moment of conducting this example we support Amazon S3, Azure, Oracle and Google. Keep in mind that the list is constantly expanded, so you can always connect with us to know if a specific cloud provider of your choosing is supported by us or not.
In this example we’re choosing S3 backup driver. Next we’ll have to set up a list of arbitrary information like cloud hostname, account info, region and so on. You’ll also have a choice between choosing an existing bucket by connecting to your existing account or to enter a name in the corresponding line to confirm the creation of a new bucket.
After all that there are two possible options left: cloud link status and “upload to the cloud during the job”. Cloud link status button allows you to immediately check your current system’s connection to a cloud of your choosing. “Upload to the cloud during the job” is an option that is chosen as a part of default settings to upload your backed up data to the cloud as soon as it’s ready (even in the process of a backup job), but you can also disable this option if you wish to upload after a job is finished or with some other schedule in mind.
Step 4 of this wizard would consist of simply typing in your preferred storage name and optional description.
After this step you can push the “Save” button to allow all of the previous changes to be committed to production. Keep in mind that in order to properly commit everything to production you’ll have to reload your storage daemon, meaning that any job that is running would fail in the process.
A logical step after this would be to set up new backup pools for this specific cloud storage and to properly configure jobs to write data to the new pools. You can address Bacula’s documentation, contact our support or see our YouTube channel to get help in regards to these steps.
To test that everything we’ve just done works properly, we’ll run a small full AWS backup job manually directly to the new storage device. Usually this process is automated using a job schedule and/or other configurations.
Minimal restore cost. Recover only exactly what you need from AWS S3 Backup Storage.
Read the datasheet to find out more on how this cloud backup capability, combined with special management tools, provides data center managers with the most integrated cloud-connecting backup software for their entire physical and virtual environments regardless of architecture – all from a single platform.
Disaster recovery can now also be delivered in a cloud-computing model so recovery resources are only paid for when they are used, making it more efficient than a traditional recovery warm site or hot site where the recovery resources must be running at all times. AWS disaster recovery services can be also implemented with Bacula Enterprise functionality.
Some key features of Bacula's AWS S3 backup solutions:
Further help on AWS S3 backup: