This article explains how to correctly configure Automation Central jobs to delete old snapshots while excluding specific Virtual Machines (VMs) using filter criteria. Incorrect filter configuration is the most common cause for unexpected snapshot deletion or job failure.
x day old snapshots is not working correctly. 'Snapshot Retention' with tag value='Snapshot Retention''Snapshot Retention' The "Preview Scope" returns no Virtual Machines (VMs) because the exclusion filter logic (does not contain) fails to evaluate assets that lack the specified tag category completely.
The /storage/log/vcops/log/analytics-[uuid].log contains entries like
[com.vmware.vcops.analytics.action.schedule.ActionScheduler.launchAction] - There are no VMs to run under the custom job
ACTION_NEVER_STARTED
There are no vms with reclaimable snapshot
The filter evaluation logic inside the criteria sets handles missing properties incorrectly, leading to unexpected asset exclusion.
Use the Preview Scope button to verify the Filter Criteria is defined correctly. The Scope will provide each VM that will be affected by the Reclaim Job. Any additional criteria will filter additional VM's into the scope of the Reclaim Job.
Example: Delete aged snapshots unless the VM has a tag category of snapshot-no-delete
Example: Delete aged snapshots unless the VM does not have a tag value of snapshot-no-delete in the tag category called lifecycle
Example: Delete snapshots older than 3 days on all VMs that do not have the Snapshot Retention or Snapshots tag categories