> 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/backup-service-faqs.md).
# FAQ
Answers to common questions about IONOS CLOUD Backup Service setup, backup and recovery, data security, pricing, and troubleshooting
## General
### What is the reason for renaming "Managed Backup" to "Backup Service"?
The **Managed Backup** name is changed to **Backup Service** to standardize our product terminology. Previously, it was referred to as **Managed Backup**, **Backup as a Service**, or **Backup by Acronis** across different platforms. This new unified name ensures consistency in our communications and branding, service catalog and price list.
* In the [DCD](/cloud/set-up-ionos-cloud/get-started/log-in-dcd.md), the product resides within **Backup & Storage** > **Backup Service** (previously named as **Backups**).
* In the [price list](https://docs.ionos.com/cloud/support/general-information/price-list), the name changed from **Backup as a Service** to **Backup Service**.
* In the [service catalog](https://docs.ionos.com/cloud/support/general-information/service-catalog), the product is renamed from **IONOS CLOUD Backup** to **Backup Service**.
* Metering descriptions in the billing API call that returns a [list of available products](https://api.ionos.com/docs/billing/v3/#tag/products/paths/~1%7Bcontract%7D~1products/get) stay intact. For example, **30d per 1GB Backup Storage for Win. or Linux Server Backup**.
* In the [Cloud API v6](https://api.ionos.com/docs/cloud/v6/), the product is renamed from **Backup units** to **Backup Service**.
Rest assured, the service itself remains unchanged.
## Setup and configuration
### What firewall configurations are needed for effective backup agent communication?
Ensure that the following firewall rules are configured to allow the backup agent to communicate effectively:
| **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. |
### How do I create snapshots or backups of my storage?
You can create snapshots or backups of your storage within the Data Center Designer. For more information, see [Create a Snapshot](/cloud/backup-and-storage/images-snapshots/snapshots/how-tos/create-snapshot.md) within the DCD.
## Infrastructure and availability
### What is the availability of IONOS CLOUD data centers?
The availability of our data centers is 99.95%. The maximum number of maintenance hours is four in three months.
### How is my virtual data center protected against hardware failures?
Our entire storage system ensures maximum redundancy for all hardware components. All storage volumes are replicated synchronously on additional storage servers, which are physically located in separate fire zones of the same modular data center. Additionally, all communication connections and devices are implemented with a minimum of single redundancy protection. In the event of a physical failure of a server with a VM, the VM restarts on another physical server.
### What is the best way to protect data and improve performance with RAID?
Reliable performance and security are ensured, to a large extent, by storing the data in duplicate, meaning in two separate zones of the data center. Reliability and security improve only marginally when mirroring mass storage devices, such as RAID 1.
Striping with RAID 0, or using RAID 5 to boost speed and reliability, would also have hardly any effect; the same holds true for DRBD storage systems.
{% hint style="info" %}
**Note:** We do not recommend striping as it interferes with additional security measures that we apply to ensure data integrity over parallel storage blocks. To enhance the integrity of your data, consider using the ZFS file system.
{% endhint %}
## Backup and recovery
### What compression ratio can be achieved for backups?
Our Backup Service saves data in a proprietary format using compression to reduce storage space. This applies to both Windows and Linux systems.
You can choose the compression level for a backup in Backup options.The compression levels are:
* **None:** Data is copied without any compression, significantly increasing the backup file size, especially with sector-by-sector backup.
* **Normal:** The recommended data compression level (default setting).
* **High:** More compression than normal, which takes more time to create a backup.
* **Maximum:** Maximum compression, but takes the longest time to create a backup.
At the normal compression level, backup sizes are typically reduced by 40–50%. Using high or maximum compression can reduce the size by an additional 3–5%.
{% hint style="info" %}
**Note:** The actual compression ratio depends on the file types stored in the backup. Files already compressed, such as .jpg, .pdf, or .mp3, will see minimal reduction in size. In contrast, formats like .doc or .xls compress well.
{% endhint %}
### What is the difference between Backup Storage, Object Storage, and Network File Storage as a backup target?
You can select the backup storage target per backup plan in the **Backup Service Console**:
* **Backup Storage:** Default target. Used automatically for backup data from any source; no setup required.
* **Object Storage:** Must be defined as a storage location before use in a backup plan.
* **Network File Storage:** Must be defined as a storage location before use in a backup plan; may require additional access configuration for the NFS share.
## Data security
### What happens if I forget my backup encryption password?
You can encrypt each backup plan with a password, which is converted into an AES-256 encryption key. Because neither Acronis nor space.vars.ionos\_cloud stores this password, there is no recovery process; if you lose it, your encrypted backups are permanently irretrievable. For the same reason, a password is also required to download and decrypt each backup using the Acronis Data Export.
## Pricing and packs
### What is the difference between the standard Backup Service and Advanced Packs, and how am I billed?
The core Backup Service covers most protection needs at no additional fee. Activating **Advanced Packs** such as Advanced Security, Advanced Management, or Direct Backup to Public Cloud adds features such as antimalware protection, patch management, and backup to an external cloud storage target.
If you activate at least one feature from an Advanced pack, you are billed for that pack for each workload (a virtual machine, server, or workstation) it is applied to. For more information, see [Advanced Packs](/cloud/backup-and-storage/backup-service/overview/advanced-packs.md) and [Prices](https://docs.ionos.com/cloud/support/general-information/price-list).
### What changed with the January 2026 Acronis Cyber Protect migration?
With the Acronis Cyber Protect release on January 22, 2026, most features previously included in the **Advanced Backup** pack were migrated into the standard Backup Service at no extra charge. This includes one-click recovery, continuous data protection, and backup support for Microsoft SQL, MariaDB, MySQL, Oracle DB, and SAP HANA, among others.
If your backup plan used any of these migrated features and was created before January 22, 2026, nothing changes; it continues to work exactly as before. The Advanced Backup pack fee was removed from subscriptions as of that date, with the January 2026 invoice being the last to include any Advanced Backup-pack fees (prorated up to the migration date).
The cloud-storage-target use case (assigning a backup plan to **Object Storage**) was renamed from **Advanced Backup** to **Direct Backup to Public Cloud**, but pricing stays the same. It may still appear as **Advanced Backup** on your invoice for the time being. For more information, see [Advanced Packs](/cloud/backup-and-storage/backup-service/overview/advanced-packs.md).
## Troubleshooting
### Why does backup fail with "The SnapAPI kernel module is not loaded"?
The Acronis backup agent relies on two kernel modules, `snapapi` and `file_protector`, to create consistent snapshots of your data. These modules are compiled from source at installation time using Dynamic Kernel Module Support (DKMS), which requires the kernel header files for your running kernel version to be present on the system.
If the backup agent worked previously and stopped after a system update, a new kernel was likely installed. When a new kernel is installed, DKMS automatically rebuilds modules like `snapapi` and `file_protector`, but only if the matching kernel headers package is present on the system.
The Acronis agent installer resolves all dependencies, including kernel headers, at installation time. After a kernel update, you have two options to restore the modules:
**Option A: Install headers for the new kernel only:** Install the headers package for the specific kernel version now running, then trigger the DKMS rebuild manually.
**Option B: Install the kernel headers meta-package (recommended):** Install the meta-package, which always tracks the same version as the kernel meta-package. Future kernel updates through `apt upgrade` automatically pull in the new headers, and DKMS rebuilds the modules without manual intervention.
Once the correct headers are installed, trigger the DKMS rebuild with:
```bash
dkms autoinstall
```
For detailed instructions to check header availability and installing them, see [Prepare for installation: kernel header](/cloud/backup-and-storage/backup-service/how-tos/install-acronis-backup-agent.md#prepare-for-installation-kernel-header).
### Why does installation fail with "package dkms does not verify: no digest" on Ubuntu 26?
On Ubuntu 26, the Acronis backup agent installation fails with the following error:
```
package dkms-3.10.17.1-99.noarch does not verify: no digest.
```
This is a compatibility issue between Ubuntu 26 and the RPM Package Manager (RPM) packages bundled with the Acronis installer. The issue is under investigation.
{% hint style="warning" %}
**Warning:** Avoid the `--nodigest` RPM workaround on Ubuntu 26. Bypassing RPM digest verification at installation time can leave the DKMS module in an inconsistent state. This can cause a kernel panic or prevent the system from booting after the next kernel update.
{% endhint %}
The Acronis backup agent cannot be installed on Ubuntu 26 at this time. To back up a workload running on Ubuntu 26, contact [IONOS CLOUD Support](https://docs.ionos.com/cloud/support/general-information/contact-information).
---
# 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/backup-service-faqs.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.