Requirements and Limitations
For the hardened repository, consider the following requirements and limitations.
- The role of the hardened repository can be assigned to a Linux machine with local or remotely attached block storage. The machine must meet system requirements for backup repositories. The Linux distribution must be 64-bit due to Veeam Data Mover requirements.
To reduce the attack surface, use a physical machine with local storage. For RAID configuration, recommendations are the following:
- The Linux machine file system must support immutable files and extended attributes modified by the chattr and setxattr commands. We recommend using XFS for performance and space efficiency reasons (block cloning support).
- As the hardened repository requires the block storage, you cannot use the following storage types:
- NFS share or a Linux machine with the mounted NFS volume
- A Linux machine with the mounted SMB (CIFS) volume
- You must add the Linux machine to the Veeam Backup & Replication console as a managed server. The hardened repository cannot be shared between different Veeam Backup & Replication servers.
- The Linux machine should have redundant network connection.
- To store backup files in a repository, use only a forward incremental backup method with enabled active full backup or synthetic full backup. Once a backup file becomes immutable, it can be merged or deleted only when the immutability time period expires. For this reason, you cannot select a reverse or a forever forward incremental backup method.
- For importing a backup, use VBK backup files. Metadata files of a backup chain (.VBM) cannot be immutable because they are updated on every job pass.
- Hardened repositories do not support rotated drives. For more information about rotated drives, see this section.
- To use the immutability feature for backup copy jobs, enable the GFS retention policy. For more information, see Long-Term Retention Policy (GFS).
- Do not use the immutability feature for a Nutanix Mine infrastructure. As Mine repositories contain thin-provisioned disks, there may be the case when Veeam Backup & Replication uses full storage capacity of a repository and cannot delete backup files from the file system.