Additional Datasheets:


Important Note: As of 15 July 2019, the Trial software has been updated. The latest version is faster to load and easier to use with new features. We recommend all Trial users to benefit by going to this link and starting over using the new guide and latest .ova file.

Thank you for assessing
Bacula Trial Edition: Bacula is the leading Enterprise Open Core network backup and restore software, and the purpose of this special trial software is to provide you with the best possible experience as you evaluate our Enterprise products.

The Trial Kickstart is intended to be used as a proof of concept. It allows the testing of all Bacula Trial products and installation on the clients of all supported platforms.

It also provides an automated way to install the Linux operating system on physical or virtual machines for the purpose of testing Bacula Trial Edition in a live environment. It is based on the CentOS Linux distribution and is designed to be installed and ready to use in 30 minutes.  The resulting installation is intended to be administered using BWeb or the Linux command-line.

We will kindly ask you to download the Trial Kickstart and then to start the installation. To be introduced to Bacula Trial Edition, you can simply play with the software by following some scenarios as described later in this guide. These scenarios are designed to demonstrate the basic functionality of Bacula Trial Edition. If you are not able to complete these scenarios, please contact us. You can also check Bacula Enterprise Edition's numerous features and configuration possibilities in the general Bacula Manual (access to the specific Bacula Enterprise Edition manual is restricted to Bacula Systems' subscribers). The Bacula Manual's key introductory sections are: A Brief Tutorial for getting started quickly, and Getting Started with Bacula for an introduction to Bacula Enterprise Edition.

Remember, more advanced features and plugins are available on request.


Introducing Bacula Enterprise

Let's have a look at the main components of Bacula Enterprise and how the data and commands flow between them.
Bacula Principles
Bacula Enterprise is composed of five main components:
  • The Director which supervises all the backup, restore, verify and archive operations.
  • The Storage Deamon is the software that performs the storage of the file attributes and data to the physical backup media.
  • The File Daemon or Client is installed on each machine to be backed up.
  • The Catalog is responsible for maintaining the file indexes for all files backed up.
  • The Consoles allow the user to interact with the Director. It is available in two versions:
    • a text-based console interface, called BConsole.
    • a web interface, called BWeb Management Suite.
For more detailed information, please refer to our main manual.

With the Trial Kickstart, you will also find three White Papers related to specific features:
  • The Global EndPoint Deduplication plugin, to help you test the Bacula Enterprise Edition deduplication feature for both the Storage Deamon and the File Daemon (the agent). Download the technical White Paper here.
  • The MSSQL plugin, showing how to back up and restore your MSSQL databases. Download the technical White Paper here.
  • The VSS plugin, giving you instructions on how to take a snapshot of your Windows system state. Download the technical White Paper here.

Minimal Requirements

The Trial Kickstart is delivered in the form of an ISO DVD image file.

