Datto Endpoint Backup v2 Linux agent

Module: Endpoint Backup v2

The Datto Endpoint Backup v2 Linux agent provides file-level backups of supported Linux servers and workstations.
The agent discovers volumes, applies default exclusions, and backs up file metadata, access control lists, extended attributes (including SELinux security labels), and symbolic links.

You manage Linux assets from the same Endpoint Backup v2 dashboard, Creating a backup policy, and Understanding retention in Datto Endpoint Backup v2 settings as your Windows and macOS assets.

System requirements

Supported distributions

Datto supports the Datto Endpoint Backup v2 Linux agent on x64 systems as shown.
Releases in the Not tested column might work, but Datto does not support them.
On distributions that support it, the agent uses the DattoBD kernel module to take volume snapshots. On the others, it backs up volumes without a snapshot.

Distribution Tested and supported,
snapshots with DattoBD
Tested and supported,
no snapshots
Not tested,
might work, not supported
Ubuntu 22.04, 24.04 26.04 —
Debian 11, 12 13 —
Red Hat Enterprise Linux 9 10 8
AlmaLinux 9 10 8
Rocky Linux 9 10 8
Oracle Linux 8, 9 10 —

Hardware

The Linux agent requires 64-bit (x64) hardware with at least 1 GB of free RAM and 10% of the protected volume available.

Volume snapshots and DattoBD

IMPORTANT  DattoBD is a kernel module.
If it cannot load, for example because Secure Boot blocks it, the machine runs a custom kernel, or module loading is restricted, the agent backs up without snapshots.
To confirm that DattoBD is loaded, check that /dev/datto-ctl exists.

File systems

The Linux agent supports volumes using:

  • ext4
  • XFS
  • ZFS
  • BtrFS
  • VFAT

Anti-virus

Make sure that your anti-virus or endpoint detection and response tool accepts the Linux agent.
See Anti-virus exceptions: Linux paths.

Encryption

The agent encrypts data in transit and at rest.
To use your own encryption key, supply it when you install the agent. If you do not supply one, Datto encrypts the asset with a Datto-managed key.
A customer-managed encryption key must be at least 8 characters long.
See Data encryption.

If you supply a customer-managed encryption key, the agent stores it in the agent's install folder, /opt/datto-backup-agent.
The file is plain text, protected by Linux file permissions, so anyone with root access to the machine can read the key. Limit root access accordingly.

ALERT  If you lose a customer-managed encryption key, you CANNOT recover your data.

Limitations

  • The Linux agent performs file-level backups, not bare metal recovery.
  • The Linux agent supports 64-bit (x64) hardware only.

Installing the agent

Installation packages ship in both deb and rpm formats, and both are signed.
On distributions that need it, the package installs DattoBD as a dependency.

To install the Linux agent, complete the following steps:

  1. Log in to UniView (login.backup.net).
  2. Creating a backup policy for your Linux assets.
  3. Click Endpoint Backup > Deployment Tokens.
  4. Create a deployment token that uses your new policy, then copy the token.
  5. Click Download Agent, then select the package that matches your distribution:
  6. Install the package on the target machine with the command for its distribution.
    Replace {YOUR_TOKEN_HERE} and {YOUR_ENCRYPTION_KEY_HERE} with your own values.

    On Ubuntu and Debian, run:

    sudo REG_TOKEN={YOUR_TOKEN_HERE} CLEAN_INSTALL=1 ENCRYPTION_KEY={YOUR_ENCRYPTION_KEY_HERE} apt install ./DattoBackupAgentInstaller-x64.deb

    On Rocky Linux, AlmaLinux, Oracle Linux, and Red Hat Enterprise Linux, run:

    sudo REG_TOKEN={YOUR_TOKEN_HERE} CLEAN_INSTALL=1 ENCRYPTION_KEY={YOUR_ENCRYPTION_KEY_HERE} dnf install ./DattoBackupAgentInstaller-x64.rpm

The install command accepts the following variables:

  • REG_TOKEN: your deployment token. This is optional. If you leave it out, pair the agent with a shortcode after installation.
  • ENCRYPTION_KEY: your customer-managed encryption key, at least 8 characters long. This is optional.
    If you leave it out, Datto encrypts the asset with a Datto-managed key.
  • CLEAN_INSTALL: set to 1 for a clean installation. See Clean installation.

The Linux installer does not prompt for a deployment token or an encryption key. You can supply them only in the install command.
You cannot add your own encryption key later without reinstalling the agent.

IMPORTANT  Replace the placeholders before you run the command. If you leave ENCRYPTION_KEY={YOUR_ENCRYPTION_KEY_HERE} unchanged, the placeholder text becomes your encryption key. If you are not using a customer-managed key, remove ENCRYPTION_KEY from the command.
The encryption key is part of the command, so it can be saved in your shell history and in the logs of the tools you deploy with. Protecting it is your responsibility.

