Before You Begin

Before you add a new hardware plan, check the following prerequisites:

1. An SSL certificate must be installed on the SP Veeam backup server.
2. Virtualization hosts that will provide resources to tenants through a hardware plan must be added to the backup infrastructure.
3. The process of configuring a hardware plan differs depending on virtualization environment — VMware vSphere or Microsoft Hyper-V. As a result, separate wizards are used for configuring hardware plans for different virtualization environments:

• The New VMware Hardware Plan wizard — for configuring VMware hardware plans.
• The New Hyper-V Hardware Plan wizard — for configuring Hyper-V hardware plans.

The description of a hardware plan setup process is illustrated primarily with the figures from the New VMware Hardware Plan wizard. However, all the described steps except for those specified, are the same for configuring both VMware and Hyper-V hardware plans.

4. It is recommended that you plan network resources in advance and configure a range of VLANs that will be reserved for Veeam Cloud Connect Replication before configuring a hardware plan. To learn more, see Managing VLANs.

Limitations for VMware Hardware Plans

To configure a VMware hardware plan that will use resources of a vCenter Server cluster, you must use the Enterprise or Enterprise Plus edition of the VMware vSphere infrastructure. Standard VMware vSphere edition does not support creating resource pools in clusters. This limitation does not appeal to standalone ESX(i) hosts managed by vCenter Server.

Limitations for Hyper-V Hardware Plans

Before you add a new Hyper-V hardware plan, check the following prerequisites:

• In Veeam Backup & Replication prior to version 9 Update 2, SCVMM is not supported for hardware plans. Hosts and clusters whose resources you want to expose to tenants must be added to the list of managed servers individually as standalone Hyper-V servers and Hyper-V clusters.
• After subscribing a tenant to a Hyper-V hardware plan, you cannot rename the virtual switch in Microsoft Hyper-V infrastructure that is used by VM replicas. If you rename the virtual switch, replication jobs targeted at the cloud host that use the renamed virtual switch will fail.