Downloads

Overview

The Downloads section contains links to download client software to the client computer.

Note

You may need to copy the software to the client by other means, such as SCP, FTP, or command line web tools.

Installing client software and configuration files

Linux, Solaris, FreeBSD

Open the shell.
Enter the following commands:
```
root\# cd /tmp
root\# tar xf filepath
root\# cd filename
root\# bash ./install.sh
```
where filepath is the full path to the downloaded installation archive, and filename is the name of the downloaded installation archive.
Download the client configuration file.
1. Go to Clients > Summary.
2. Select the client you want to download the configuration file from.
3. Right-click the client, and then click Download Config.
4. Save the bacula-fd.conf configuration file in the /opt/eversync/etc directory.
Warning
The configuration file contains a password that will allow privileged access to the client. The password shouldn’t be made publicly available, and should be removed immediately after successfully downloading to the client. We recommend setting the permissions on this file to allow only the root user to read it.
In the shell, enter the following command to start the backup client manually:
```
root\# /etc/init.d/rvx-backup start
```

HP/UX

Open the shell.
Enter the following commans:
```
root\# gunzip filename
root\# swinstall -s filepath
```
where filename is the name of the downloaded installation archive, and filepath is the full path to the downloaded installation archive.
Download the client configuration file.
1. Go to Clients > Summary.
2. Select the client you want to download the configuration file from.
3. Right-click the client, and then click Download Config.
4. Save the bacula-fd.conf configuration file in the /opt/eversync/etc/ directory.
Warning
The configuration file contains a password that will allow privileged access to the client. The password shouldn’t be made publicly available, and should be removed immediately after successfully downloading to the client. We recommend setting the permissions on this file to allow only the root user to read it.
In the shell, enter the following command to start the backup service manually:
```
root\# /sbin/init.d/eversync-backup start
```
To stop the service, enter the following command:
```
root\# /sbin/init.d/eversync-backup stop
```
Note
The DR backup agent should start automatically on boot (installer installs links in /sbin/init.d/rcX.d).

Windows

The DR backup agent for Windows supports for SQL Server 2005 and 2008, Exchange 2007 and Exchange 2010. We recommend that you install the latest service packs for both the operating system and the server applications.

The DR backup agent requires the following prerequisite software:

Visual C++ Runtime Libraries
.NET 4.0 framework
MAPI (for Microsoft Exchange Server mailbox plugin only)

If missing, most prerequisite software will be downloaded and installed automatically during the DR backup agent installation. But the MAPI software for Microsoft Exchange Server mailbox backup requires manual installation. The DR backup agent installer will provide a link to download the MAPI software.

Note

By default, the Backup Agent check box will be selected.

If you are installing on a Microsoft Exchange Server, the Exchange Database Plugin or Exchange Mailbox Level Plugin options may be available.

If you are installing on a Microsoft SQL Server, an additional option MSSQL Database Backup Plugin will be available.

macOS

The DR backup agent supports macOS 10.3 (Panther) and later. It installs a universal binary that supports both PowerPC and Intel hardware.

First, you need to install the client configuration file, and the client software after that. (If you have installed the client software first, and then the configuration file, you need to restart the system in order for the client service to find the client configuration.)

To download the client configuration file:

From the /usr folder, create the /rvx/etc/ folder.
In the CFA Management Console, go to Clients > Summary.
Select the client that you want to download the configuration file from.

In order for you to download the configuration file, the client needs to communicate with the DR backup agent.
Right-click the client, and then click Download Config.
Save the bacula-fd.conf configuration file in the /usr/rvx/etc/ folder.

To install the DR backup agent, run the downloaded installation file.

NetWare

Create the SYS:\system\revinetix folder.
Unzip the downloaded installation file and copy its contents into the newly created folder.

As software client files are updated, the client filename that you enter may differ to reflect the file version you downloaded.
Download the client configuration file as follows:
1. Go to Clients > Summary.
2. Select the client you want to download the configuration file from.
  
  In order for you to download the configuration file, the client needs to communicate with the DR backup agent.
3. Right-click the client, and then click Download Config.
4. Save the bacula-fd.conf configuration file in the \system\revinetix folder.
5. Open the shell and enter the following command to start the backup service:
```
SYS:\system\revinetix\revinetix
```

The NetWare client also has a migration feature that can be used to work with migration software such as the CaminoSoft MSHSM solution.

Follow these steps to enable migration:

Add the -m option to the Bacula-fd client start command in the revinetix.ncf file.
```
Load Address Space=Bacula sys:rvx\baculafd.nlm -m -c sys:rvx\bacula-fd.conf
```
Create a run.ncf command script on the Novell server, and save it in the SYS:\system\revinetix directory.

The client’s Run Before option in its configuration on the CFA must point to the script. The script should be as follows:
```
SYS:\MSHSM\MSSTUBSV SAVE PATH SYS: FILE
SYS:/STUBS/STUBSAVESAV FLAG /L /NODISP
delay 120
SYS:/MSHSM/MSSTUBSV SAVE PATH SYS: FILE
TEST:/STUBS/TESTSAV.SAV FLAG /L /NODISP
```

Note

NetWare doesn’t actually support command output redirection. The user must check the server console log screen to see the output. Some NLMs can’t be multiply loaded. The delay value in the example command script needs to be long enough (measured in seconds) for the first instance of MSSTUBSV to complete before the command runs again on another volume.