Slide Linux Agent¶
The Slide Linux Agent is a Linux package that runs as a systemd service and communicates with the Slide Box and the Slide Cloud to facilitate backups. For backups to function, the Slide Agent must be installed on the computer that you want to back up.
The Slide Linux Agent runs on supported distributions and uses the mooCBT kernel module (installed via DKMS) for change tracking. This page explains installation, supported file systems, current limitations, and other notes.
Installation¶
You can install the Slide Linux Agent by running the following command on any supported distribution and version. Press enter when prompted to confirm the install and to enable updates.
Tip
For non-interactive installation, you can pass -y to automatically accept all prompts.
After the installation is complete, you will see the pairing code at the bottom of your terminal. Navigate to your Slide Boxes page to pair the Slide Agent with a Slide Box. Detailed steps can also be found in the Getting Started guide.
View Pairing Code via Command Line¶
Don't worry if you missed the pairing code. You can always look it up again by running the slideagent command with the info parameter. This will display the agent's info, which includes the pairing code.
Linux Agent Known Limitations¶
File system support¶
The Slide Linux Agent supports the following file systems.
| Version | Supported |
|---|---|
| ext2/3/4 |  |
| XFS | |
| FAT32 | |
| NTFS |  |
| ZFS | |
| BTRFS | |
Note
NTFS support is planned, however there are no plans to support BTRFS or ZFS at this time.
Note
Backing up filesystems on raw block devices without partition tables is not currently supported.
Support for LVM is mixed, with more complicated configurations not supported at this time.
- Simple LVM setups, such as a linear volume on one disk without mirroring, striping, or RAID-style LVM layers are supported.
- Mirrored, striped, and RAIDed LVM layouts are not supported.
Storage with disk encryption (dmcrypt, setupcrypt, LUKS) is not supported. Backups may succeed, but restores may not preserve the original encryption scheme. Please note that Slide backups are encrypted themselves, and consider using User Managed Encryption Passphrases.
Supported architectures¶
The Slide Linux Agent and the mooCBT kernel module are 64-bit and run on x86_64 architectures.
Secure Boot¶
The Slide Linux Agent does not support Secure Boot. Secure Boot must be disabled to use the agent and kernel module.
Restore features¶
The initial Slide Linux Agent release only supports file restores and image exports. Support for virtualization, boot verification, push to protected system, and file search will be added in a future release.
Warning
When you create an image export, the image will have a running Slide Agent in the exported image. This means that if you restore the image and boot it (either to bare metal or a virtual machine), the agent will try to start taking backups as if it were the original agent. You must manually disable the agent, or backup corruption in future backups of the original agent could occur. The simplest way to disable the agent is to uninstall it, see below.
A future release will disable the Agent in the exported image like we do for the Windows Agent.
Public API pairing¶
Pairing the Slide Linux Agent through the Slide API is not available yet. The pairing process via the Slide Console is the supported method to pair the agent with your Slide Box.
Hardware requirements¶
The Slide Linux Agent requires the following hardware:
- x86_64 architecture
- 8 GB of RAM
Note
The mooCBT kernel module will use 10% of the volume's storage for its COW file during a backup for each volume in the backup, requiring a minimum of 10MB per volume. This space is freed up after the backup completes and only uses a small fraction (about 0.2%) of the volume's storage to track incremental changes.
Uninstallation¶
To uninstall the Slide Linux Agent, run the following command.
This will remove the mooCBT kernel module and therefore the Slide Linux Agent which depends on it. Some Agent configuration is left behind to allow reinstallation while maintaining the agent's association with your Slide account and Slide Box.
To remove all traces of the Slide Linux agent, including configuration, use the purge command.
Other notes¶
Major Distribution Upgrades¶
Major distribution upgrades, such as an upgrade from Ubuntu 22.04 (jammy) to 24.04 (noble), will require intervention. Distro-provided tooling will not update the installed Slide Linux Agent package repository listing when performing a major distribution upgrade.
On a major distribution upgrade, you need to update /etc/apt/sources.list.d/slideagent.list to match the version codename string of the new version.
For example, if the original version was Ubuntu 22.04, codenamed "jammy":
deb [arch=amd64 signed-by=/etc/apt/keyrings/slide.gpg] https://update.slide.tech/agent/pkg/stable jammy main
and the machine was updated to 24.04, codenamed "noble", then change it to:
deb [arch=amd64 signed-by=/etc/apt/keyrings/slide.gpg] https://update.slide.tech/agent/pkg/stable noble main
Indirect Branch Tracking (IBT)¶
Systems using IBT are not supported by the Slide Linux Agent, as it may trigger kernel panic with the mooCBT kernel module.
Indirect Branch Tracking (IBT) is a hardware-assisted control-flow integrity feature. Using it requires all of the following:
- A CPU that implements IBT (part of Intel CET and the AMD equivalent).
- Linux kernel 5.18 or newer.
- A Linux distribution that has IBT enabled by default on the distribution's kernel.
Our mooCBT DKMS / build scripts check for this environment because it can not run on systems with IBT. If all the requirements are met, the mooCBT build fails so the driver is never loaded into a configuration where it could cause problems on the machine.
Many recent Intel Core (from roughly 11th-generation “Tiger Lake” onward) and AMD (Zen 3 onward) processors include IBT support. View /proc/cpuinfo (look for ibt in flags on supported kernels) to confirm IBT support for a given host.
If you are unsure whether your system qualifies, rely on the mooCBT build checks: a failed build means the module was not installed because the environment was not considered safe for loading.