Creating a vSAN Data Protection Group gives below error
Error reported in vCenter Client: "Create protection group task failed. Check the vSAN data protection UI logs for details"
Logs at VMware Snapshot Service appliance:
snap-service.log:
{"level":"info","timestamp":"202#-0#-10T19:21:01.883Z","C":"cluster_db/cluster_db.go:140","message":"Creating snapstore DB namespace","opID":"68c1cb29","cluster ":"domain-c#","filename ":"snapstoreDB"}
{"level":"error","timestamp":"202#-0#-10T19:21:01.949Z","C":"vcenter/file_manager.go:47","message":"Failed to create directory","opID":"68c1cb29","filename":"snapstoreDB","error":"ServerFaultCode: Cannot complete file creation operation.","S":"gitlab.eng.vmware.com/core-build/vsan_snapshot_service/pkg/server/vsphere/vcenter.Vcenter.CreateNamespaceDirectory\n\t/build/mts/rel
snap-service-ui.log
{"level":"info","timestamp":"202#-0#-10T19:21:03.515Z","C":"controller/LogsImpl.go:46","message":"WARN: [\"[MonitorTask]: task error: undefined\"]"}
{"level":"error","timestamp":"202#-0#-10T19:21:03.516Z","C":"controller/LogsImpl.go:48","message":"[\"[vSAN SM ERROR]: \",\"Create protection group task failed. Check the vSAN data protection UI logs for details.\"]","error":"UI error","S":"gitlab.eng.vmware.com/core-
Note: You can also run "vm-support" on "VMware Snapshot Service appliance" to collect log bundle for the vSAN Data protection appliance.
Logs at vCenter:
vpxd.log:
202#-0#-10T19:21:01.936Z info vpxd[27082] [Originator@6876 sub=vmomi.soapStub[27011] opID=snapservice-68c1cb29-32] SOAP request returned HTTP failure; <<io_obj p:0x00007f99f0119348, h:59, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-58100/vpxa>, method: CreateDirectory; code: 500(Internal Server Error); fault: (vim.fault.CannotCreateFile) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "vob.vsanprovider.object.creation.failed",
--> arg = <unset>,
--> message = "Failed to create object."
--> },
--> (vmodl.LocalizableMessage) {
--> key = "vob.vsan.clomd.policy.invalid",
--> arg = <unset>,
--> message = "Invalid vSAN policy specified."
--> }
--> ],
--> file = "snapstoreDB (Cannot Create File)"
--> msg = "Received SOAP response fault from [<<io_obj p:0x00007f99f0119348, h:59, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-58100/vpxa>]: CreateDirectory
--> Received SOAP response fault from [<<io_obj p:0x000000ec2af26460, h:29, <TCP '127.0.0.1 : 16034'>, <TCP '127.0.0.1 : 8307'>>, /sdk>]: CreateDirectory
--> Cannot complete file creation operation."
--> }
Logs at ESXi:
clomd.log:
The error says the policy is invalid
--> (vmodl.LocalizableMessage) {
--> key = "vob.vsan.clomd.policy.invalid",
--> arg = <unset>,
--> message = "Invalid vSAN policy specified."
--> }
It is invalid because they have dedupe and compression enabled in the policy.
2025-09-10T19:21:01.920Z No(29) clomd[2099319]: [Originator@6876] CLOMLogConfigurationPolicy: Object size 273804165120 bytes with policy: (("stripeWidth" i1) ("cacheReservation" i0) ("proportionalCapacity" (i0 i100)) ("hostFailuresToTolerate" i1) ("forceProvisioning" i0) ("spbmProfileId" "a5ce23aa-bc1d-4159-8825-be6fcb4a0843") ("spbmProfileGenerationNumber" l+1) ("storageType" "Allflash") ("replicaPreference" "Capacity") ("iopsLimit" i0) ("checksumDisabled" i0) ("spbmProfileName" "READING - Optimal Datastore Default Policy - RAID5") ("datastoreSpaceEfficiency" "DedupAndCompression") ("dataAtRestEncryption" i0))
2025-09-10T19:21:01.920Z No(29) clomd[2099319]: [Originator@6876 opID=1804289442] CLOMProcessWorkItem: Op PLACEMENT starts:1804289442
2025-09-10T19:21:01.921Z Cr(26) clomd[2099319]: [Originator@6876 opID=1804289442] CLOMValidateAndUpdateTargetPolicy: Dedup policy is not supported on vSAN2 cluster
2025-09-10T19:21:01.921Z Cr(26) clomd[2099319]: [Originator@6876 opID=1804289442] CLOMConfigPreFlight: Failed to validate the target policy! Bad parameter
2025-09-10T19:21:01.921Z Cr(26) clomd[2099319]: [Originator@6876 opID=1804289442] CLOMGenerateNewConfig: Object placement pre-flight failed
2025-09-10T19:21:01.921Z Cr(26) clomd[2099319]: [Originator@6876 opID=1804289442] CLOM_Diagnose: Invalid vSAN policy specified.
2025-09-10T19:21:01.921Z Cr(26) clomd[2099319]: [Originator@6876 opID=1804289442] CLOMProcessWorkItem: Failed to generate configuration: Bad parameter
The creation of vSAN Data Protection Group failed because the "vm storage policy" assigned to the VM has "DedupAndCompression" which is not supported in vSAN ESA
Refer : Unable to create Deduplication and Compression policies on ESA datastore
Assign a policy to the VM that does not have "DedupAndCompression" enabled and try to re-create the vSAN Data Protection Group again for the VM.