Named disks are standalone virtual disks that you create in Organization VDCs. Organization administrators and users who have the respective rights can create, remove, and update named disks, and connect them to virtual machines.

When you create a named disk, it is associated with an Organization VDC but not with a virtual machine. After you create the disk in a VDC, the disk owner or an administrator can attach it to any virtual machine deployed in the VDC. If you have the Create a Shared Disk right, you can create a shared named disk that you can attach to multiple VMs. The disk owner can also modify the disk properties, detach it from a virtual machine, and remove it from the VDC. System administrators and organization administrators have the same rights to use and modify the disk as the disk owner.

Note: Although vSphere supports configurations like Windows Server Failover Cluster (WSFC) and you can create a shared disk through physical SCSI bus sharing, VMware Cloud Director 10.2 does not support this feature. When creating a shared disk in VMware Cloud Director, you only create an underlying independent persistent disk in vSphere with multiwriter mode enabled.

If you attach a named disk, you cannot take VM snapshots. If a shared disk is attached to a VM, you cannot edit its hard disk setting from the VM details view.

If the organization VDC has a storage policy with enabled VM encryption, you can encrypt VMs and disks by associating them with storage policies that have the VM Encryption capability. See Virtual Machine Encryption.