This image can be booted natively by VMware and VirtualBox (regarding VM's, please specifically use one of these two), and it can also be burned onto a DVD for installation on a physical machine.

All CentOS updates available as of the release date have been merged into the Trial Kickstart ISO image.  Additional updates can be installed automatically if your network provides internet access.

The Trial Kickstart can be installed on both physical and virtual servers that are compatible with CentOS Linux.  The server should meet the following minimum specifications:

    * Compatible with CentOS 6.
    * Bootable from ISO image or physical DVD.
    * 64-bit AMD64/Intel CPU supporting the x86_64 instruction set.
    * Minimum 4GB of RAM for large-scale use (2GB is ok for small-scale tests).
   * Internal hard disk greater than 100GB in capacity, or greater than 200GB to test the optional VTL or our universal deduplication capabilities.
    * At least one ethernet interface on your network.

If installing on a virtual machine, it is strongly recommended to use a single virtual hard disk that is large enough to accommodate the operating system and backup storage space.

Step 1: Pre-installation

The Bacula server should be physically connected to your network prior to running the Trial Kickstart.

The following settings need to be available to ensure a successful installation.
Using incorrect settings will result in an unusable installation.

    * Keyboard Layout
        The country-specific keyboard code used by the Bacula server. Please refer to this list, in the chapter named "Keyboard".

    * Timezone
        The system timezone for the Bacula Trial Edition server. Please refer to this list.

    * Hostname
        The un-qualified "short" hostname for the Bacula server.

    * Domain (not required if using the DHCP feature)
        The DNS domain name for your network.

    * IP Address (not required if using the DHCP feature)
        The IPV4 network address for the Bacula server.

    * Netmask (not required if using the DHCP feature)
        The IPV4 network mask for the Bacula server.

    * Primary and secondary DNS servers (not required if using the DHCP feature)
        The IP addresses for the DNS servers on your network.

    * NTP Server (optional)
        The IP address of your network time protocol (NTP) server.

    * SMTP Server (optional)
        The IP address of your mail server.

    * Passwords for the root user on the system and for the Bacula Enterprise users
        The passwords that will be used for root and bacula accounts in the Linux
        operating system and PostgreSQL database.

Step 2: Installation

Download the ISO image provided by Bacula Systems. If you need packages to install on your client, please download them from the same place.

If you are installing the Trial Kickstart in a Virtual Machine, please use the downloaded ISO to boot the VM. If you don't want to use a 100Gb partition as indicated in the requirements, please use the boot option in step 4 to install on a physical server to have the option to choose the partition's size. If you are using a physical server, select the media type your would like to boot your server on this ISO image.
  1. Boot from ISO image. The installer offers you the choice to install to a physical machine or to a virtual machine.

  2. Follow the wizard asking for your keyboard layout and time zone.

  3. Hard disk configuration.

    • If installing on a virtual machine, a single hard disk will be assumed and a default partition layout used. It is assumed that virtual machines will mainly be used for testing Bacula Enterprise, not for production. We strongly recommend to install Bacula Enterprise on a physical server for better performance.

    • If installing on a physical server (or using the bare metal boot option on a  virtual machine with multiple disks), you will be prompted to specify the size of the OS partitions, optionally mirror their root disk, and create storage space using RAID. The number of choices provided depends on the number of disks detected.

  4. The CentOS system is installed. It should take about 15 minutes and certainly no more than 30 minutes.

  5. Account passwords.

    • You will be prompted to enter the passwords for the root and Bacula Entreprise Edition catalog. The entered passwords will be set both for the local Linux accounts as well as PostgreSQL accounts of the same name.

  6. Network Identification

    • You will be prompted for the hostname, domain, and dns settings.

  7. Network Interfaces

    • You will be prompted for the IP address and netmask information if you don't use DHCP as proposed.

    • If installing on bare metal, choices will be provided for optionally configuring jumbo frames or ethernet trunking. These should only be used if the environment supports it and you really require them.

  8. Network Time Protocol (optional)

    • You will be prompted for the IP address of their NTP server.

  9. Email Settings (optional)

    • You will be prompted for the address of your SMTP server. Choices will also be provided to enable SSL and SMTP authorization if the mail server supports them.

  10. Catalog Database

    • You will be prompted for the databases supported by Bacula Trial Edition. We strongly advise to use PostgreSQL database, which is more efficient with a Bacula Enterprise infrastructure.

  11. Default Volume Pool

    • The default volume pool is where your backed up data will be stored if you don't use a Virtual Tape Library or ZFS.

  12. Virtual Tape Library Settings (optional)

    • A portion of your storage can be configured as a virtual tape library. This emulates a real tape library.

  13. Dedupe Device creation (required to use the Global End Point Deduplication Plugin)
    • The Global End Point Deduplication require the creation of dedicated Dedupe Devices and Storage. Please check the scenario 6 or the Global End Point Deduplication White Paper for more information.

  14. Demo Config

    • If you wish to follow the scenarios in this guide, please install the demo config.

  15. Installation complete. A reboot of the system is required after its update. It can take time due to some recompilation.

Step 3: Using Bacula Trial Edition

In the following scenarios, you will get the opportunity to use Bacula Trial Edition to backup and recover data using BWeb Management Suite and BConsole.

After the reboot, the Trial Kickstart displays a welcome page that gives you the information you need to access BWeb Management Suite, the monitoring and administration web tool.

You can connect to BWeb Management Suite from Firefox (version 10 or above) from your desktop.

Scenario 1: Backing up files from /usr folder using BWeb Management Suite

BWeb Management Suite is a web interface that interacts with the Director and offers tools to run backup and restore jobs, to monitor and to configure the Bacula Trial Edition infrastructure.

  1. Open BWeb Management Suite using the link available on the Trial Kickstart's welcome page.

  2. Once on the BWeb Management Suite welcome page, you will see an overview of the current Bacula Trial Edition status. If you have not yet run any job, the chart will be empty.

  3. Let's back up the /usr directory. Click in the main menu on Jobs->Defined Jobs tab. Select usr from the drop-down menu of defined jobs.

  4. Let's click Run Job to start it immediately.

  5. The window refreshes to display the job options available. Accept the default values by clicking Run Now once again.

  6. You will be taken to the running job information window. You can click Refresh to watch the progress. NOTE: THIS JOB BACKS UP >75,000 FILES WHICH MIGHT TAKE A FEW MINUTES DEPENDING ON THE PERFORMANCE OF YOUR SYSTEM.



  7. Once the job is complete, an automatic refresh will take you to the job information window where you can see the outcome of the backup job. You can also find this information by navigating to Jobs->Jobs History and clicking on the status icon.



Scenario 2: Restoring files from your previous backup using BWeb Management Suite

Now let's restore the files to the "restores" directory located on your desktop.
  1. Select in the main menu Jobs->Web Restore .

  2. Select the client (1) in the "Select a client..." list and job (2) in the "Select a job..." list. The directory tree to restore will automatically show up on the Directories panel.



  3. In the Directories panel, browse to /usr/bin/.

  4. The content will show up in the panel Directory Content.
    Highlight some or all of the files in /usr/bin, and mouse drag them on to the Restore Selection panel located below.



  5. Click Run Restore.



  6. A Restore Selection pop-up will show up. By default, your recovered files will be redirected to /tmp/bacula-restores/ using the value in the Where field.

  7. Click on Run to start the job, and you will again be taken to a status window. A green status bar will show the job progress if you refresh the window by clicking the Refresh button.



  8. When the restore is successful, you'll be taken to a job status window and have a copy of the selected files into the restore folder, by default /tmp/bacula-restores/.

  9. To check the restored file, start a ssh connection to your server, and list the content of your /tmp/bacula-restores/ folder.

Scenario 3: Running a backup of /home/doc using BConsole

The third scenario demonstrates BConsole, a text based console interface used to interact with the Director, to run backup and restore jobs and to monitor your Bacula infrastructure.

To access BConsole, log on your server directly or via ssh.

This scenario uses the folder /home/bacula located on your server.
  1. To backup some files, please create a 200Mb file with random data. Type "dd if=/dev/urandom of=/home/bacula/random.log bs=100M count=2" in your terminal.
    	
    root@bacula:~]# dd if=/dev/urandom of=/home/bacula/random.log bs=100M count=2
    2+0 records in
    2+0 records out
    209715200 bytes (210 MB) copied, 19,8817 s, 10,5 MB/s
    root@bacula:~]# 
    	
    

  2. Type /opt/bacula/bin/bconsole in your terminal to enter BConsole.
    	
    [root@bee ~]# /opt/bacula/bin/bconsole
    
    Connecting to Director bee:9101
    1000 OK: 10002 bee-dir Version: 8.9.12 (11 December 2017)
    Enter a period to cancel a command.
    	
    

  3. In the console, type in run, then type enter (please type enter after each command).
    	
    *run
    	
    
  4. Select the job labeled home by typing the number in front of it.
    Example: 3: home  you hit the 3 key and validate with Enter.
    	
    Automatically selected Catalog: MyCatalog
    Using Catalog "MyCatalog"
    A job name must be specified.
    
    The defined Job resources are:
         1: BackupCatalog
         2: BackupClient1
         3: Home
         4: DatabaseServer
         5: RestoreFiles
         6: WebServer
         7: XenServer Hypervisor
    
    Select Job resource (1-7): 3
    	
    
  5. Review the job settings. Note that this job is an incremental one. You may modify parameters at run time, but in this case just type yes to start the job.

    	
    Run Backup job
    JobName:  Home
    Level:    Incremental
    Client:   bee-fd
    FileSet:  Full Set
    Pool:     File (From Job resource)
    Storage:  File1 (From Job resource)
    When:     2018-01-31 10:56:39
    Priority: 10
    
    OK to run? (yes/mod/no): yes
    	
    

  6. You should be returned to the prompt and given an indication that the job has been queued (Job queued. JobId=x).
  7. 	
    		Job queued. JobId=11
    	
    
  8. To view the status of the job, type status dir.
  9. 	
    *status dir
    bacula-dir Demo Version: 8.8.6 (18 October 2017) x86_64-redhat-linux-gnu-bacula-enterprise redhat 
    Daemon started 31-Jan-18 11:12, conf reloaded 31-Jan-2018 11:12:27
     Jobs: run=2, running=1 mode=0,2011
     Heap: heap=315,392 smbytes=394,496 max_bytes=1,409,644 bufs=498 max_bufs=505
     Res: njobs=7 nclients=3 nstores=4 npools=4 ncats=1 nfsets=10 nscheds=5
    
    Scheduled Jobs:
    Level          Type     Pri  Scheduled          Job Name           Volume
    ===================================================================================
    Incremental    Backup    10  31-Jan-18 20:00    Backup-Job         VOL002
    ====
    
    Running Jobs:
    Console connected at 31-Jan-18 11:50
     JobId  Type Level     Files     Bytes  Name              Status
    ======================================================================
        13  Back Full          0         0  home              is running
    ====
    
    Terminated Jobs:
     JobId  Level    Files      Bytes   Status   Finished        Name 
    ====================================================================
         1  Full    139,663    1.342 G  OK       19-Jan-18 09:10 bacula
         3  Full    139,663    1.342 G  OK       19-Jan-18 09:16 bacula
         5  Full    115,581    1.079 G  OK       19-Jan-18 09:20 usr
         6  Full    115,581    1.079 G  OK       19-Jan-18 09:25 usr
         7  Restore        1         0   OK       19-Jan-18 10:03 restore
         8  Incr          0         0   OK       19-Jan-18 10:29 home
         9  Incr          0         0   OK       19-Jan-18 11:22 home
        10  Incr        262    2.229 M  OK       19-Jan-18 11:23 bacula
        11  Incr          2    209.7 M  OK       31-Jan-18 11:51 home
        12  Incr          0         0   OK       31-Jan-18 11:51 home
    
    ====
    *
    	
    
  10. You might see the job listed under Running Jobs or under Terminated Jobs if it is already finished. You can also see scheduled jobs and previously completed jobs here. For example, you may find the previous job run using BWeb Management Suite.

  11. At any time, you can type messages in BConsole to review the job log.
  12. 	
    *messages
    19-Jan 11:22 bacula-dir JobId 9: Start Backup JobId 9, Job=home.2018-01-19_11.22.40_08
    19-Jan 11:22 bacula-dir JobId 9: Using Device "FILE" to write.
    19-Jan 11:22 bacula-sd JobId 9: Volume "VOL001" previously written, moving to end of data.
    19-Jan 11:22 bacula-sd JobId 9: Elapsed time=00:00:01, Transfer rate=0  Bytes/second
    19-Jan 11:22 bacula-sd JobId 9: Sending spooled attrs to the Director. Despooling 0 bytes ...
    19-Jan 11:22 bacula-dir JobId 9: Bacula Enterprise bacula-dir 8.8.6 (18Oct17):
      Build OS:               x86_64-redhat-linux-gnu-bacula-enterprise redhat 
      JobId:                  9
      Job:                    home.2018-01-19_11.22.40_08
      Backup Level:           Incremental, since=2018-01-19 10:29:09
      Client:                 "bacula" 8.8.6 (18Oct17) x86_64-redhat-linux-gnu-bacula-enterprise,redhat,
      FileSet:                "HOME" 2018-01-19 09:05:37
      Pool:                   "FILE" (From Command input)
      Catalog:                "Catalog" (From Client resource)
      Storage:                "FILE" (From Pool resource)
      Scheduled time:         19-Jan-2018 11:22:40
      Start time:             19-Jan-2018 11:22:43
      End time:               19-Jan-2018 11:22:43
      Elapsed time:           1 sec
      Priority:               10
      FD Files Written:       0
      SD Files Written:       0
      FD Bytes Written:       0 (0 B)
      SD Bytes Written:       0 (0 B)
      Rate:                   0.0 KB/s
      Software Compression:   None
      Comm Line Compression:  None
      Snapshot/VSS:           no
      Encryption:             no
      Accurate:               no
      Volume name(s):         
      Volume Session Id:      1
      Volume Session Time:    1516360680
      Last Volume Bytes:      4,937,942,805 (4.937 GB)
      Non-fatal FD errors:    0
      SD Errors:              0
      FD termination status:  OK
      SD termination status:  OK
      Termination:            Backup OK
    	
    
  13. You should now have a full backup of your /home/bacula folder. Next step is to restore this data to the default restore location, currently the folder /tmp/bacula-restores/.