If you supply a token or an encryption key, the installer checks it before it finishes.
Installation stops with an error if the deployment token is not valid or if the encryption key is shorter than 8 characters.

The agent takes its first backup once it is paired.

Clean installation

IMPORTANT  Consider these warnings before working with the clean install flag:
- Do not ever use the clean install flag in scripts or automations.
- Using the clean install flag consumes a new license. You must delete your old asset in UniView to avoid being billed for both.
- Clean install is a permanent, one-way operation with no revert path.
- Clean install will create a new asset with same name, which can be visually confusing if you don't delete the previous instance.

With CLEAN_INSTALL=1, the installer creates new encryption keys, change tracking files, and agent settings instead of reusing any that an earlier installation left on the machine.
By default (CLEAN_INSTALL=0), the installer keeps them.

  • Only use CLEAN_INSTALL=1 when you want the agent to start over with new settings and encryption keys.
  • Leave it out when you reinstall the agent and want to keep its existing settings and encryption keys.

Install folder and logs

The agent installs in /opt/datto-backup-agent. This folder contains:

  • DattoBackupAgent: the agent
  • DattoBackupAgentStatus: the status application shown in the system tray
  • DattoBackupAgentUpdater: the updater, which checks for and installs agent updates
  • config.sqlite: the agent's settings
  • The agent's log files
  • keychain: your customer-managed encryption key, if you supplied one

Pairing with a shortcode

If you install the agent without a deployment token, pair it with a shortcode:

  1. On the Linux machine, click the Datto Backup Agent icon in the system tray and generate a shortcode.
  2. Log in to UniView (login.backup.net).
  3. Paste the shortcode into UniView by clicking the link icon, then click Pair.

Shortcodes come from the system tray icon, so this method needs a desktop environment.
On a machine without one, install the agent with a deployment token.

System tray

On machines with a desktop environment, the agent adds a system tray entry for the currently logged-in user.

Default exclusions

The agent applies a set of default exclusions so that backups leave out temporary files, caches, and pseudo-file systems.

Selective inclusion and exclusion

With selective backups, you define custom inclusions and exclusions for folder paths or volumes you choose, so that all of your selected data, and only your selected data, is backed up.

Linux paths are absolute and case-sensitive, so the agent uses the same inclusion and exclusion logic as the macOS agent rather than the drive-letter syntax used on Selective inclusion and exclusion.

Inclusion restricts backups

If no inclusions are set, all supported, non-excluded volumes are backed up.

IMPORTANT  If any inclusions are set, those specified inclusions are the only data backed up.

Inclusion restriction example

If you define an inclusion for: C:\Users\datto\Documents or /Users/datto/Documents, then only that one folder is backed up.
Everything else on all other volumes is excluded.

Wildcards

Use the following wildcards to define your backup policy:

? - A non-recursive wildcard that represents exactly one character.

* - A non-recursive wildcard that represents zero or more characters.

** - A recursive wildcard that substitutes for path segments.
** cannot be combined with other symbols (e.g., C:\Logs\**.log and /Logs/**.log function like a simple *).

When applying rules to selective backups, exclusions take precedence over inclusions.

Agent updates

The Linux agent keeps itself current.
The package installs an updater alongside the agent, so you do not need to push new agent versions yourself or upgrade the agent package to stay on the latest version.

  • The updater checks for a new version every 15 minutes.
  • Agent updates do not come from an apt or dnf repository.
    When an update is available, the updater downloads the new package for your distribution, deb or rpm, and installs it with the system's own package tools, so your package manager always shows the installed version.
  • Every package is signed with a GPG key, and the updater applies only signed, verified updates.
  • To check for an update right away, restart the updater service:

    sudo systemctl restart datto-backup-agent-updater

  • To update the agent manually, download the latest package and install it with apt or dnf, as described in Installing the agent.
    Leave out CLEAN_INSTALL so that the agent keeps its settings and encryption keys.

Restoring from a Linux asset

Start a restore the same way as for any other asset.
See Recovering an endpoint.

You can restore files to the original asset, to an alternate asset, or download them as a ZIP file.
Restores include each file's access control lists, extended attributes, and symbolic links.

NOTE  After restoring to an alternate asset, check that file ownership is correct.

TIP  Track the status of your restore with the Recovery operations view.

Troubleshooting

If installation stops with an error, check the following:

  • If you supplied a deployment token, you copied the full token from Deployment Tokens, and the token still exists.
  • If you are using a customer-managed encryption key, it is at least 8 characters long.

If the protected asset does not appear in UniView, take the following steps:

  1. Verify the deployment token used at registration.
  2. Check network connectivity.
    The agent needs outbound traffic on port 443 to *.datto.io.
  3. Review the agent logs in /opt/datto-backup-agent.

Support

Submit a Kaseya Helpdesk request for help with the Linux agent.

Related topics