The following instructions can be used to help you install the Backup Agent for Linux, Solaris, and FreeBSD systems.

The installer files can be downloaded from the Client > Software tab. Once the appropriate rvx-backup-client installer file has been downloaded to your Client, the software can be installed as follows.

Note: 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 / /rvx-backup-client-3.0.0.1.XXXX.YYYY.tar.gz </span> </li>
  • cd rvx-backup-client-3.0.0.1.XXXX.YYYY
  • bash ./install.sh
  • </ul>

    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/

    </div>

    (Note, there is 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.

    Notes: 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 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 filesystems which are good candidates for the Linux client's File Set. Keep this output handy when configuring the Client on the CFA.

    *[AES]: Advanced Encryption Standard *[AESs]: Advanced Encryption Standards *[API]: application programming interface *[APIs]: application programming interfaces *[BMR]: BareMetal Restore *[BMRs]: BareMetal Restores *[CAB]: Cloud Application Backup *[CABs]: Cloud Application Backups *[CB]: Cloud Backup *[CBs]: Cloud Backups *[CBT]: Changed Block Tracking *[CBTs]: Changed Block Trackings *[CFA]: cloud failover appliance *[CFAs]: cloud failover appliances *[CIFS]: Common Internet File System *[CIFSs]: Common Internet File Systems *[DC]: data center *[DCs]: data centers *[DDFS]: deduplication file system *[DDFSs]: deduplication file systems *[DPS]: Data Protection Server *[DPSs]: Data Protection Servers *[DR]: disaster recovery *[DRs]: disaster recoverys *[DRaaS]: Disaster Recovery as a Service *[DRaaSs]: Disaster Recovery as a Services *[GCP]: Google Cloud Platform *[GCPs]: Google Cloud Platforms *[ICAB]: Infrascale Cloud Application Backup *[ICABs]: Infrascale Cloud Application Backups *[ICB]: Infrascale Cloud Backup *[ICBs]: Infrascale Cloud Backups *[ICMP]: Internet Control Message Protocol *[ICMPs]: Internet Control Message Protocols *[IDR]: Infrascale Disaster Recovery *[IDRs]: Infrascale Disaster Recoverys *[IPMI]: Intelligent Platform Management Interface *[IPMIs]: Intelligent Platform Management Interfaces *[JVM]: Java virtual machine *[JVMs]: Java virtual machines *[LVM]: logical volume management *[LVMs]: logical volume managements *[MFA]: multi-factor authentication *[MFAs]: multi-factor authentications *[MSP]: managed services provider *[MSPs]: managed services providers *[N/A]: Not applicable *[N/As]: Not applicables *[NAS]: network-attached storage *[NASs]: network-attached storages *[NAT]: network address translation *[NATs]: network address translations *[NFS]: Network File System *[NFSs]: Network File Systems *[NIC]: network interface controller *[NICs]: network interface controllers *[NTP]: Network Time Protocol *[NTPs]: Network Time Protocols *[NTPD]: Network Time Protocol Daemon *[NTPDs]: Network Time Protocol Daemons *[OBRM]: Online Backup and Recovery Manager *[OBRMs]: Online Backup and Recovery Managers *[PBKDF2]: Password-Based Key Derivation Function 2 *[PBKDF2s]: Password-Based Key Derivation Function 2s *[POSIX]: Portable Operating System Interface for Unix *[POSIXs]: Portable Operating System Interface for Unixs *[RAID]: Redundant Array of Independent Disks *[RAIDs]: Redundant Array of Independent Diskss *[RCT]: resilient change tracking *[RCTs]: resilient change trackings *[ROM]: read-only memory *[ROMs]: read-only memorys *[SDK]: software development kit *[SDKs]: software development kits *[SMB]: Server Message Block *[SMBs]: Server Message Blocks *[SMTP]: Simple Mail Transfer Protocol *[SMTPs]: Simple Mail Transfer Protocols *[SNMP]: Simple Network Management Protocol *[SNMPs]: Simple Network Management Protocols *[UCAR]: unique content addressable repository *[UCARs]: unique content addressable repositorys *[UEFI]: Unified Extensible Firmware Interface *[UEFIs]: Unified Extensible Firmware Interfaces *[UNC]: Universal Naming Convention *[UNCs]: Universal Naming Conventions *[vCFA]: virtual cloud failover appliance *[vCFAs]: virtual cloud failover appliances *[VM]: virtual machine *[VMs]: virtual machines *[VNC]: Virtual Network Computing *[VNCs]: Virtual Network Computings *[vNIC]: virtual network interface controller *[vNICs]: virtual network interface controllers *[VPN]: virtual private network *[VPNs]: virtual private networks *[VSS]: Volume Shadow Copy Service *[VSSs]: Volume Shadow Copy Services