Scenario 4: Running a restore of /home/bacula using BConsole

In this scenario we are restoring some data from an existing backup folder from  /home/bacula. Please follow scenario 3 first to have a complete backup of /home/bacula.
  1. To begin with, enter restore mode by typing restore in BConsole.
  2. 	
    *restore
    
    Using Catalog "Catalog"
    
    First you select one or more JobIds that contain files
    to be restored. You will be presented several methods
    of specifying the JobIds. Then you will be allowed to
    select which files from those JobIds are to be restored.
    	
    
  3. Here you will see the different ways to find what you want to restore. Type 5, which will select the last backup job run. Note that your backup client is automatically selected since there is only one client available.
  4. 	
    To select the JobIds, you have the following choices:
         1: List last 20 Jobs run
         2: List Jobs where a given File is saved
         3: Enter list of comma separated JobIds to select
         4: Enter SQL list command
         5: Select the most recent backup for a client
         6: Select backup for a client before a specified time
         7: Enter a list of files to restore
         8: Enter a list of files to restore before a specified time
         9: Find the JobIds of the most recent backup for a client
        10: Find the JobIds for a backup for a client before a specified time
        11: Enter a list of directories to restore for found JobIds
        12: Select full restore to a specified Job date
        13: Cancel
    Select item:  (1-13): 5 
    
    
  5. Here you will see all data sets that have been run. Select the fileset labeled home by typing the number before home to select the home folder.
  6. 	
    The defined FileSet resources are:
         1: BACULA
         2: CATALOG
         3: HOME
         4: USR
    Select FileSet resource (1-4): 
    
    
  7. When you hit enter, Bacula Enteprise Edition builds a file tree from the catalog, allowing you to browse and select files you want to restore.
    	
    Select FileSet resource (1-4): 3
    +-------+-------+----------+-----------+---------------------+------------+
    | JobId | Level | JobFiles | JobBytes  | StartTime           | VolumeName |
    +-------+-------+----------+-----------+---------------------+------------+
    | 13    | F     | 6        | 209798797 | 2018-01-31 11:51:55 | VOL002     |
    +-------+-------+----------+-----------+---------------------+------------+
    You have selected the following JobId: 13
    
    Building directory tree for JobId(s) 13 ...  
    5 files inserted into the tree.
    
    You are now entering file selection mode where you add (mark) and
    remove (unmark) files to be restored. No files are initially added, unless
    you used the "all" keyword on the command line.
    Enter "done" to leave this mode.
    
    cwd is: /
    $ 
    
    
  8. Many standard commands are available such as ls to list the directory, cd to change directories.
    	
    $ ls
    home/
    
    
    Let's restore now /home/bacula/.

  9. Start by typing  cd /home/bacula , then type enter. The path is case sensitive.
  10. 	
    $ cd home
    cwd is: /home/ 
    
    
  11. Type the command mark * . That will mark the contents of the directory for restore.
    	
    $ mark *
    6 files marked.
    
    

  12. When you are done selecting files and folders, type done.
  13. 	
    $ done
    
    
  14. Review the job settings, most importantly the Where and Restore Client directives. We can leave these alone for now, but if you ever want to restore to a different location or another client machine, here is one way to accomplish it.
  15. 	
    
    Bootstrap records written to /opt/bacula/working/bacula-dir.restore.2.bsr
    
    The Job will require the following (*=>InChanger):
       Volume(s)                 Storage(s)                SD Device(s)
    ===========================================================================
       
        VOL002                    FILE                      FILE                     
    
    Volumes marked with "*" are in the Autochanger.
    
    
    6 files selected to be restored.
    
    Run Restore job
    JobName:         restore
    Bootstrap:       /opt/bacula/working/bacula-dir.restore.2.bsr
    Where:           /tmp/bacula-restores
    Replace:         Always
    FileSet:         BACULA
    Backup Client:   bacula
    Restore Client:  bacula
    Storage:         FILE
    When:            2018-01-31 14:16:50
    Catalog:         Catalog
    Priority:        10
    Plugin Options:  *None*
    
    
  16. Type yes to run the restore job.
  17. 	
    OK to run? (yes/mod/no): yes
    
    
  18. To view the status of the job, type status dir.
    	
    *status dir
    bacula-dir Demo Version: 8.8.6 (18 October 2017) x86_64-redhat-linux-gnu-bacula-enterprise redhat 
    Daemon started 31-Jan-18 11:12, conf reloaded 31-Jan-2018 11:12:27
     Jobs: run=4, running=0 mode=0,2011
     Heap: heap=315,392 smbytes=341,829 max_bytes=1,453,846 bufs=481 max_bufs=509
     Res: njobs=7 nclients=3 nstores=4 npools=4 ncats=1 nfsets=10 nscheds=5
    
    Scheduled Jobs:
    Level          Type     Pri  Scheduled          Job Name           Volume
    ===================================================================================
    Incremental    Backup    10  31-Jan-18 20:00    Backup-Job         VOL002
    ====
    
    Running Jobs:
    Console connected at 31-Jan-18 11:50
    No Jobs running.
    ====
    
    Terminated Jobs:
     JobId  Level    Files      Bytes   Status   Finished        Name 
    ====================================================================
         5  Full    115,581    1.079 G  OK       19-Jan-18 09:20 usr
         6  Full    115,581    1.079 G  OK       19-Jan-18 09:25 usr
         7  Restore        1         0   OK       19-Jan-18 10:03 restore
         8  Incr          0         0   OK       19-Jan-18 10:29 home
         9  Incr          0         0   OK       19-Jan-18 11:22 home
        10  Incr        262    2.229 M  OK       19-Jan-18 11:23 bacula
        11  Incr          2    209.7 M  OK       31-Jan-18 11:51 home
        12  Incr          0         0   OK       31-Jan-18 11:51 home
        13  Full          6    209.7 M  OK       31-Jan-18 11:52 home
        14  Restore        6    209.7 M  OK       31-Jan-18 14:19 restore
    
    ====
    You have messages.
    *
    
    
  19. Type messages in BConsole to review the job log. You should type it many times to see the termination status "Restore OK".
  20. 	
    *messages
    31-Jan 14:19 bacula-dir JobId 14: Start Restore Job restore.2018-01-31_14.19.20_08
    31-Jan 14:19 bacula-dir JobId 14: Using Device "FILE" to read.
    31-Jan 14:19 bacula-sd JobId 14: Ready to read from volume "VOL002" on File device "FILE" (/storage/file).
    31-Jan 14:19 bacula-sd JobId 14: Forward spacing Volume "VOL002" to addr=209955084
    31-Jan 14:19 bacula-sd JobId 14: End of Volume "VOL002" at addr=419910551 on device "FILE" (/storage/file).
    31-Jan 14:19 bacula-sd JobId 14: Elapsed time=00:00:01, Transfer rate=209.7 M Bytes/second
    31-Jan 14:19 bacula-dir JobId 14: Bacula Enterprise bacula-dir 8.8.6 (18Oct17):
      Build OS:               x86_64-redhat-linux-gnu-bacula-enterprise redhat 
      JobId:                  14
      Job:                    restore.2018-01-31_14.19.20_08
      Restore Client:         bacula
      Start time:             31-Jan-2018 14:19:22
      End time:               31-Jan-2018 14:19:23
      Files Expected:         6
      Files Restored:         6
      Bytes Restored:         209,715,726
      Rate:                   209715.7 KB/s
      FD Errors:              0
      FD termination status:  OK
      SD termination status:  OK
      Termination:            Restore OK
    
    31-Jan 14:19 bacula-dir JobId 14: Begin pruning Jobs older than 3 months .
    31-Jan 14:19 bacula-dir JobId 14: No Jobs found to prune.
    31-Jan 14:19 bacula-dir JobId 14: Begin pruning Files.
    31-Jan 14:19 bacula-dir JobId 14: No Files found to prune.
    31-Jan 14:19 bacula-dir JobId 14: End auto prune.
    
    *
    
    
  21. Type exit to close BConsole.
    	
    *exit
    root@bacula:~]# 
    
    

