This page is for information purposes only. We are reworking completely the functionality of Linux DR image backup at the moment. For now, we do not recommend configuring and making Linux DR image backups using the backup agent.
The installer files can be downloaded from the appliance Management Console › Settings › Tools › Downloads.
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:
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 ./install.sh
You may now download the client configuration file from Clients › Summary. Right-click the desired client to show the context menu, and then click Download Config. For clients running Linux, Solaris, and FreeBSD, save the downloaded bacula-fd.conf configuration file to the one of the following directories:
-
for backup agent 4.x and earlier:
/usr/rvx/etc -
for the backup agent 5.x and later:
/opt/eversync/etc/
There is a known bug in 5.3 version, in which the configuration file will attempt to use the 4.0 working directory. You can comment out the
/usr/rvx/etcdirectory 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 running the following command as the root user:
/etc/init.d/rvx-backup start
You can stop the backup agent at any time by running the following 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 agent each time your system starts.
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 MS-DOS may have problems with file names that are not 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 file systems, which are good candidates for the Linux client file set. Keep this output handy when configuring the client on appliance.