What is a Veeam Hardened Repository?
A Veeam Hardened Repository is a Linux server that stores Veeam backups as files locked against change or deletion for a set period, enforced by the Linux filesystem. Veeam deploys it with single-use credentials it does not keep, so a stolen backup console login cannot unlock the files. Root access and the system clock still can.
How do single-use credentials work?
When the repository is added, Veeam connects to the Linux server once with an account's credentials to install its components, then discards them. They are not saved in the backup server's configuration database. From then on the backup server reaches the repository only through Veeam's own transport service installed there, not through a stored login.
The result is that no reusable password for the repository sits on the backup server. An attacker who takes over the backup console gains no account that can sign in to the Linux server and lift the locks. Veeam's guidance is to remove the deployment account's elevated rights once setup is complete, so that account cannot lift the locks either.
How is the lock applied?
- Backups are written to the repository as files.
- Each backup file is marked immutable with a Linux file attribute for the period set when the repository was added.
- Until that period ends, the files cannot be changed, moved or deleted by any process, Veeam included. They can still be read and copied.
- When the period passes, Veeam's own retention removes files that are no longer needed.
Because the lock lives in the filesystem of a separate machine, it is a route to an immutable backup that does not depend on a console setting.
What can still open the lock?
- Root. A user with root on the Linux server can remove the attribute and delete the files. A reused root password, an open SSH service or a server joined to the production domain makes that route easier.
- The hypervisor. On a virtual machine, a hypervisor administrator can delete or copy the virtual disk beneath the guest. A physical server removes that route, which is why Veeam's documentation prefers physical hardware.
- The clock. The lock expires by comparing the current time to a date. An attacker who moves the server's clock forward makes the period appear to end early.
Which operating conditions keep the lock intact?
The lock is only as strong as the way the server is run. Hardened deployments share a short set of conditions: SSH disabled after deployment, a unique root password held offline, no membership of the production domain, management interfaces on an isolated network, regular operating system patching, and time taken from a source that attackers on the production network cannot alter. Each condition shrinks the administrative blast radius, the number of accounts that can reach the files.
How does object storage lock differently?
Object storage uses a different lock. Veeam requests retention dates through the S3 interface, and the storage enforces them with S3 Object Lock. In compliance mode no account on the storage, administrators included, can shorten a lock before its date. The hardened repository depends on hardening one Linux server, while object lock moves enforcement into the storage platform. Veeam Backup & Replication supports both as repository types.
Frequently asked questions
Can a hardened repository be a virtual machine?
It can, but the hypervisor then becomes part of the trust boundary. An attacker with hypervisor access can bypass the file lock by acting on the virtual disk. Physical servers avoid that.
Can immutable files on a hardened repository still be read?
Yes. Immutability blocks change and deletion, not reading or copying, so access control and encryption are still needed.
Is a hardened repository the same as an air gap?
No. It is locked but remains online and reachable over the network. An air gap removes the network path, fully or logically.
