Before you add a new hardware plan, check the following prerequisites:
- A TLS certificate must be installed on the SP Veeam backup server.
- Virtualization hosts that will provide resources to tenants through a hardware plan must be added to the backup infrastructure.
- 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 to configure hardware plans for different virtualization environments:
- The New VMware Hardware Plan wizard — to configure a VMware hardware plan.
- The New Hyper-V Hardware Plan wizard — to configure a Hyper-V hardware plan.
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.
- 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 apply to standalone ESX(i) hosts managed by vCenter Server.
Before you add a new Hyper-V hardware plan, consider the following limitations:
- Standalone Hyper-V hosts that run Nano Server installations of the Microsoft Windows Server 2016 OS cannot be used for configuring hardware plans.
- The following types of Hyper-V clusters are not supported for exposing resources through hardware plans:
- Clusters with server nodes that run Nano Server installations of the Microsoft Windows Server 2016 OS
- Clusters with the Cluster Operating System Rolling Upgrade feature enabled
- Multi-domain and Workgroup Clusters
- After you subscribe 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.
- Usage of a Microsoft SMB3 shared folder as a storage for VM replicas is not supported in the Veeam Cloud Connect infrastructure.