Veeam Backup & Replication infrastructure comprises a set of components needed to perform data protection and disaster recovery tasks. The backup infrastructure that we will use for evaluation includes the following components:
- Veeam backup server: a physical or virtual machine running Veeam Backup & Replication. The Veeam backup server performs the role of the main management component: it is the configuration and control center of the backup infrastructure.
- Virtual infrastructure servers: ESX(i) hosts used as the source and the target for backup and replication.
- Backup proxy: a 'data mover' component that retrieves VM data from the source storage, processes it and transfers to the destination.
- Backup repository: a location used to store backup files and auxiliary replica files.
To perform evaluation exercises, you can use a simple deployment scenario or a distributed deployment scenario (recommended). The choice depends on your test lab environment. If you have a very small test lab and there is no possibility to allocate dedicated servers that will perform the roles of a backup proxy and backup repository, you can use a simple deployment scenario to evaluate the product. However, whenever possible, it is recommended that you use a distributed deployment scenario. This will help you gain insight into the architecture of the backup infrastructure, evaluate its benefits and increase your experience in deploying backup infrastructure components.
In a simple deployment scenario, you will need three components:
- Veeam backup server
- Source ESX(i) host
- Target ESX(i) host (used for a replication scenario)
The Veeam backup server performs three roles:
- It is the 'control center' of the backup infrastructure, coordinating job performance and other administrative activities.
- It is the default backup proxy. When you perform backup or replication, VM data is processed directly on the Veeam backup server and then moved to the target. All services necessary for backup proxy functioning are installed locally on the Veeam backup server.
- It is the default backup repository: all backups and auxiliary replica files are stored on the Veeam backup server, in the Backup folder on the volume with the greatest amount of free disk space.
In the distributed deployment scenario, Veeam backup server, backup proxy and backup repository roles are assigned to three different servers. This type of deployment enables efficient data transfer and use of resources in the backup infrastructure because you move the data processing load from the Veeam backup server to a dedicated backup proxy and store data to a dedicated backup repository.
Depending on your production environment and the backup and replication scenarios you plan to use, the distributed backup infrastructure may include multiple dedicated backup proxies and backup repositories, both onsite and offsite, controlled by a single Veeam backup server. Use of multiple backup proxies and repositories allows for dynamic assignment of jobs and intelligent load balancing across the backup infrastructure.
To follow evaluation scenarios in this guide, it is sufficient to deploy one backup proxy and one backup repository locally in your test lab. The backup infrastructure will include the following components:
- Veeam backup server
- Backup proxy
- Backup repository
- Source and target ESX(i) hosts
To deploy Veeam backup infrastructure, perform the following exercises.
Install Veeam Backup & Replication on a physical or virtual machine.
In the Veeam Backup & Replication console, connect hosts that you want to use as the source and the target for backup and replication.
In the Veeam Backup & Replication console, connect a server that you want to use as a backup proxy, and assign the role of the backup proxy to it. This exercise must be performed only if you decide to follow the distributed deployment scenario.
In the Veeam Backup & Replication console, connect a server or that you want to use as a backup repository, and assign the role of a backup repository to it. This exercise must be performed only if you decide to follow the distributed deployment scenario.