Category: eazyBackup Installation

Linux (Other Distribution)

This is a distribution-agnostic package that can be used if eazyBackup does not have a more specific package available for your Linux distribution.

Please note that in order to avoid distribution-specific differences, the package does not automatically start on boot. You should configure your system to run the launch script in /opt/ on boot (e.g. via a systemd unit, upstart script, /etc/init.d/ script, or a line in init.rc).

System Requirements

  • CPU: x86_64, or x86_32 with SSE2, or ARM (see below)
  • Kernel 2.6.23 or later
  • Dependencies
    • bashxz, GNU awk, and standard GNU/Linux system utilities
    • ca-certificates and tzdata (see below)

ARM CPU support

eazyBackup is available for multiple ARM platform variants. The eazyBackup installer will select the best available binary for your hardware at install-time.

Platform Description
ARMv8l ARM 64-bit (Aarch64), no glibc required
ARMv7l ARM 32-bit with vfp, and a glibc-based OS with the "hard-float" ABI (gnueabihf)
ARMv6kl ARM 32-bit with vfp, no glibc required

Timezone database dependency

eazyBackup on Linux requires the OS to provide an up-to-date timezone database, to perform timezone calculations

  • On many Linux distributions, installing the tzdata or timezone package should be sufficient
  • Otherwise, eazyBackup will look for a timezone database in all of the following locations;
    • /usr/share/zoneinfo
    • /usr/share/lib/zoneinfo
    • /usr/lib/locale/TZ

CA certificate database dependency

eazyBackup on Linux requires the OS to provide an up-to-date set of root certificate authorities, to validate HTTPS / SSL connections.

  • On many Linux distributions, installing the ca-certificates package should be sufficient
  • Otherwise, eazyBackup will look for a certificate bundle in all of the following locations;
    • /etc/ssl/certs/ca-certificates.crt (used by Debian/Ubuntu/Gentoo etc.)
    • /etc/pki/tls/certs/ca-bundle.crt (used by Fedora/RHEL 6)
    • /etc/ssl/ca-bundle.pem (used by OpenSUSE)
    • /etc/pki/tls/cacert.pem (used by OpenELEC)
    • /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem (used by CentOS/RHEL 7)


Run the .run file. This is a self-extracting archive, and will need to be executed in an elevated environment.

The installer will:

  1. install the software into a branded /opt/ subdirectory
  2. prompt you for an initial username and password
  3. register the current Linux device into that eazyBackup account
  4. start running eazyBackup in the background.

If you make a mistake with the username/password prompt, you should follow the below instructions to uninstall the software, and then start the installation again.

Linux Install options

You can control the installer by setting environment variables in your shell before running the .run file.

The following options are available:
WRITE_INSTALL_LOG Set this to a file path, to record details of the installation.
OVERRIDE_INSTALL_SERVER Set this to a URL (including http/https and trailing slash) to override the eazyBackup Server URL used by eazyBackup.

You can set an environment variable in bash either on the same line e.g. WRITE_INSTALL_LOG=install.log ./
or as a separate export command e.g. export WRITE_INSTALL_LOG=install.log followed by ./

Restarting at boot

The installer creates a script that can start the service. The eazyBackup agent on "Other Distribution" Linux can be restarted by running the script.

In order for eazyBackup to start after a system reboot, you must configure this script to be run on system boot. Different Linux distributions support different methods for running commands on system boot: choose the most appropriate method for your Linux distribution. Some common choices are documented below.

Preserve HOME environment variable

eazBackup uses the $HOME environment variable to find its saved credentials. When configuring eazyBackup to start at system boot, ensure that the $HOME environment variable is set (i.e. to /root/), to ensure that eazyBackup can find its saved credentials. If eazyBackup is unable to log in, it's possible that your Linux distribution does not set $HOME at this early-boot stage. In that case, you should try running HOME=/root/ /opt/eazyBackup/ & instead. eazyBackup will automatically try to use /root/ as the $HOME directory if $HOME is not already set or if it is set to a blank path.

Note: If you execute the .run installation script as root, this may have different results than if you execute the .run script using an elevated terminal session with 'sudo'. The 'sudo' command preserves the $HOME variable on Ubuntu; whilst on Debian the $HOME variable is erased, and sudo then sets it to the home directory of the originating user.

