Downloads

The Software subtab contains links to download client software to the client computer.

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 a root shell.
Enter the following:
```
root\# cd /tmp
root\# tar xf /path/to/Eversync-backup-client-6.1.0.xxx.XXXX.YYYY.tar
root\# cd Eversync-backup-client-6.1.0.xxx.XXXX.YYYY
root\# bash ./install.sh
```
For your specific client, for the 6.5.0.xxx.*XXXX*.*YYYY* strings in these commands, substitute the corresponding client-specific information from your client operating system filename. For example, for the Solaris/Sparc operating system, you would enter the following commands:
```
root\# cd /tmp
root\# tar xf /path/to/rvx-backup-client-1.5.3.22.sparc.SunOS.tar
root\# cd rvx-backup-client-1.5.3.22.sparc.SunOS
root\# bash ./install.sh
```
Your file version information may be different from what is shown in the table due to updates in the downloaded software.
Download the client configuration file.
1. Go to Clients > Summary.
2. Select the client that 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 directory /opt/eversync/etc.
The configuration file contains a password that will allow privileged access to the client; the password should not be made publicly available, and should be removed immediately after successfully downloading to the client. We recommend setting the permissions on this file to only allow root to read it.
Enter root\# /etc/init.d/eversync-backup start to start the backup client manually.

HP/UX

Open a root shell.
Enter the following:
```
root\# gunzip eversync-agent-VERSION.ia64.depot.gz
root\# swinstall -s /full/path/to/eversync-agent-VERSION.ia64.depot.gz
\\\*
```
Your file version information may be different from what is shown in the table due to updates in the downloaded software.
Download the client configuration file.
1. Go to Clients > Summary.
2. Select the client that you want to download the configuration file from.
3. Right-click the client and select Download Config.
4. Save the bacula-fd.conf configuration file in the directory /opt/eversync/etc/.
The configuration file contains a password that will allow privileged access to the client; the password should not be made publicly available, and should be removed immediately after successfully downloading to the client.
Enter root\# /sbin/init.d/eversync-backup start to start the backup client manually.

To stop the client, enter root\# /sbin/init.d/eversync-backup stop.

The agent should start automatically on boot (installer installs links in /sbin/init.d/rcX.d).

Windows

The Windows backup agent includes support 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.

For DR Image backups, it will require the additional download and install of the DR Imaging software. The software is compatible with both x86 and x64 versions of Windows. The DR Imaging software works with the windows agent, and both need to be installed to do DR Image backups of a client machine.

Prerequisites

Before installing the Windows backup agent, make sure the following software is installed:

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

Most required software will be automatically downloaded and installed during installation if it is not already installed, but the MAPI software for exchange mailbox backups requires manual installation. The agent installer will provide a link to the MAPI software to download from Microsoft if you need it and don’t have it installed already.

Installing Backup Agent for Windows

Run the Infrascale-backup-client-X.exe file.
If the prerequisite software is missing, it will be installed automatically.
Click Install to install the listed components, or click Cancel to exit the installation.
Follow the instructions to complete the process.

By default, the Infrascale Backup Agent check box will be checked.

If you are installing on an Exchange Server, the Exchange Database Plugin or Exchange Mailbox Level Plugin options may be available. See Exchange Server Backups.

If you are installing on a SQL Server, an additional option MsSQL Database Backup Plugin will be listed.
After installation is completed, the following window shows:
- If you select the manual method, specify the CFA address, CFA password, and client name.
- If you select the active directory method, click Lookup. The screen will display a list of the CFAs detected on your network. Select your CFA from the list, and then click Next. Then, on the screen that appears, type the administrator password.

Installing DR imaging software

Run the DR Imaging software installer.
Click Install.
Click Close when installation completes.

Configuring Backup Agent for Windows

Use the Infrascale Agent Configuration (InfrascaleConfig) program to configure the Service Control, Exchange Database Backup, Exchange Mailbox Backup, and SQL Backup tabs.

Service Control tab

The Service Control tab controls how the Bacula service runs. The default account type is the local system account, but you can change it to run as a user account. Running as a user account is usually required for the Exchange agent to run properly. The Service Control tab is the same for all Windows agents.

To capture your system station information, check the Enable System State Backup check box. Client settings, such as setting the location to save the .bkf file, should be configured here in the Service Control tab. However, each client file set can enable or disable the entire System State feature so that some clients use it and others don’t.

Exchange Database Backup tab

See Exchange Server Backups for more information on configuring Exchange backups.

This tab allows to enable or disable the online backup (enabled by default). You can also choose to truncate the Exchange logs after the backup, though by default Exchange logs are truncated after full backups only. The following setting is to truncate after incremental and differential backups, which is not recommended:

Exchange Mailbox Backup tab

The Exchange server tab also displays the Message Store(s) and server name to be backed up, and indicates whether the permissions are OK for the account. Also, mailboxes in the message store can be displayed. Finally, you can select the restore method (overwrite, skip, or duplicate) if a message already exists.

SQL Backup tab

On an SQL Server you can use the SQL Backup tab to enable or disable the SQL backup (enabled by default).

The screen displays a list of databases found on the server. By default, all databases, except the tempdb database, are selected for backup. To explicitly include or exclude a database for backup, check the check box in the Include or Exclude column, respectively.

SQL Support Chart

The CFA supports the following SQL versions for client configuration:

SQL Server 2005
SQL Server 2008
SQL Server 2012
SQL Server 2014

CFA does not support backing up and restoring of the Evaluation editions and IA64 versions.

macOS

The backup agent supports macOS 10.3 (Panther) or 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 be communicating with the backup agent (as indicated by a green check mark in the Status column).
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 backup agent, run the rti-backup-client-X.X.X.X.MacOSX.mpkg file.

NetWare

Create the SYS:\system\revinetix folder.
Unzip the rvx-backup-client-3.0.4 090218.i386.netware.zip file and copy its contents into the new \system\revinetix folder.

As software client files are updated, the client filename that you enter may be different to reflect the file version that you downloaded.
Download the client configuration file as follows:
1. Go to Clients > Summary.
2. 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 be communicating with the backup agent (as indicated by a green check mark in the Status column).
3. Right-click the client, and then click Download Config.
4. Save the bacula-fd.conf configuration file in the \system\revinetix folder.
5. Enter SYS:\system\revinetix\revinetix to start the backup service.

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 enabling migration:

Add the -m option to the Bacula-fd client start command in the revinetix.ncf file.

For example: 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 similar to the following:
```
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
```

NetWare does not actually support command output redirection. The user must check the server console log screen to see the output. Some NLMs cannot 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.