Scenario 5: Backup a Windows client using Bweb Management Suite

In this scenario we will backup a Windows client using BWeb Management Suite.

At the BWeb Management Suite's main menu, click Configuration / Configure Bacula.

Click the "Add a new Client resource" in the Wizards menu on the left.

  • In step 1/5, enter the name and a description of your Windows client. Please pay attention to the naming hints in this dialog.
    Click Next.
     
  • In step 2/5, choose Windows from the "OS Type" drop-down menu. In the "Address" field, type in either the FQDN or IP address of your test Windows client. Leave the port and password alone.

    Click Next.
     
  • In step 3/5 of this wizard, simply click Next.

    Click Next.
     
  • In step 4/5 of this wizard, copy the File Daemon configuration file from the yellow box and paste into a text file called "bacula-fd.conf". This will be needed later, when installing the File Daemon on your Windows client.
    Click Next.
     
  • In step 5/5 of this wizard, click "Edit" and you will be taken to the configuration page of this new Windows client to review.
     
  • On this page, simply click "Save".


     
  • After clicking "Save", you will be at the "Clients" page showing the list of configured clients.

    Click "Workset" at the top menu.

    On this page, you will see the list of changes that have been staged, but not yet committed to your configuration.
    Click "Commit"
     
  • After commiting the changes to the workset you will be presented with a "Services restart/reload" dialog.
    In this box, check only the "Reload" checkbox for the Director, then click the "Restart/Reload" button.

    Now that the Director knows about a new Windows client, we can create the new Job Resource which will define what we are going to backup from this client. Later we will install the Bacula File Daemon on this Windows client.
     
Creating the new Job Resource for the Windows client
Back at the main menu of the Bweb Management Suite, click on Configuration / Configure Bacula.

Click "Add a new Backup" in the Wizards menu on the left.
  1. In step 1/5, give the job a name and a description, then select "DEFAULT" from the Job Template drop-down menu.
    Click Next.
     
  2. In Step 2/5, select the new Windows client from the "Client Name" drop-down menu.
    Click Next.
     
  3. In step 3/5, select "ALL_WINDOWS_DRIVES" from the "Fileset Name" drop-down menu.
    Click Next.
     
  4. In step 4/5, select "FILE" from the drop-down menus for both the "Pool Name" and the "Storage Name". Leave "Messages" as "Standard".
    Click Next.
     
  5. In step 5/5, select "Manual" from the Schedule drop-down menu since we will be starting the job manually.
    Click Next.
     
  6. After clicking Next, you will be taken to the new Job's configuration page for review. Do not change anything here.
    Note: The "Level" by default is incremental, but Bacula will automatically upgrade it to a full backup since no full backup has been made prior to this scenario. If you run this job a second time it will be an incremental job as expected.

    Click "Save" and you will be taken to the list of jobs.

    Click "Workset" at the top menu.
     
  7. On this page, you will once again see the list of changes that have been staged but not yet committed to your configuration.
    Click "Commit"
     
  8. After commiting the changes to the workset you will be presented with a "Services restart/reload" dialog. In this box, check only the "Reload" checkbox for the Director, then click the "Restart/Reload" button.
    Click on the "Bacula Enterprise Configuration" item in the top menu to exit configuration mode.
     