Start in the background

If you are running commands over SSH, please be aware that the script runs in the foreground and will die when the SSH session is closed. You can avoid this by running the script in the background.

You can run the script in the background (daemonize) by using the file instead.

Startup via rc.local

You can make eazyBackup start at system boot by adding an entry to the rc.local file.

First, find the rc.local file on your system:

  • /etc/rc.local (Debian/Ubuntu)
  • /etc/rc.d/rc.local (CentOS/RHEL)

Add the following content to the rc.local file:

/opt/eazyBackupBackup/ &

If the rc.local file contains an exit 0 statement, the additional command should be added before such a statement.

As of CentOS 7, the rc.local file is not executable by default. You should run chmod +x on the rc.local file to enable using this method for startup scripts.

Startup via rc.d

You can make eazyBackup start at system boot by adding a file to the rc.d directory.

First, find the rc.d directory on your system:

  • /usr/local/etc/rc.d (Synology DSM 6.1+)

Add a new file to the rc.d directory with the following contents:


Mark the file as executable: chmod +x /usr/local/etc/rc.d/

Startup via cron

You can make eazyBackup start at system boot by adding an entry to root's crontab.

  1. Run crontab -e -u root to launch a crontab editor
  2. Add the line @reboot /opt/eazyBackupBackup/

Startup via init.d

No further documentation is available for this topic.

Startup via systemd

You can use the following unit as an basic example:


Description=eazyBackup Client









This unit file correctly starts the eazyBackup service at system boot.

However, the process management in systemd is not fully compatible with the way eazyBackup's multi-process model works. In particular, there are compatibility issues with the software updater. As a result, the above unit is (A) unable to take advantage of process group cleanup; (B) unable to auto-restart the eazyBackup agent service; and (C) after a software upgrade, eazyBackup will keep running but the unit will remain in "exited" state.

Autostart for graphical desktop application

In the "Other Distribution" package, the graphical application is not automatically configured to start when the desktop logs in. You may add backup-interface --background as an autostart command to your desktop environment's settings.


The "Other Distribution" version of eazyBackup supports upgrading the software, with some caveats:

  • The .run file will automatically upgrade the existing version
  • The software can be remotely upgraded via the eazyBackup Server web interface.

However, the existing service will only be replaced with the upgraded version if the product brand name is unchanged.

Future "Other Distribution" versions of eazyBackup will support upgrading between installations regardless of product brand name.


To uninstall "Other Distribution" versions of eazyBackup, you should

  1. Stop all eazyBackup processes
  2. Remove the relevant subdirectory under /opt/
  3. Remove any custom startup scripts

Change password on Linux client

Use the 'Change Password' function in the eazyBackup client area.

Then fully uninstall and reinstall the client, using the new credentials. Your device settings and Protected Items will be preserved.

macOS Installation

System Requirements 

  • x86_64 CPU architecture
  • OS X 10.9 or later (10.11 or later recommended)


The macOS operating system requires codesigning to be enabled in order to launch a downloaded .pkg file. If you have not configured codesigning for macOS, you will be unable to launch the installer. However, you can bypass this by right-clicking the .pkg file and choosing Open.

Run the eazyBackup.pkg file and follow the prompts.

Once installed, the client software prompts for account details to log in.

If you are running the .pkg file from the Downloads directory, macOS will offer to move the .pkg file to the Trash after a successful installation.


The installer will safely remove and upgrade any prior versions of eazyBackup, including those with a different software branding.

Silent upgrade (advanced)

You can silently upgrade the software remotely via the eazyBackup Server interface, or by running /usr/sbin/installer -allowUntrusted -pkg "eazyBackup.pkg" -target / via your remote management software.


macOS does not have a standard system for uninstalling programs. However, you can still uninstall eazyBackup by running the following command from a terminal window:

sudo -u root "/Applications/"

This will automatically stop all running eazyBackup processes, unregister eazyBackup's launchd services, and remove all application files from the disk.

Uninstalling the software preserves any username/password credentials saved on this computer. To remove the saved credentials, delete the /Users/USERNAME/Library/Preferences/backup-interface/config.sys file.


