The installer files can be downloaded from the Client > Software tab.


File versions may be slightly different, swap in the correct version numbers for the file you downloaded. Replace the XXXX and YYYY placeholder with the correct information from the file name for your operating system.

In a root shell execute the following commands one at a time:

cd /tmp
tar -xzf /path/to/rvx-backup-client-X.X.X.X.XXXX.YYYY.tar.gz
cd rvx-backup-client-X.X.X.X.XXXX.YYYY
bash ./

You may now download the client’s configuration file from the Clients > Summary tab. Right click on anywhere on the row for your client and choose the option to Download Config. For clients running Linux, Solaris, and FreeBSD, save the downloaded bacula-fd.conf configuration file to the one of the following directories:

  • 4.0.X.X: /usr/rvx/etc
  • 5.X.X.X: /opt/eversync/etc/


There’s a known bug in 5.3 versions in which the configuration file will attempt to use the 4.0 working directory. You can comment out the /usr/rvx/etc directory in the configuration file with ## at the beginning of the directory.

After saving the client configuration file, you can start the backup client manually by issuing the following command as the root user:

/etc/init.d/rvx-backup start

The backup Client may be stopped at any time by issuing this command as the root user:

/etc/init.d/rvx-backup stop

Possibly also handy:

/etc/init.d/rvx-backup restart

The installer also creates a script, which will start the backup Client each time your system boots up.


If the client is using a firewall, make sure that the bacula-fd.conf service is allowed to pass through. File systems mounted as type MSDOS may have problems with filenames that aren’t 8.3 compliant. They will either be truncated or cause an error. Possible work around is to mount with vfat and no check option.

Typing df -l will show locally mounted filesystems which are good candidates for the Linux client’s File Set. Keep this output handy when configuring the Client on the CFA.