Failure to Synchronize Snapshot - VCenter

[lloydz]

We just upgraded our vCenter install from 6.7 to 7.  In the process, vCenter has created vCLS virtual machines that assist with HA within our cluster.  There is one particular VM that is throwing an error every time our Nimble appliance tries to perform a snapshot.  The error is below:

 Failed to create vCenter snapshot associated with volume collection VMware schedule Schedule-new for virtual machine vCLS-c4abb9f3-edf6-4499-9d4c-1892a8d1fbec because administrator@vsphere.local does not have permission to perform the operation. Configure user with the proper permissions or log in as a user with such permissions.

Is there a way to exclude that VM from the snapshot?  It's not happening on any other of the vCLS VMs, oddly enough.

[support_s]

System recommended content:

1. VMware vCenter 5.x - Support Guides | VMware ESXi 5.5 U3 - Error "Path Redundancy to Storage Device Degraded"

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[mamatadesaiNim]

Great question.  Try the steps from this blog.  We added this feature a while back.

https://community.hpe.com/t5/around-the-storage-block/excluding-vms-from-vmware-application-synchronized-snapshots/ba-p/7020001#.YyyQzi-B1pQ

[Mahesh202]

Hi lloydz

• Please edit the Volume Collection and enter a user name and password that has appropriate permissions to create and delete vCenter snapshots (On virtual machines) and then save the changes.
• Alternatively to changing the user, you could grant the proper permissions to the configured user:
  • Privileges required for VMware sync-snapshots:
    1. “VirtualMachine.State.CreateSnapshot”
    2. “VirtualMachine.State.RemoveSnapshot”

When you run the “Validate” operation on a vCenter-sync snapshot integrated volume collection, each VM contained within a volume associated with the volume collection will be checked for the above permissions.

hope this helps.!!

Regards
Mahesh

[DShoemaker]

Hi Lloydz,

We are experiencing the same trouble. Did any of the recommendations in the post work for you?
Cheers,

DShoemaker

[lloydz]

Yes - creating the tag category and assigning those VMs to the tag resolved our issue.