A virtual shared disk can be accessed by a maximum of 128 VMs at the same time. VMs with a shared disk are ideal for business scenarios where clustered deployment and shared storage are required, such as Oracle RAC clusters and MySQL InnoDB clusters. Data is synced to the same disk in real time to ensure the consistency of business data in the cluster.
Use Restrictions
Common Features of VMs with Shared Disk
Feature
Supported or Not
Offline Specification Change
Yes. You can change CPU and memory specifications. To change the capacity of the shared disk, power off all associated VMs first.
Online Specification Change
Yes. You can only increase the number of CPUs and the memory size. To change shared disk specifications (including capacity and IO limit), power off the VM first.
Cold Migration (Run Location)
Yes. In a stretched datastore, all VMs associated with the shared disk must be migrated to the same fault domain.
Live Migration (Run Location)
No. Live migration is not supported for VMs mounted with virtual shared disks.
HA
Yes. The datastore where the destination node resides must be able to access the shared disk. (The source and destination nodes must be in the same virtual datastore or associated with the same external LUN.)
VM Snapshot
Yes. The VM snapshot contains only data in the VM's private disks and does not contain data in the virtual shared disk.
Cloning
Yes. You need to remount the virtual shared disk to the VMs after cloning (mounting relationships cannot be inherited).
Cross-Cluster VM Migration
No. VMs with a shared disk cannot be migrated across clusters. To migrate them to another cluster, unmount the shared disk first.
{{ $t('index.defaultHeader.chromeBrowserTip') }}