This is working as per design, upon creating a virtual machine snapshot, separate Virtual SAN objects are created The newly created objects will store the new writes (new content) for each object (delta disk.)
The benefit of this approach is specific for the delta disks in VIEW environment (For example, for each linked clone in Horizon View) may have a different policy than that of the base disk, as the requirements and workload for each are different
The user should consolidate snapshots and change the policy on the Virtual Machine unless otherwise specified for a specific reason.
Workaround:
- A virtual machine should not be running on snapshot as the snapshot are only for temporary periods and point-in-time copies of data. The sole purpose of the snapshot is to enable the Administrator to revert back changes in case it does not bring desirable results after applying them (ex. Taking a snapshot of VM before applying a patch inside the guest OS)
- It is very important to consolidate or delete all snapshots before you make changes in the Storage policy for objects located on a vSAN cluster (VM, VM DISK, Namespace etc - SPBM policy)