What is Veeam Backup & Replication?
Veeam Backup & Replication is Veeam's software for backing up, replicating and restoring virtual machines, physical servers, cloud workloads and applications. A backup server controls jobs and configuration, proxies read and move data, and repositories store restore points, either alone or grouped into a scale-out backup repository.
What do the core roles do?
- Backup server. Runs jobs and schedules, holds the configuration database with credentials and the restore point catalog, and is where administrators sign in. It runs on Windows or, in recent releases, as a Linux-based deployment.
- Backup proxy. Reads source data, compresses and deduplicates it, and sends it to a repository. Proxies sit close to the workloads, and there can be many.
- Backup repository. Stores backup files. It can be a Windows or Linux server, a network share, a deduplication appliance or an S3-compatible bucket.
- Helper roles. Gateway servers connect to shares and object storage, and mount servers expose restore points for file and application item restores.
Jobs write full and incremental restore points, and the backup server tracks each chain in its catalog so a restore knows which files to combine.
What is a scale-out backup repository?
A scale-out backup repository (SOBR) groups several repositories into one logical target with up to three tiers. The performance tier is made of extents, individual repositories that receive new backups. The capacity tier is object storage that receives a copy of new restore points, or older restore points moved off the performance tier. The archive tier holds long-term restore points on low-cost object storage. Jobs see one repository while data moves between tiers by policy. Object storage tiers are covered under Veeam backup to object storage.
How is a replica different from a backup?
A backup is a compressed set of files that has to be restored before use. A replica is a standby copy of a virtual machine kept ready to power on, with a short rollback history. Replicas serve disaster recovery, not long retention.
Where is the design exposed?
The backup server holds credentials for hypervisors, guests and repositories, and controls retention. Anyone who takes it over can delete restore points from the console, and the deletion looks like routine cleanup in the job log. The common exposure is joining the server to the production Active Directory domain, so a domain administrator account stolen anywhere also administers backups. Veeam's own security guidance keeps the server in a workgroup or separate management domain with multi-factor sign-in. The attack pattern is described under credential theft.
Two other items hold recovery knowledge. The configuration backup contains job definitions, repository connections and encryption passwords, and is lost with the server if stored only there. Console retention can be shortened from the console, so restore points stay protected only where the repository refuses deletion, as on a hardened Linux repository or object storage with S3 Object Lock.
Frequently asked questions
Is a Veeam replica the same as a backup?
No. A replica is a ready-to-run copy of a virtual machine with a short rollback history. A backup is compressed, restored on demand and kept for as long as retention requires.
What is the difference between the capacity tier and the archive tier?
The capacity tier holds copied or moved restore points on object storage for operational restores. The archive tier keeps long-term restore points on cheaper storage that is slower to retrieve.
Can Veeam Backup & Replication write directly to object storage?
Yes. An S3-compatible bucket can serve as a standalone repository or as an extent or tier in a scale-out backup repository.
