Virtual Server: How to install and configure backups (Bacula Enterprise) on a Windows Server


The Bacula backup service is the optional daily backup service listed in the ITS VMware Hosted Solutions page. Backups are FILE LEVEL only.

If you are a VM customer and have purchased this service, a client will need to be configured on your server to communicate with the backup server. This article describes installing and configuring the Bacula client on a Windows Server VM.


You should already have this service purchased through ITS Managed Services. A staff member will provide information to the private network for the backups:

Private network IP address
Private network gateway address

Private network subnet mask

An additional network interface (NIC) for the private network will also be added on the VM and an installation file for the Bacula Enterprise client will be sent to you (via UH Filedrop).

PLEASE NOTE: Some virtual servers were not configured to have two networks. If your server has only one network, please follow these instructions.


Part I: Configuring the private network and adding static routes

Part II: Configuring the backup client

Part I: Configuring the private network and adding static routes

  1. Confirm that you have a secondary network interface added on your VM. This can be viewed in the Network Connections window, or by going to Start > Control Panel > Network and Sharing Center > Change adapter settings.

    To easily differentiate between the two interfaces, you can rename your primary interface to something like "Public" and "Backup-private" for the secondary interface. The public network interface has the public facing IP configured for the VM.
  2. Right-click on the secondary (private) interface and go to Properties. Uncheck "Internet Protocal Version 6 (TCP/IPv6)" and select "Internet Protocol Version 4 (TCP/IPv4)" and click Properties.

  3. Select "Use the following IP address" in the window that opens and fill out the network information.

    Below is an example of what the configuration will look like. The IP address in the screenshot is just an example; your actual private IP address will be provided by staff.

    IP address: provided by ITS staff
    Subnet mask: provided by ITS staff
    Default gateway: left BLANK

    Preferred DNS server:
    Alternate DNS server:

    Click OK to confirm the settings and save.
  4.  Next, static routes will need to be configured on the private network interface. Open the Command Prompt and run as an admistrator and enter

    netstat -r

    to display the routing table (the window will need to be expanded to show the entire output).

    Take note of the Interface List in the output as you will need to note down the interface number. In this example, the interface number of the secondard private interface is "16" (outlined in red below). You should also double-check the MAC address to make sure it is correct.

  5. Run the following commands in the terminal to add the static routes. You will need to know your private gateway IP address as provided by Managed Services staff.

    route add mask <gateway IP> -p IF <interface number>
    route add mask <gateway IP> -p IF <interface number>
    route add mask <gateway IP> -p IF <interface number>

    The screenshot example shows adding the three static routes to the private gateway IP address to the secondary network interface, which Windows defined as 16.

  6. Enter netstat -r again in the command prompt to confirm the addition of the static routes.

  7. To test that the routes are properly configured, run the nslookup command on these two hosts to verify it resolves to those IPs. This ensures that the server is able to see the two Bacula backup servers.

    NOTE: On Windows Server 2016, the nslookup command may not properly resolve the Bacula hosts unless you specify the private DNS server, i.e.


  8. Update the Windows Firewall to allow incoming traffic on ports 9102 and 9103 from ( and (

Single-Network Servers

Your virtual server may not have been configured with two networks. If you have a single public network assigned on your server, you do not need to setup static routing.

Please be sure to change the DNS addresses on the public network interface to the following:

Then, run nslookup to verify that the Bacula server host can be resolved. After that, you may follow the instructions to install the Bacula client.


Part II: Configuring the backup client

  1.  Install the Bacula Enterprise 8.6.16 client (bacula-enterprise-win64-8.6.16.exe) by right-clicking the file and selecting “Run as Administrator”.

    Click Next at the below dialog box.

    If you agree to the license agreement, click I Agree at the below dialog box.

    Choose Automatic at the below dialog box and then click Next.