Installing the Bacula File Daemon on the Windows client
Pre-requisite: Any version of a Windows system (on physical hardware or a virtual machine) where you have administrator rights and a Firefox web browser installed. We will install the Bacula File deamon and disable the Windows firewall.
  1. First, log onto your test Windows system and disable the Windows firewall. You can achieve this using this simple how-to. In a production environment you might prefer to create a rule specific for Bacula.
     
  2. Deactivate the computer sleep's time. (use this FAQ "How can I prevent my computer from automatically sleeping or hibernating?")
     
  3. Please download the bacula-enterprise-demo executable file 64 bit).
     
  4. Install the software. Select the Automatic Installation.
     
  5. Leave the listed components as they are.
     
  6. The Windows File Daemon (FD) installer will ask for information about your Director




  7.  
  8. Open the text file where you saved the client configuration from step 4/5 of the wizard. At the top you will see a "Director" section. Cut-n-Paste the Name and Password from here into the "DIR Name" and "DIR Password" fields.
     
  9. For the "DIR Address", type in either the FQDN or IP address of the Director. Hint: It is currently shown in your browser's URL field.
     
  10. Click "Install"
     
  11. When prompted to "Save Client template", please be sure the check box is un-checked, then click "Next".
     
  12. Once the installation is complete, copy the "bacula-fd.conf" file that was saved in step 4/5 of the "Add a new Client resource" wizard into C:\Program Files\Bacula, overwriting the existing one.
     
  13. Open Windows "Services" and restart the Bacula service.
     
  14. The Bacula Windows File daemon is now installed and ready to be used.
     
Testing new client before running a backup job
You can now test the connectivity between the Director and this new Windows client by clicking Clients / Clients from the top menu.

From the list of clients, click the checkbox next to the new Windows client, then click the second "Status" icon on the far right.

Here you should see a page similar to the image below:

Directorsettings - BEE windows installation


If you receive an error here, please check the following parameters:
  • IP addresses or fully qualified domain names in both the client definition in BWeb Management Suite and on the Windows client in C:\Program Files\Bacula\bacula-fd.conf
  • Check that the passwords, name of the director (with -dir) or file daemon (with -fd) in the new Windows "bacua-fd.conf" file match what is in the Director's configuration for this Client
  • Check that your Workset is applied and reload the Director
  • Finally, on the new Windows client, check that the firewall is disabled

  • You may also contact Bacula's support team if you cannot figure out the cause of the connectivity problem. Please See instructions at the end of this document.

    If the previous Status command runs as expected, we can now run our new backup job:

    Click on Jobs in the top menu, then Defined Jobs in the drop down menu.

    In Step 1, Select the "Windows_Test" job from the Job Name drop-down menu.

    Directorsettings - BEE windows installation
    Once you select the new "Windows_Test" job, you will be taken to Step 2, where you can review the properties of the job that is about to be run. Do not make any changes here, just click "Run Job".

    Directorsettings - BEE windows installation
    Once you click "Run Job", you will be redirected to a job status page where you can see the job running. The backup may take some time because there are several gigabytes of data to be backed up. This page will be automatically updated every 30 seconds, but you may click on the Refresh button (two green arrows) to get an immediate updated view.

    Once the job is finished you should have a job summary page similar to the image below. Notice the green check mark at the top under the "Status" column indicating that this job has completed normally.

    In the yellow box is the job's log, including a partial listing of the job's summary at the bottom.

    Directorsettings - BEE windows installation

Scenario 6: Backup a Windows client with the Global End Point Deduplication plugin

In this scenario we will backup a Windows client from BWeb Management Suite using the Global End Point Deduplication plugin. We will choose to deduplicate data on both the client and the storage side.
Pre-requisite: any version of a Windows system (on a physical hardware or a virtual machine) with the Bacula Enterprise Edition File Daemon
installed through the scenario 5 above. You must use the Trial Kickstart to use this scenario as some folders used by the Global End Point Deduplication were created on it.

This scenario uses the folder C:\toBackup\ on your Window system to backup files.
  1. To backup some files, please create a 200Mb file with random data in C:\toBackup\ on your Windows system. Please use any available technology or software to generate this file, for example RDFC.

  2. To be able to use the Global EndPoint Deduplication, we will create new resources for a new job, a new fileset and a new storage with BWeb Management Suite.

  3. Please go on your BWeb Management Suite and go to Configuration (top right) / Configure Bacula. Click on the Storage Deamons icon in the Bacula Enterprise Components frame, then choose Devices tab.

  4. Click on the device named "DDEV001" then click on the Copy button on the top right of the resource window. Rename it GED_Device then press OK. Fill in all the information as shown in the screen below.
  5. Create a GED device

  6. Click on the Save button.

  7. You should then create a Storage resource in the Director that points to this new device called "GED_Device". Click on Workset in the tab menu then click on the Storages/Autochangers tab.

  8. Select an already made Storage (for example DEFAULT), click on it, then copy it by clicking on the Copy button on the top right of the resource window. Rename it GED_Storage then press OK. Fill in all the information as in the screen below.
    Create a storage resource for the GED.

  9. Click on the Save button.

  10. You should then create a FileSet resource in the Director that specifies what to backup and how. It is here that we will set the Global End Point Deduplication parameters. Click on FileSet in the tab menu.

  11. Click on the "+" button top left to open a new window to create a new FileSet resource.  First type a name for your FileSet then click on "Add Include List" to include C:/toBackup.
    Create the FileSet for GED

  12. In the next screen named Configure FileSet, choose the Client to browse (use the one installed in scenario 5 above) then select the directory to backup and click on Add Selection. When all the directories are selected, click Next.
    FileSet edition:
