You have the option of converting clusters to use a new host type, if the original host type you selected no longer meets your needs.
- You can convert clusters containing i3 hosts to i3en or i4i hosts.
- You can convert clusters containing i3en hosts to i4i hosts.
Contact your VMware representative to schedule a cluster conversion. A conversion window is scheduled and you will have the opportunity to approve the conversion window.
You receive notifications when a cluster conversion is scheduled, about to start, and completed. To ensure that you receive these notifications, ensure that email@example.com is added to your email allow list.
Cluster Conversion Process
Three days before the cluster conversion is scheduled, VMware will run pre-checks on the cluster to ensure that it is ready for conversion.
During the conversion, EDRS scale-in is turned off so that it does not interfere with the process. Two hosts of the target host type are added to the cluster. The NSX Edge VMs are migrated to these two new hosts. Then workload VMs are migrated off of one of the original hosts and it is removed from the cluster. The removal of original hosts and the addition of target hosts is repeated until all original hosts have been removed and the cluster is fully converted. Then EDRS scale-in is re-enabled. Based on cluster utilization, the number of final target hosts might differ from the number of hosts you started with.
- The current used capacity in the starting VSAN cluster.
- The number of hosts present in the starting cluster.
- The space-savings efficiency ratio of the starting cluster.
- The available capacity in the capacity tier of storage for the target host instances.
- An extra 20% headroom for VSAN operations and overhead.
- The estimated fault domains required in the target cluster. Currently, the estimate does not take into account the VM storage policies and estimates the required fault domains based only on the cluster size. This means that for all clusters containing seven hosts or fewer, the target cluster will contain the same number of hosts as the source cluster.
The estimate is a best guess only. The final result might differ based on the state of the cluster. After conversion, EDRS might scale in or scale out the cluster based on the resource usage and the EDRS policy applied to the cluster. You can also manually resize the cluster after conversion is complete.
Cluster conversion might take hours to days to complete. VMware recommends taking a backup before the cluster conversion takes place.
Impact of Cluster Conversion on Operation
- Removing hosts
- Editing EDRS policy settings
- Do not perform hot or cold workload migrations to or from the cluster being converted.
- Do not perform workload provisioning (New/Clone VM).
- Do not make changes to Storage-based Policy Management settings for workload VMs.
- Avoid starting HCX migrations that might overlap with the conversion window.
- Avoid the following DRaaS activity on the cluster being converted:
- Create or destroy site pairings
- Execute recovery plan
- Planned migration
- Test failover or test cleanup
- Real failover
- Replication management operations, such as configuring or stopping replication
- Do not add or remove hosts from the cluster being converted.
Compute policy tags are not copied over during cluster conversion. You will need to attach host policy tags after conversion is complete.
Cluster Conversion and Billing
During the cluster conversion process, your cluster contains a mixture of host types. Until the cluster conversion is complete, all hosts are billed at the original host rate. After the conversion is complete, billing switches to the target host rate.
Converting the cluster host types does not convert any term commitments that you have purchased. For example, if you purchased an i3 term commitment, and later converted that cluster to use i3en hosts, you can choose to purchase a new i3en term commitment or have your i3en hosts billed at the on-demand rate. In either case, you will continue to pay for your i3 term commitment.