简单部署

在本页面

The simple deployment scenario is good for small virtual environments or the purpose of the Veeam Backup & Replication evaluation. In this scenario, Veeam Backup & Replication is installed on a single Windows-based machine.

Important

You must not install Veeam Backup & Replication directly on a Hyper-V host. Such installation may lead to unpredictable system behavior. Instead, install Veeam Backup & Replication on a VM on the host.

The machine where Veeam Backup & Replication is installed performs the following roles:

Backup server that coordinates all jobs, controls their scheduling and performs other administrative activities.
Default backup repository where backup files are stored. During installation, Veeam Backup & Replication checks volumes of the machine on which you install the product and identifies a volume with the greatest amount of free disk space. On this volume, Veeam Backup & Replication creates the Backup folder that is used as the default backup repository.
Mount server that is needed for restoring of VM guest OS files.
Guest interaction proxy that is needed for application-aware processing, guest file system indexing and transaction log processing.

The role of the default backup proxy is assigned to the source Hyper-V server. It handles job processing and transfers backup traffic directly to the target server. All services necessary for the backup proxy are installed directly on the source Hyper-V server.

Simple Deployment

Veeam Backup & Replication is ready for use right after the installation. The only thing you must do is add Microsoft Hyper-V servers that you plan to use as source and target for backup, replication and other activities. For details, see Adding Microsoft Hyper-V Servers.

In Hyper-V environments that require a large number of backup or replication activities to be performed, the simple deployment scheme is not appropriate due to the following reasons:

The backup server might not have enough disk capacity to store the required amount of backup data.
A significant load is placed on production servers that combine the roles of backup proxies and source hosts.

To take the overhead off the backup server and source Hyper-V servers, you can use the advanced deployment scenario. For details, see Advanced Deployment.