directories to backup


  13. In the screen Options, choose the Dedup type Storage, as in the screen below. Finally click on the button Apply, then on the button Add to save your FileSet.
    FileSet option for GED

  14. You should now create a Pool resource in the Director that specifies the backup policy. Click on Pools in the tab menu.

  15. Click on the "+" button top left to open a new window to create a new Pool resource.  First type a name for your Pool, specify the label format and the storage to use, as illustrated in the printscreen below and click on Add to create it.
    Creat Pool GED

  16. Finally, we are able to create a Job that will use all the resources created previously. Click on Jobs in the tab menu.

  17. Click on the "+" button top left to open a new window to create a new Job resource. Please follow the printscreen below to fill in all fields. Finally, click the Add button.
    Creat Job for GED

  18. All that is needed to run a backup job is now done. Click on Workset in the tab menu, then commit the workset by clicking on Commit. Choose to restart the Director and the Storage.
    If you don't see this choice on your screen, please go to Directors and click on Restart Director. Once the Director restarted, please go to Storage Deamons and click on Restart Local Storage Daemon.

  19. It is now possible to run the job. Before running the job, please add a big file with random data as explained in our introduction to this scenario. For this example, a 50MB file was created in C:\toBackup\ .
    Now you have created your file, click on the Bacula Enterprise at the top left of the screen. Click on the menu Jobs, then Defined Jobs in the drop down menu.

  20. Select the job you have just created in the Job Name drop list and click on Run Now, a summary form appears.

  21. Please check you have the following settings for your Job (except client name and Level). Finally click on Run now on this summary page.
    GED - Run Job


  22. You'll be redirected to a job status page where you can see the job running (this might take some time depending on how much data you backup). You can click on the Refresh button any time to see the progress.

  23. Once the job is done you should have a display like this (please check the total size of the backup, highlighted below):
    	
    2018-02-02 18:11:16 bacula-dir-dir JobId 8: No prior Full backup Job record found.
    2018-02-02 18:11:16 bacula-dir-dir JobId 8: No prior or suitable Full backup found in catalog. Doing FULL backup.
    2018-02-02 18:11:18 bacula-dir-dir JobId 8: Start Backup JobId 8, Job=GED_Job.2018-02-02_18.11.16_31
    2018-02-02 18:11:19 bacula-dir-dir JobId 8: Created new Volume="GED_Pool_0004", Pool="GED_Pool", MediaType="GED_data" in catalog.
    2018-02-02 18:11:19 bacula-dir-dir JobId 8: Using Device "GED_Device" to write.
    2018-02-02 18:11:19 bacula-dir-sd JobId 8: No slot defined in catalog (slot=0) for Volume "GED_Pool_0004" on "GED_Device" (/storage/dedupe).
    2018-02-02 18:11:19 bacula-dir-sd JobId 8: Cartridge change or "update slots" may be required.
    2018-02-02 18:11:19 bacula-dir-sd JobId 8: Labeled new Volume "GED_Pool_0004" on Dedup device "GED_Device" (/storage/dedupe).
    2018-02-02 18:11:19 bacula-dir-sd JobId 8: Wrote label to prelabeled Volume "GED_Pool_0004" on Dedup device "GED_Device" (/storage/dedupe)
    2018-02-02 18:11:20 kickstart-win-fd JobId 8: Generate VSS snapshots. Driver="Win64 VSS"
    2018-02-02 18:11:20 kickstart-win-fd JobId 8:     Snapshot mount point: C:\
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "MSSearch Service Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:28 kickstart-win-fd JobId 8: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:11:33 bacula-dir-sd JobId 8: Elapsed time=00:00:14, Transfer rate=7.506 M Bytes/second
    2018-02-02 18:11:33 bacula-dir-sd JobId 8: Sending spooled attrs to the Director. Despooling 4,197 bytes ...
    2018-02-02 18:11:34 bacula-dir-dir JobId 8: Bacula Enterprise bacula-dir-dir 8.8.6 (18Oct17):
      Build OS:               x86_64-redhat-linux-gnu-bacula-enterprise redhat 
      JobId:                  8
      Job:                    GED_Job.2018-02-02_18.11.16_31
      Backup Level:           Full (upgraded from Incremental)
      Client:                 "kickstart-win-fd" 8.8.6 (18Oct17) Microsoft Windows 7 Professional Service Pack 1 (build 7601), 64-bit,Cross-compile,Win64
      FileSet:                "GED_FileSet" 2018-02-02 17:58:13
      Pool:                   "GED_Pool" (From Command input)
      Catalog:                "Catalog" (From Client resource)
      Storage:                "GED_Storage" (From Pool resource)
      Scheduled time:         02-Feb-2018 18:11:16
      Start time:             02-Feb-2018 18:11:19
      End time:               02-Feb-2018 18:11:34
      Elapsed time:           15 secs
      Priority:               10
      FD Files Written:       18
      SD Files Written:       18
      FD Bytes Written:       209,810,262 (209.8 MB) <----
      SD Bytes Written:       105,096,585 (105.0 MB)
      Rate:                   13987.4 KB/s
      Software Compression:   49.9% 2.0:1
      Comm Line Compression:  5.4% 1.1:1
      Snapshot/VSS:           yes
      Encryption:             no
      Accurate:               no
      Volume name(s):         GED_Pool_0004
      Volume Session Id:      1
      Volume Session Time:    1517591469
      Last Volume Bytes:      186,576 (186.5 KB)
      Non-fatal FD errors:    0
      SD Errors:              0
      FD termination status:  OK
      SD termination status:  OK
      Termination:            Backup OK
    
    2018-02-02 18:11:34 bacula-dir-dir JobId 8: Begin pruning Jobs older than 6 months .
    2018-02-02 18:11:34 bacula-dir-dir JobId 8: No Jobs found to prune.
    2018-02-02 18:11:34 bacula-dir-dir JobId 8: Begin pruning Files.
    2018-02-02 18:11:34 bacula-dir-dir JobId 8: No Files found to prune.
    2018-02-02 18:11:34 bacula-dir-dir JobId 8: End auto prune.
    	
    
  24. You can now test the Deduplication feature by copying the original large file on your client into the same directory you backed up. You will have then two identical large files. Then re-run the backup job as done previously from 18. above. The job log output will show only a few additional kB of backed up data because the file is deduplicated and not stored again with only pointers to the original file stored:
    	
    2018-02-02 18:12:58 bacula-dir-dir JobId 9: Start Backup JobId 9, Job=GED_Job.2018-02-02_18.12.56_42
    2018-02-02 18:12:58 bacula-dir-dir JobId 9: Using Device "GED_Device" to write.
    2018-02-02 18:12:58 bacula-dir-sd JobId 9: No slot defined in catalog (slot=0) for Volume "GED_Pool_0004" on "GED_Device" (/storage/dedupe).
    2018-02-02 18:12:58 bacula-dir-sd JobId 9: Cartridge change or "update slots" may be required.
    2018-02-02 18:12:59 bacula-dir-sd JobId 9: Volume "GED_Pool_0004" previously written, moving to end of data.
    2018-02-02 18:13:00 kickstart-win-fd JobId 9: Generate VSS snapshots. Driver="Win64 VSS"
    2018-02-02 18:13:00 kickstart-win-fd JobId 9:     Snapshot mount point: C:\
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "MSSearch Service Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:08 kickstart-win-fd JobId 9: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE)
    2018-02-02 18:13:09 bacula-dir-sd JobId 9: Elapsed time=00:00:10, Transfer rate=18.26 K Bytes/second
    2018-02-02 18:13:10 bacula-dir-sd JobId 9: Sending spooled attrs to the Director. Despooling 4,422 bytes ...
    2018-02-02 18:13:10 bacula-dir-dir JobId 9: Bacula Enterprise bacula-dir-dir 8.8.6 (18Oct17):
      Build OS:               x86_64-redhat-linux-gnu-bacula-enterprise redhat 
      JobId:                  9
      Job:                    GED_Job.2018-02-02_18.12.56_42
      Backup Level:           Full
      Client:                 "kickstart-win-fd" 8.8.6 (18Oct17) Microsoft Windows 7 Professional Service Pack 1 (build 7601), 64-bit,Cross-compile,Win64
      FileSet:                "GED_FileSet" 2018-02-02 17:58:13
      Pool:                   "GED_Pool" (From Command input)
      Catalog:                "Catalog" (From Client resource)
      Storage:                "GED_Storage" (From Pool resource)
      Scheduled time:         02-Feb-2018 18:12:56
      Start time:             02-Feb-2018 18:12:58
      End time:               02-Feb-2018 18:13:10
      Elapsed time:           12 secs
      Priority:               10
      FD Files Written:       19
      SD Files Written:       19
      FD Bytes Written:       262,239,274 (262.2 MB) <----
      SD Bytes Written:       182,613 (182.6 KB)
      Rate:                   21853.3 KB/s
      Software Compression:   99.9% 1436.0:1
      Comm Line Compression:  5.4% 1.1:1
      Snapshot/VSS:           yes
      Encryption:             no
      Accurate:               no
      Volume name(s):         GED_Pool_0004
      Volume Session Id:      2
      Volume Session Time:    1517591469
      Last Volume Bytes:      418,121 (418.1 KB)
      Non-fatal FD errors:    0
      SD Errors:              0
      FD termination status:  OK
      SD termination status:  OK
      Termination:            Backup OK
    
    2018-02-02 18:13:10 bacula-dir-dir JobId 9: Begin pruning Jobs older than 6 months .
    2018-02-02 18:13:10 bacula-dir-dir JobId 9: No Jobs found to prune.
    2018-02-02 18:13:10 bacula-dir-dir JobId 9: Begin pruning Files.
    2018-02-02 18:13:10 bacula-dir-dir JobId 9: No Files found to prune.
    2018-02-02 18:13:10 bacula-dir-dir JobId 9: End auto prune.
    	
    
  25. On the restore side, if you click from the main menu on Jobs, Web Restore then select the client name and the latest job you just ran above, you will see all the copied file that can be restored.Restore GED

