Home > Welcome to the Bacula Enterprise Trial > Using Bacula Enterprise Trial > Scenario 6: Backup using the Cloud Plugin

Scenario 6: Backup using the Cloud Plugin

In this scenario we will backup a Linux and/or Windows client from BCenter using the “S3 Cloud” Storage Daemon plugin. The Amazon Simple Storage Service (Amazon S3) object storage framework will be employed to save the cloud volumes.

For a Windows client, it is necessary to have a Windows system (either on physical hardware or a virtual machine) with the Bacula Enterprise File Daemon installed, as described in Scenario 5.

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 creating an Amazon Web Services (AWS) account and following the AWS Best Practices to create a restricted user with credentials specifically for the Bacula Enterprise Trial, solely for backup purposes.

Go to https://aws.amazon.com/free/ to find more information and to create your AWS account.

Configure Bacula Resources

To be able to use the Cloud plugin, we will create a new Cloud destination using BCenter.

  1. Go to the “+” icon on the left menu, and select “Add destination”.
  2. In Step 1 of the “Add destination” wizard, it is necessary to choose the storage type. Ensure to mark the checkbox labeled “Cloud Storage (S3 Compatible, AWS, Google,…)”. Following that, select the Provider AWS and a Storage Daemon from the provided drop-down menus. Finally, click on “Next”.
  3. A window will appear, requesting AWS credentials. Enter the URL, the Access key, and the Secret key. Then click on “Done” to proceed to Step 2.
  4. Choose a bucket from the list of available ones, and click “Select”.
    Click on “Next”.
  5. In Step 3, you have the option to choose parameters such as Storage class and Maximum upload/download speed. Keep the default values and click on “Next”.
  6. A window will pop up, and you will be asked to enter a name for the new destination. Click on the edit icon located to the right of the name field, and write a meaningful label for the destination. Then click on “Done”.
  7. Finally, in Step 4, you will receive a summary of the newly configured Cloud destination.Click on “Close”.
  8. You will be then redirected to the “Destinations” page. Ensure that you refresh your browser page by clicking on the circular arrows and select the “Cloud” tab. The newly created destination will be listed below.
  9. Now, return to the “Dashboard” page from the left menu. Under “Destinations”, you will find the new entry in the “Cloud” set.

Backup to the Cloud

The next step will be to run a backup job to the new Cloud storage device.

You can use Scenario 1: “Backing Up “All” Files on the Trial Linux VM using BCenter” to run backup tests for a Linux host, and you can also use Scenario 5: “Backup a Windows Client using BCenter” to run backup tests for a Windows host. In each backup scenario, you will need to add a new source so that the backup job uses your newly created cloud storage resource. This can be achieved by clicking on the “+” icon in the upper left corner, and selecting “Add source”.

When testing restores, you can use Scenario 2: “Restoring Files from the Previous Backup using BCenter” to run restore tests for the Windows and Linux hosts backed up data sent to the cloud.