Windows Installation


System Requirements

  • x86_32+SSE2 or x86_64 CPU architecture
  • Minimum 1024x600 screen resolution
  • Windows Vista, 7, 8, 8.1, 10, or newer
  • Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016, or newer

Microsoft will end Extended support for Windows 7, Server 2008, and Server 2008 R2 in early January 2020. Future versions of eazyBackup may drop support for older versions of Windows no longer under active security support from Microsoft.

Not compatible with Windows XP (released 2001)

At the time of writing, there is no version of eazyBackup available for Windows XP / Server 2003. All versions of eazyBackup rely heavily on features that were only introduced in Windows Vista / Server 2008.

Windows XP / Server 2003 no longer receives security patches from Microsoft. It is unsafe to connect such a machine to the internet. If you are attempting to supply backup services to a customer in this situation, you should arrange to first upgrade their operating system with urgency.

Despite the above warning, our company would like to support as many platforms as possible. It might become supported in the future.


You can work around this issue by:

  • installing eazyBackup on another machine, and then backup the XP machine over the network; or
  • virtualizing the XP machine, and backing up the VM guest from the VM host. This also allows you to remove internet access from the XP machine.


Visit our downloads page to obtain the latest copy of eazyBackup

You should now have a .zip file which contains the installer. Right click the .zip file and choose 'Extract Here'

The .zip archive contains two files, install.dat & install.exe. Right click the 'install.exe' choose Run as administrator.

"Do you want this app to make changes to your device?" Click Yes.

When you complete the install, eazyBackup asks for your account details the first time you open the program.

You can find your backup account username and reset the account password within the
client area from Services -> Manage Accounts.

Silent install (advanced)

eazyBackup allows you to install and configure the software silently, by running install.exe /CONFIGURE=user:password via your remote management software.

Service account 

eazyBackup 18.6.0 and later automatically create a Virtual Account (NT SERVICE\backup.delegate) with all necessary permissions to back up files on the PC.

Isolating eazyBackup under a Virtual Account is supported on Windows 7 or later, and Windows Server 2008 R2 or later when that server is not a Domain Controller. On other machines (e.g. Windows Server 2008 RTM, and domain controllers) the backup service will run as LOCAL SYSTEM by default.

On a Domain Controller running Windows Server 2008 R2 or later, we recommend configuring a Managed Service Account inside Active Directory for the backup service. This allows you to isolate the backup service permissions in a password-less service account. You should apply this to the backup.delegate service (but not the backup.elevator service, used for software updates).


The installer will safely remove and upgrade any prior version of eazyBackup, including those with a different software branding.

If the product name is changed as a result of the installation process, the newly-branded software may be installed into the old-branded directory name. You can avoid this issue by completely uninstalling and reinstalling the software.

Silent upgrade (advanced)

You can silently upgrade the software remotely via the eazyBackup Server interface, or by running install.exe /S via your remote management software.

Service account

In eazyBackup 19.3.0 and later, if you customize the backup.delegate service to use any user account other than LOCAL SYSTEM or NT SERVICE\backup.delegate, your changes will be preserved in any future software upgrade.

In eazyBackup 18.6.1 and later prior to 19.3.0, such changes will be preserved. However, if the chosen user account requires a password, it may need to be reconfigured after the software upgrade.

Prior to eazyBackup 18.6.1, any changes to the service user account were not preserved across software upgrades.


The software can be uninstalled via the "Programs and Features" section in the Windows Control Panel.

During this process, you may be prompted whether you wish to preserve any username/password credentials saved on this computer.

You can also remove the saved credentials manually by deleting the AppData/Roaming/backup-interface/config.sys file.

You should also remove the saved credentials from the backup.delegate service. This is stored in the C:\Users\backup.delegate\AppData\Roaming\backup-tool\config.dat file (if the backup.delegate service was running as the NT SERVICE\backup.delegate user; the path may differ if the service was running as another user account).

Silent uninstall 

You can silently uninstall eazyBackup for Windows by passing the /S command-line argument (e.g. "C:\Program Files\eazyBackup\Uninstall.exe" /S).