When attempting to restore a Virtual Machine using Commvault backup into a VxRail 2-Node + Witness vSAN cluster, the restore operation fails. Restores to non-VxRail clusters within the same vCenter succeed.
In the vSphere client, you may see generic "Failed to create object" errors.
vSAN OSA 8.0U3
This issue occurs when the Virtual Machine Storage Policy assigned during creation or restoration requests more local hardware resources than the vSAN Original Storage Architecture (OSA) hosts possess.
In a 2-node cluster environment, the top-level Site disaster tolerance rule of "Host mirroring - 2 node cluster" is correct and necessary to ensure a full mirror of data exists across the hosts.
The failure is caused by the secondary Failures to tolerate rule being set to 1 (local RAID 1). Attempting to build an additional, local RAID 1 tree on a single node requires a minimum of 3 Disk Groups per host in a vSAN OSA environment. Because the hosts in the cluster possess fewer than 3 Disk Groups, the policy cannot be satisfied, resulting in placement failures.
Review the clomd.log on the ESXi hosts during the restore attempt. You will find entries similar to the following:
2026-05-25T20:16:47.364Z Cr(26) clomd[3353360]: [Originator@6876 opID=1804290611] CLOM_CheckClusterResourcesForPolicy: 1 DG(s) available in certain fault domains, needed at least 3 DG(s) in all the upper fault domains2026-05-25T20:16:47.365Z Er(27) clomd[3353360]: [Originator@6876 opID=1804290611] CLOM_Diagnose: 1 or more fault domains have 1 DG(s) in them. The operation requires at least 3 DG(s) in all fault domains except witness fault domain.
To resolve this issue and adhere to best practices for a 2-node vSAN cluster ( with less than 3 disk groups each ) , modify the Storage Policy so that it enforces cross-site mirroring without demanding unsupported local redundancy.
1. Log in to the vSphere Client.2. Navigate to Policies and Profiles > VM Storage Policies.3. Edit the `vSAN Default Storage Policy` (or the specific custom policy being used by the backup software).4. Navigate to the vSAN rules tab.5. Under Site disaster tolerance, select Host mirroring - 2 node cluster.6. Under Failures to tolerate, select No data redundancy.7. Save the policy.