Comet Backup installation 

Windows 

System Requirements 

  • x86_32+SSE2 or x86_64 CPU architecture
  • Minimum 1024x600 screen resolution
  • We recommend using any version of Windows still under active security support from Microsoft (e.g. Windows 7, Windows 10, Windows Server 2008 or newer). Older versions of Windows might work, but are not supported by Comet.

Not compatible with Windows XP (released 2001) 

At the time of writing, there is no version of Comet available for Windows XP / Server 2003. All versions of Comet 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.

Install 

Run the CometBackup_install.exe file and follow the prompts.

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

Silent install (advanced) 

Comet 17.12.0 or later allow you to install and configure the software silently, by running install.exe /CONFIGURE=user:password via your remote management software.

Upgrading 

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

Silent upgrade (advanced) 

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

Uninstall 

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

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

macOS 

System Requirements 

  • x86_64 CPU architecture
  • OS X 10.7 or later

More specific system requirements are not yet available.

Linux (Debian, Ubuntu) 

Future versions of Comet Backup will provide .deb packages for Debian, Ubuntu, and compatible distributions. In the meantime, you can install Comet Backup using the "Other Distribution" package.

Linux (Red Hat Enterprise Linux (RHEL), CentOS) 

Future versions of Comet Server will provide .rpm packages for RHEL, CentOS, and compatible distributions. In the meantime, you can install Comet Backup using the "Other distribution" package.

Linux (Other Distribution) 

This is a distribution-agnostic package that can be used if Comet 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 

  • x86_32+SSE2 or x86_64 CPU architecture

ARMv6 / ARMv7 versions of the software will be available in the future.

Install 

Run the .run file. This is a self-extracting archive, with runtime dependencies on bash, xz, GNU awk, and standard GNU/Linux system utilities.

The software will be installed into a branded /opt/ subdirectory, and will start automatically.

Restarting 

The Comet Backup agent on "Other Distribution" Linux can be restarted using the backup-daemon-start.sh file.

If you are running commands over SSH, please be aware that this script runs in the foreground and will die when the SSH session is closed; to avoid this, you should daemonize it yourself via nohup / disown / double-fork.

For example (double-fork):

( cd /opt/CometBackup ; ./backup-daemon-start.sh >/dev/null 2>/dev/null & ) &

Run at startup 

The installer includes a backup-daemon-start.sh script that can start the service. It is recommended that you configure this script to be daemonized on system boot, by writing either an init.d script, systemd unit, or rc.local entry, depending on your specific Linux distribution.

Startup via rc.local 

You can make Comet Backup 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/CometBackup/backup-daemon-start.sh &

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

Startup via cron 

You can make Comet Backup 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/CometBackup/backup-daemon-start.sh
Startup via init.d 

No further documentation is available for this topic.

Startup via systemd 

No further documentation is available for this topic.

Upgrading 

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

  • The .run file will automatically upgrade the existing version
  • The software can be remotely upgraded via the Comet 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 Comet will support upgrading between installations regardless of product brand name.

Uninstall 

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

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