Scenario 7: Backup using the Cloud plugin

In this scenario we will backup a Linux and/or Windows client from BWeb Management Suite using the “S3 Cloud” Storage daemon plugin. We will use Amazon’s Simple Storage Service (Amazon S3) object storage architecture to store the cloud volumes. Alternatively, you can also see the video: How To: Add Cloud Storage in Bacula Enterprise

For convenience and ease of testing the “S3 Cloud” plugin, the Trial VM has a “FakeS3” service already installed, and configured with a test bucket called “BaculaTrialS3Bucket”. An “S3 Cloud” resource, and an “S3 Autochanger” with two S3 devices has already been pre-configured on the Trial VM. Additionally, there are several jobs already configured to write to this local “FakeS3” cloud storage service. This configuration mimics the behavior of the Bacula Enterprise S3 cloud storage plugin by writing to a local S3 storage provider.

For a Windows client, it will be necessary to have a Windows system (on physical hardware or a virtual machine) with the Bacula Enterprise Edition File Daemon installed as described in scenario 5 above.

For a Linux client, the one already installed for the Trial will be used.

To follow the examples in this scenario, you will need an Amazon Web Services (AWS) account to store your backups in the cloud.

If you do not have, or do not want to use your current cloud provider, we recommend that you create an Amazon Web Services (AWS) account and follow the AWS Best Practices to create a restricted user with credentials to be used with the Bacula Enterprise Trial, only for backup purposes.

Please go to to find more information and to create your AWS account.

Please find the AWS Best Practices guide here: .

Configure Bacula Resources

To be able to use the Cloud plugin, we will create a new Cloud resource and a new Storage using BWeb Management Suite.

  1. In BWeb Management Suite, click Configuration –> Configure Bacula.
  2. Enable the Autocommit feature by clicking the “Autocommit:” slider in the far right side of the Main Menu:
  3. In the left column, click “Add a New Storage Resource” button
  4. In Step 1 of 4, click the “Select a Storage Daemon and add newly created Devices into it” radio button, and then select the “bacula-enterprise-trial-sd” from the “Storage Daemon” drop-down menu, and “Cloud Virtual Disk Changer” from the “Device Type” drop-down menu:
  5. Click “Next” to move on to Step 2 of 4 in this wizard.
  6. In Step 2 of 4, select the “S3Autochanger” from the “Copy from existing Storage” drop-down menu. The rest of the fields will be automatically populated.
  7. Click “Next” to move on to Step 3 of 4 in this wizard.
  8. Fill in all the information as shown in the image below. Please note that the Region field at the bottom may need to be modified to match your environment.
  9. For the “Bucket Name:” field, you may type in the name of a new bucket, and one will be automatically created. Optionally, you may click the “Select existing bucket” icon, and you will be presented with a list of existing buckets to choose from. For example:
  10. Once the bucket is selected, click on the “Cloud link status:” icon. Bacula will check connectivity and credentials, and this icon should change into a white check mark in a green circle:
  11. The “Where volumes will be stored on the local disk” field is important in this page. The directory specified must exist, and there must be enough free space to store Cloud volumes in this “local cache”. The Bacula Enterprise Trial has a 200GB disk mounted under /mnt/bacula where all backup jobs (file, dedup, S3 Cloud) are written. It is safe to create a new directory (eg: /mnt/bacula/My_Cloud_Test) under here that Bacula can use as the local cache for testing your backups to a real S3 cloud provider. Please make sure the permissions to the folder created permit the user “bacula” to write to it. For convenience, the Trial VM already has a directory called “/mnt/bacula/Cloud_Test_Wizard” with the correct permissions and ownership, so you may use it here rather than creating your own. If you choose to create your own, please follow the instructions in Step 12, otherwise you may skip Step 12.
  12. If you decide to create your own local cloud backup directory, please log into the Trial VM and run the following commands:

    $ ssh root@<IP Address Of Trial VM> (password “bacula”)
    # mkdir -p /mnt/bacula/My_Cloud_Test
    # chown bacula:bacula /mnt/bacula/My_Cloud_Test
    # chmod 750 /mnt/bacula/My_Cloud_Test
    # exit
  13. Click on the “Next” button to be taken to Step 4 of 4 in the wizard.
  14. On this page, enter a name and an optional description for this new Cloud Storage:

Click on the “Save” button.

Your new Cloud resource and a new S3 Autochanger with ten read/write devices and two read-only devices is now ready for use.

You can check the connection status between the new Storage created and a Client previously created. To do this, we first need to leave configuration mode by clicking on the Bacula Enterprise title on the top menu.

Next, select Storage from the main menu, then Storage Overview. Choose the newly created S3 Storage from the drop-down list. Click on the Network test button. A new window is displayed. Select one client in the Client list and the newly created S3 Storage device in the Storage list. Then click on the Run Test button. You should have an output like:


Part 3 – Backup to the Cloud

If both the Status and Network tests run as expected, the next step is to run a backup job to the new Cloud storage device.

You can use Scenario 1: “Backing up “all” files on the Trial VM using BWeb Management Suite” to run backup tests for a Linux host, and you can also use Scenario 5: “Backup a Windows client with BWeb Management Suite” to run backup tests for a Windows host. In each backup scenario, you will need to manually modify the storage so that the backup job uses your newly created cloud storage resource. This is accomplished in the BWeb manual job run wizard (click Jobs → Defined Jobs and select the job you want to run) during step 2 by clicking the ‘Where’ icon.

When testing restores, you can use Scenario 2: “Restoring files from your previous backup using BWeb Management Suite” to run restore tests for the Windows and Linux hosts.


Congratulations! We hope that you enjoyed using Bacula Trial Edition. You still have the opportunity to further test some of your Bacula Trial installations’ other features. Please refer to our main manual, in particular the chapters “A Brief Tutorial” and “Getting Started with Bacula“.

If you have any comments or suggestions please fill out the feedback form and let us know. We’ll get back to you in a timely fashion, and would like to thank you in advance.

For more information about plugins, support options, features, training and pricing, please contact the sales team via our contact form.

If you are not able to complete these scenarios, or have a technical issue regarding any products, please contact the support team via the welcome screen of the .ova, as below:

Bacula Enterprise is used by a large number of high-profile customers, where each one exploits the special qualities of Bacula in a variety of different ways. Bacula Systems looks forward to bringing the same benefits to your organization; please contact us to find out how we can best help you to move forwards, modernize your backup and recovery strategy, and significantly reduce costs.

Bacula Enterprise Features Overview


With our best regards,
The Bacula Systems Support Team

Additional notes: The Bacula Enterprise Trial VM will stop working after 30 days. If you would like to continue testing after this time, you can simply click the “Reset Bacula Enterprise Trial environment” icon on the Landing Page, or re-import the Trial ova.

How useful was this Trial Guide?
1 Star2 Stars3 Stars4 Stars5 Stars
(1 votes, average: 5.00 out of 5)