> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/backup-and-storage/backup-service/how-tos/install-acronis-backup-agent.md).
# Install Acronis Backup Agent on Linux
Acronis Backup Agent facilitates the backup and recovery of data on Linux systems. It allows users to protect and restore their data efficiently. The Acronis Agent is installed on individual machines and servers to activate seamless integration with the Acronis Backup infrastructure, providing features such as scheduled backups, recovery options, and data protection in various environments.
## How the backup agent works with the Linux kernel
The Acronis Backup Agent requires two kernel modules to function:
* `snapapi`: For consistent snapshot-based backups.
* `file_protector`: For Active Protection, which monitors file access in real time to detect and block ransomware and cryptomining activity.
These modules are compiled specifically for the kernel version running on your system at the time of installation and must be rebuilt every time the kernel is updated.
This means the server must have the GNU Compiler Collection (GCC) and related build tools at installation time and after every kernel update.
{% hint style="info" %}
**Note:** Some hardening policies prohibit C compilers on production servers. If your organization has such a policy, grant an exception for any server running the Acronis Backup Agent.
{% endhint %}
The installer automatically installs GCC, Make, and Dynamic Kernel Module Support (DKMS) if they are not already present. The kernel header packages are the only dependencies the installer cannot always resolve on its own. For more information, see [Prepare for installation: kernel header](#prepare-for-installation-kernel-header).
## Prerequisites
* Only contract administrators, owners, and users with the **Create Backup Units** privilege can use the **Backup Service Console**.
* Ensure that you have the following:
* Appropriate permissions for installation.
* Your browser allows pop-ups.
* A backup unit to download the installer.
* Internet connectivity for the Virtual Machine (VM) and all its ports are open:
| **Type** | **Destination IP address** | **Ports** |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Management servers | 85.215.127.12
85.215.127.13
85.215.127.14
85.215.127.15
| TCP ports `443` and `8443` are used to access the **Backup Service Console**, register the backup agents, download the certificates, obtain user authorization, and download files from the cloud storage. The backup agents use the whole range from `7770`-`7800` to communicate with the management server. |
| Storage servers | 85.214.7.152
85.214.7.153
| TCP port `44445` is used by backup agents for data transfer during backup and recovery. |
* **SUSE Linux Enterprise Server (SLES):** SUSE Linux Enterprise requires active product registration through the SUSE Customer Center (SCC) before any package can be installed. If your repositories are empty, register first:
```bash
SUSEConnect -r
```
## Prepare for installation: kernel header
The installer needs the **kernel header package** matching your currently running kernel to compile the modules. Cloud images sometimes run a kernel version whose headers have already been removed from the distribution's package repository. If this is the case, the installation fails.
{% stepper %}
{% step %}
### Check whether headers are available
Run this before doing anything else:
**Debian / Ubuntu:**
```bash
apt-cache show linux-headers-$(uname -r)
```
**RHEL / AlmaLinux / Rocky Linux:**
```bash
dnf info kernel-devel-$(uname -r)
```
**SLES:**
```bash
zypper info kernel-default-devel
```
* **Package metadata returned?** Headers are available. Skip to [Install the kernel headers meta-package](#install-the-kernel-headers-meta-package) and then proceed to the installation.
* **No output / error?** Headers are no longer in the repository. Update the kernel first using option A or option B.
{% tabs %}
{% tab title="Option A: Full distribution update" %}
This is the simplest and safest option. Afterward, the required headers will be available, and the system will be up to date:
**Debian / Ubuntu:**
```bash
apt update && apt upgrade -y
# Reboot if a new kernel was installed as part of the upgrade
reboot
```
**RHEL / AlmaLinux / Rocky Linux:**
```bash
dnf upgrade -y
reboot
```
**SLES:**
```bash
zypper update -y
reboot
```
{% endtab %}
{% tab title="Option B: Update the kernel only" %}
If you want to avoid a full system upgrade, update only the kernel:
**Debian:**
```bash
apt update && apt install -y linux-image-cloud-amd64
reboot
```
**Ubuntu:**
```bash
apt update && apt install -y linux-image-generic
reboot
```
**RHEL / AlmaLinux / Rocky Linux:**
```bash
dnf upgrade -y kernel kernel-devel kernel-headers
reboot
```
**SLES:**
```bash
zypper update -y kernel-default
reboot
```
{% endtab %}
{% endtabs %}
{% endstep %}
{% step %}
### Install the kernel headers meta-package
Regardless of whether you updated the kernel in [step 1](#check-whether-headers-are-available), install the **headers meta-package** for your distribution. Unlike version-specific header packages, meta-packages track the active kernel. This ensures matching headers are installed during future kernel updates, allowing DKMS to rebuild modules automatically without manual intervention.
{% hint style="info" %}
**Note:** At the time of writing, this step is required to reliably support future kernel updates. A future Acronis release may handle this automatically.
{% endhint %}
**Debian (cloud images):**
```bash
apt install -y linux-headers-cloud-amd64
```
**Debian (non-cloud / bare metal):**
```bash
apt install -y linux-headers-amd64
```
**Ubuntu:**
```bash
apt install -y linux-headers-generic
```
**RHEL / AlmaLinux / Rocky Linux:**
Enterprise Linux has no matching meta-package. The recommended approach is to keep the system fully updated so that `kernel-devel` always matches the running kernel:
```bash
dnf upgrade -y kernel kernel-devel kernel-headers
```
Configure automatic updates using `dnf-automatic` or your patch management workflow to keep this going forward.
**SLES:**
Keep the system registered and fully patched through your standard `zypper update` workflow.
{% endstep %}
{% step %}
### Ubuntu images
Ubuntu cloud images require following actions for the installer to run successfully:
#### Activate the `universe` repository and install `rpm`
The installer requires the `rpm` tool. On Ubuntu cloud images, the `universe` repository is not activated by default:
```bash
apt-add-repository -y universe
apt update
apt install -y rpm
```
#### Install extra kernel modules
The installer requires the `nls_utf8` module, which is not loaded on Ubuntu cloud images by default:
```bash
apt install -y linux-modules-extra-$(uname -r)
modprobe nls_utf8
```
{% endstep %}
{% endstepper %}
## Download the agent (command line)
{% hint style="warning" %}
**Warning:** Do not download to `/tmp`. On cloud VMs, `/tmp` is typically a memory-backed filesystem (tmpfs) sized at a fraction of RAM. The installer binary is about 1.1 GB and fails to download if `/tmp` is too small.
{% endhint %}
Download the agent to `/root` or `/var/tmp` instead:
```bash
curl -L -o /root/name_of_your_agent.bin \
"https://backup.ionos.com/bc/api/ams/links/agents/redirect?language=multi&system=linux&architecture=64&productType=enterprise"
chmod +x /root/name_of_your_agent.bin
```
## Download the agent (Web browser)
{% stepper %}
{% step %}
### Navigate to the Backup Unit Manager
1\. In the **DCD**, go to **Menu** > **Backup & Storage** > **Backup Unit Manager**.
2\. Select a backup unit which you want to download the backup agent installer.
3\. Click the **Open Console** option within the **Backup Unit Manager**.
{% endstep %}
{% step %}
### Add a device
1\. A **Backup** window will open up with the [Backup URL](https://backup.ionos.com/). Go to **DEVICES** > **Add**.
2\. In **Add Devices** window, scroll down to **SERVERS** and then select **Linux**.
{% endstep %}
{% step %}
### Download the installer
1\. To allow downloads on the [Backup URL](https://backup.ionos.com/), confirm your action by selecting **Allow**.
{% hint style="info" %}
**Note:**
* You can cancel the download if you only need the URL.
* Open the **Download Folder** on your browser and copy the link address. Delete everything after `.bin` to get the download URL directly. Now you can use the URL to download the backup agent installer on your target machine. **Example:** `wget https://backup.profitbricks.com/download/u/baas/x.0//name_of_your_agent.bin`
{% endhint %}
{% hint style="success" %}
**Result:** The **Backup Agent Installer** is now downloaded.
{% endhint %}
{% endstep %}
{% step %}
### Make the installer executable and run it
To make the downloaded binary file executable, use:
```bash
chmod +x name_of_your_agent.bin
```
{% endstep %}
{% endstepper %}
## Install Backup Agent
{% stepper %}
{% step %}
### Run the installer
`./name_of_your_agent.bin`
{% endstep %}
{% step %}
### Select components to install
1\. The Acronis Agent setup will now be initiated. Select the components that you want to install from the **Component Selection** list. You can choose **Agent for Linux** and then select **Next**.
{% endstep %}
{% step %}
### Install required packages
1\. To install the required packages automatically, select **Continue**; otherwise, select **Skip**.
2\. The installation of the required packages will begin.
{% endstep %}
{% step %}
### Register the machine
1\. Once the installation is completed, a prompt to register the machine will be displayed. To get the registration information, select **Show registration info** and hit **Enter**. If your machine has a graphical user interface and a web browser installed, you can use the **Register the machine** button. This opens your default browser and starts the backup console registration process.
2\. You will see a **Registration link** and a **Registration code**. Use the **Registration Code** to register a machine in the **Backup Service Console**.
3\. To register a machine in the **Backup Service Console** devices, go to **DEVICES** > **Add** > **REGISTRATION VIA CODE**. Click **REGISTER**.
{% endstep %}
{% endstepper %}
{% hint style="success" %}
**Result:** The **Backup Agent** is now installed and registered in the **Backup Service Console** devices. Part of the registration process is also to select a backup plan for the new machine.
{% endhint %}
## Unattended installation
The installation of Acronis Backup Agent, for which you do not need to select options or provide input for each step, you can use either of the following methods:
* Using token
* Using backup unit credentials
{% stepper %}
{% step %}
### Generate a registration token
For unattended installation using a token, you must generate a token first.
1\. In the **Backup** window, go to **DEVICES** and click **+Add**.
2\. Scroll down to **REGISTRATION TOKEN** > **GENERATE**.
{% endstep %}
{% step %}
### Run the installation command
Run the following command:
```bash
./name_of_agent.bin -a --rain="https://backup.ionos.com" --token=XXXX-XXXX-XXXX
```
{% hint style="success" %}
**Result:** The installation is completed using the token and without being prompted for more information.
{% endhint %}
Alternatively, for unattended installation using backup unit credentials, run the following command:
`./name_of_agent.bin -a --rain="https://backup.ionos.com" --login=contractnumber-backupunitname --password=xxxxx`
{% endstep %}
{% step %}
### Verify the agent is running
This step is optional.
```bash
systemctl status acronis_mms
```
The service shows `active (running)` when running correctly.
{% endstep %}
{% endstepper %}
{% hint style="success" %}
**Result:** The installation is successfully completed using the backup unit credentials and without being prompted for more information.
{% endhint %}
## Troubleshooting
### Failed to install required header package from Cyber Protection Agent Packages
The installer fails if the header files package for your kernel version is not available in your distribution's repositories.
To fix this, exit the installer, update your kernel to a version with an available header package from your distribution's repository, and restart with the new kernel. Then start the installer again. For more information, see [Prepare for installation: kernel header](#prepare-for-installation-kernel-header).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ionos.com/cloud/backup-and-storage/backup-service/how-tos/install-acronis-backup-agent.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.