vSAN File Share object in a state of Non-availability related incompliance.

Products

• VMware vSAN

Issue/Introduction

The FSVM_Profile_DO_NOT_MODIFY Storage Policy is automatically applied to the vSAN File Service VMs but should not be used for anything else including the vSAN File Shares themselves.

A vSAN File Share object can get into a state of Non-availability related incompliance due to the FSVM_Profile_DO_NOT_MODIFY Storage Policy being mistakenly applied originally and subsequently another valid Storage Policy attempt being applied to it.

 

Environment

vSAN File Services

Cause

This Non-Compliance of the Storage Policy can arise if the owner host of the vSAN File Share object is different to the host where it's Components are pinned to.

Even if the Storage Policy is Compliant, due to the FTT=0 and Host Local Affinity rules contained in the policy, the vSAN File Share data will have no redundancy and the Data will be pinned to a vSAN diskgroup / storagepool on a particular host.

It is not possible to re-apply another Storage Policy to vSAN objects that have been created using this Storage Policy as when trying to do so it will fail and the following can be observed in the clomd.log:

CLOM_Diagnose: Host locality policy is only allowed for new object creation and cannot be changed later

Resolution

Need to copy the Data off all vSAN File Shares with the FSVM_Profile_DO_NOT_MODIFY Storage Policy applied, create new vSAN File Shares with a valid Storage Policy and import the data from the old vSAN File Shares prior to deleting them.