The VM scheduling policy supports the configuration of mutual exclusion or aggregation policies for multiple virtual machines and clusters. Through the scheduling policy, the running location of the virtual machine can be precisely controlled to meet the needs of virtual machine business tuning.

Precautions:

1. The running virtual machine does not support modifying the Running Location configuration.
2. After the scheduling policy is created on the running virtual machine, the virtual machine needs to restart to take effect.
3. Supports configuring boot orders for VMs when SCP 6.10.0 is connected to HCI 6.10.0 and higher.

There are 4 VM scheduling types:

• VM-VM Affinity:

Function Description:

Aggregated VM allows multiple VM to be bound and run on a physical node. For example, VM with frequent business visits or virtual machine in the same business group is bound to the same server to improve business access performance.

Precautions:

1. The running virtual machine does not support modifying the Running Location configuration.
2. After the scheduling policy is created on the running virtual machine, the virtual machine needs to restart to take effect.
3. Supports configuring boot orders for VMs when SCP 6.10.0 is connected to HCI 6.10.0 and higher.

• VM-VM Anti-Affinity:

Mutually exclusive virtual machines run the selected virtual machine on different physical nodes. For example, cluster systems such as Oracle RAC are mutually exclusive on different physical servers to ensure business reliability.

Precautions:

1. The running virtual machine does not support modifying the Running Location configuration.
2. After the scheduling policy is created on the running virtual machine, the virtual machine needs to restart to take effect.

• VM Group Anti-Affinity:

Virtual machine group mutual exclusion supports running multiple selected VM groups on different physical nodes. For example, suppose the three VM of business A and the three VM of business B are configured to be mutually exclusive in VM groups when the physical node running business A fails. In that case, business B will not be affected, improving business availability.

Precautions:

1. The run location must be configured in the same fault domain or automatically selected for the same virtual machine group.
2. The running virtual machine does not support modifying the Running Location configuration.
3. After the scheduling policy is created on the running virtual machine, you need to restart the virtual machine for it to take effect.
4. The virtual machine in the same virtual machine group will not be aggregated by default, and the aggregation policy needs to be manually configured.

• VM-Host Affinity:

VM group to host group supports running selected virtual machine groups on different physical host groups. For example, run service group A of the active-active service in the main fault domain of the extended cluster and run service group B of the active-active service in the standby fault domain of the extended cluster. It is to ensure that data and services are active-active simultaneously.

Precautions:

1. For the same VM group, the operating location must be configured in the same fault domain or automatically selected.
2. The running VM does not support modifying the Running Location configuration.
3. After the scheduling policy is created on the running VM, you need to restart VM for it to take effect.
4. A stretched cluster group hosts in the same fault domain into the same host group by default.