If you want to go further with this plugin, please refer to the Global EndPoint Deduplication plugin White Paper in your "whitepapers" folder in your personal Download Area.

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 Cloud plugin. We will use Amazon’s Simple Storage Service (Amazon S3) object storage architecture to store the cloud volumes.

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 previously installed with the KickStart will be used. You must use the Trial Kickstart to follow this scenario as some folders used by the Cloud plugin have already been created on it.

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 have a restricted user with credentials to be used with the Kickstart only for the backup purposes.

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

Please find the AWS Best Practices guide here: http://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html .

The Cloud plugin provides the AWS Command Line Interface (CLI) that will be used to perform the procedures explained below. The commands are available in a Linux shell. Please find more details about the AWS Command Line Interface (CLI) here: https://aws.amazon.com/documentation/cli/

The procedure below demonstrates how to have an IAM restricted user created with its own credentials with an attached policy to access a specific bucket for use with the Kickstart trial. Please note you will need to create the bucket prior to following this procedure by using the AWS root credentials or any other IAM user with the necessary permissions.


  1. Create IAM restricted user:

    			
    
    # aws iam create-user --region=us-east-1 --endpoint-url https://iam.amazonaws.com --user-name backup_user
    
    {
    
    "User": {
    
    	"UserName": "backup_user",
    
    	"Path": "/",
    
    	"CreateDate": "2017-04-02T14:22:46.017Z",
    
    	"UserId": "user-id-value",
    
    	"Arn": "arn:aws:iam::account-id:user/backup_user"
    
    	}
    
    }
    
    
    
    

  2. Create a new AWS secret access key and corresponding AWS access key ID for the specified user:
    			
    
    Note: The default status for a new key is “Active”.
    
    
    
    # aws iam create-access-key --region=us-east-1 --endpoint-url https://iam.amazonaws.com --user-name backup_user
    
    {
    
    	"AccessKey": {
    
    		"UserName": "backup_user",
    
    		"Status": "Active",
    
    		"CreateDate": "2017-04-02T14:28:06.436Z",
    
    		"SecretAccessKey": "secret-access-key-value",
    
    		"AccessKeyId": "access-key-id-value"
    
    	}
    
    }
    
          		
    
    

  3. Create a policy using a json policy document:
    			
    
    # cat backup_user-policy
    
    {
    
    	"Version": "2012-10-17",
    
    	"Statement": [{
    
    		"Effect": "Allow",
    
    		"Action": "s3:ListAllMyBuckets",
    
    		"Resource": "arn:aws:s3:::*"
    
    	},{
    
    		"Effect": "Allow",
    
    		"Action": [
    
    			"s3:ListBucket",
    
    			"s3:GetBucketLocation"
    
    		],
    
    		"Resource": "arn:aws:s3:::baculavolumes-us"
    
    	},{
    
    		"Effect": "Allow",
    
    		"Action": [
    
    			"s3:PutObject",
    
    			"s3:GetObject",
    
    			"s3:DeleteObject"
    
    		],
    
    		"Resource": "arn:aws:s3:::baculavolumes-us/*"
    
    	}]
    
    }
    
    		
    
    
    			
    
    
    
    # aws iam create-policy --region=us-east-1 --endpoint-url https://iam.amazonaws.com –policy-name backup_user-policy --policy-document file://backup_user-policy
    
    {
    
    	"Policy": {
    
    		"PolicyName": "backup_user-policy",
    
    	}
    
    }
    
    	"CreateDate": "2017-04-02T22:24:10.423Z",
    
    	"AttachmentCount": 0,
    
    	"IsAttachable": true,
    
    	"PolicyId": "policy-id-value",
    
    	"DefaultVersionId": "v1",
    
    	"Path": "/",
    
    	"Arn": "arn:aws:iam::account-id:policy/backup_user-policy",
    
    	"UpdateDate": "2017-04-02T22:24:10.423Z"
    
    			
    
    
  4. Assign the policy to the IAM user:

    			
    
    # aws iam attach-user-policy --region=us-east-1 --endpoint-url https://iam.amazonaws.com –user-name backup_user --policy-arn arn:aws:iam::account-id:policy/backup_user-policy
    
    		
    
    
  5. Create a us-east-1 region (US Standard) bucket:
    			
    
    # aws s3 mb --region=us-east-1 --endpoint-url https://iam.amazonaws.com s3://us-1-volumes
    
    		
    
    
  6. Test listing bucket content using backup_user's credentials:
    			
    
    # aws s3 ls --recursive --region us-east-1 --endpoint-url https://s3.amazonaws.com s3://us-1-volumes
    
    	
    
    

  7. Now we are ready to create the new Bacula resources needed for backups using a S3 compatible object storage solution.

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


  8. In BWeb Management Suite, click Configuration --> Configure Bacula.


  9. Click on the Storage Daemons icon in the Bacula Enterprise Components box, then choose the Clouds tab in the top menu to create a Cloud resource.


  10. Click the green "plus sign" icon to add a new Cloud resource and fill in all the information as shown in the image below. Please note that the Region field at the bottom may also need to be modified to match your environment.




  11. Click on the Add button.


  12. Once the Cloud resource has been created, click the Devices menu item to create a new Device resource. Click the green "plus sign" to add a new Device resource and fill in all the information as shown in the image below.



  13. Note: The Archive Device field is important in this page. The directory specified must exist, and there must be enough free space to store Cloud volumes in the "local cache". Depending on the choices made during the installation of the Kickstart Trial, there may be more free space in another directory. This default location is OK to run some small test backups.

  14. Click on the Add button.


  15. Next, we need to create a Storage resource in the Director that points to this new device called "Cloud-Drive-Bucket-us-1-volumes".


  16. Click on the Storages/Autochangers tab in the main menu.


  17. Select an already made Storage (for example DEFAULT), then copy it by clicking on the Copy button on the top right of the resource window. Rename it to "Cloud-Storage" then press OK. Fill in all the information as in the image below.


  18. Note: The Address will most likely be different here, or it may even point to a FQDN depending on your network environment. Whatever is pre-filled in for the Address should be correct, and should be left as-is.

  19. Click on the Save button. Now all the changes we have made are in the Workset, but they have not been committed to the production configuration, as shown in the image below.

  20. Click "Workset" in the top menu to see the current uncommitted changes.


  21. Click "Commit" to commit the change to the production configuration.

  22. Once the Workset is committed, the Director must be reloaded, and the Storage daemon must be restarted in order to use this new Cloud configuration.



  23. You can check the status of the new Storage created. To do this, we first need to leave configuration mode by clicking on the Bacula Enterprise title on the top menu.


  24. Next, select Storages --> then Manage Device. A list of Storage devices appears. Select the new “Cloud-Storage” device from the list, then click on the Status button. You should have an output like:



  25. You can also check the connection status between the new Storage created and a Client previously created.
    To do this, select Storages from the main menu, then Storage Overview. Choose the new Cloud 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 new “Cloud-Storage” device in the Storage list. Then click on the Run Test button.

    You should have an output like:




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

    You can use Scenario 1: “Backing up files from /usr folder via Bweb Management Suite” to run backup tests for a Linux host, and you can use Scenario 5: “Backup a Windows client with Bweb Management Suite” to run backup tests for a Windows host.

    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.

    In all cases, please note you will need to select the “Cloud-Storage” storage in order for your backup/restore job to use the Cloud device created in this scenario.




Congratulations! We hope that you enjoyed using Bacula Trial Edition. You have the opportunity to further test your Bacula Trial Edition installation. Please refer to our main manual, in particular the chapters "A Brief Tutorial" and "Getting Started with Bacula".

If you have any comment/suggestion please fill out the feedback form and let us know. We'll get back to you in a timely fashion.

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

If you are not able to complete these scenarios, or have an issue regarding any products, please contact the sales team via our contact form.

With our best regards,
The Bacula Systems Support Team


Additional notes: The Trial Kickstart is not usable one month after the first run job.

The appliance will stop working after 30 days. Please contact us if you need more time.

Appendix

Installation of a File Daemon (a backup agent) on Debian or Ubuntu

  1. Log in into your system where you want to install a backup agent, called a File Daemon within Bacula Enterprise Edition.

  2. Run the following command as root:

    1. apt-get update
    2. apt-get install apt-transport-https

  3. Install the package signature with the following commands:

    1. cd /tmp
    2. wget https://www.baculasystems.com/dl/KickStart/BaculaSystems-Public-Signature.asc
    3. apt-key add BaculaSystems-Public-Signature.asc
    4. rm BaculaSystems-Public-Signature.asc

  4. Edit the file /etc/apt/sources.list with your favorite editor and add the following lines adapted to your platform (needs to be changed twice in the line - wheezy-64 if you run Debian Wheezy 64 bit, trusty-64 if you run Ubuntu Trusty 64 bit, etc...):

    For Debian platforms
    #Trial Bacula Enterprise
    deb https://www.baculasystems.com/dl/KickStart/wheezy-64/ wheezy demo

    For Ubuntu platforms
    #Trial Bacula Enterprise
    deb [arch=amd64] https://www.baculasystems.com/dl/KickStart/trusty-64/ trusty demo
    [arch=amd64] is mandatory only for 64 bit Ubuntu platforms.

  5. To install the client, type the following command:
    1. apt-get update
    2. apt-get install bacula-enterprise-demo-client

  6. Please setup your local firewall to accept a Bacula Enterprise Edition connection, or disable it completely:

    1. /etc/init.d/iptables stop
    2. chkconfig iptables off

  7. If successfully installed, continue by adding a client as explained in the next chapter named "Creation of a new Client Resource in BWeb Management Suite".

Installation of a File Daemon (a backup agent) on CentOS or Red Hat

  1. Log in into your system where you want to install a backup agent, called a File Daemon within Bacula Enterprise Edition.

  2. Run the following command as root or via sudo (please adapt the URL to your RHEL/CentOS platform, where all CentOS must be replaced by RHEL):

    1. URL=https://www.baculasystems.com/dl/KickStart/rhel6-64/
    2. rpm -ivh $URL/bacula-enterprise-setup.rpm

  3. To install the client, type the following command:

    1. yum install bacula-enterprise-demo-client

  4. Please setup your local firewall and SELinux to accept a Bacula Enterprise Edition connection, or disable it completely:

    1. /etc/init.d/iptables stop
    2. chkconfig iptables off
    3. edit /etc/selinux/config and change SELINUX=enforcing to SELINUX=permissive

  5. If successfully installed, continue by adding a client as explained in the next chapter named "Creation of a new Client Resource in BWeb Management Suite".

Creation of a new Client Resource in BWeb Management Suite

  1. Use BWeb Management Suite to configure a client and generate the agent configuration file to paste in /opt/bacula/etc/bacula-fd.conf on the client side. To do so, go to your BWeb Management Suite, click on Configuration in your main menu, Configure Bacula. Click on the Wizard named Add a new client resource.

  2. Type the name of your agent in the field Client Name and click Next.

  3. Fill in the OS Type and the Address field. You may also change the Password field if you wish. Click Next.
    Configure Client


  4. Replace all the content of the file /opt/bacula/etc/bacula-fd.conf on your client with the whole text displayed in the page named Configure new Client resource 3/4. Once done, click Next. You can configure a new backup job from the next screen. Please feel free to benefit from the previous scenarios to add a new job for this client.
    FD configuration to copy to the FD

  5. In the main menu, click on Workset. Click on Commit then reload the Director as proposed.
    Commit Workset

  6. Restart the File Daemon (FD) on the client side by running in a shell: /etc/init.d/bacula-fd restart .

  7. Check if the Director can contact the File Daemon. From BWeb Management Suite, click on the Bacula Enterprise in the top left corner. Click on Clients on the main menu, again on Clients in the menu. Select the listed client you want to test and click on the Status button. The result should be similar to the screen below.
    Check Status client

  8. Now you can configure a new job following any scenario and run a backup on this client.

Supported Platforms for the Trial Agent version

Listed below are the supported platforms to install the Trial File Daemon on your servers. Please just replace the related string in the procedure to install a File Daemon above.

Code
Corresponding Operating System
rhel6-64 Redhat Enterprise Linux 6.x 64 bit / CentOS 6.x 64 bit
rhel7-64 Redhat Enterprise Linux 7.x 64 bit / CentOS 7.x 64 bit
jessie-64 Debian Jessie 8 64 bit
trusty-64 Ubuntu Trusty 14.04 LTS 64 bit
win64 Microsoft Windows 64 bit

Important: Bacula Enterprise Edition offers many more platforms for production. Please contact us for more information.