A NetBackup VMware policy backup fails with Status Code 4292

Problem

A VMware policy backup fails with Status Code 4292

Error Message

Job Details:

Info bpbrm (pid=254714) Starting create snapshot processing
Info bpfis (pid=254746) Backup started
snapshot backup of client <VM_Name> using method VMware_v2
Info bpbrm (pid=254714) INF - vmwareLogger:  Creating snapshot for vCenter server <Vcenter_Server>, ESX host <ESX_Ser er>, BIOS UUID <UUID>, Instance UUID <UUID>, Display Name <VM_Display_Name>, Hostname <VM_Name> 
Info bpbrm (pid=254714) INF - vmwareLogger:  Connection state of virtual machine: connected.
Critical bpbrm (pid=254714) from client <VM_Name>: FTL - vSphere_freeze: Can not enable change block tracking, virtual machine has snapshots. Please remove virtual machine snapshots and retry
Critical bpbrm (pid=254714) from client <VM_Name>: FTL - snapshot processing failed, status 4292
Unable to activate change block tracking in current state of virtual machine (4292)

Cause

If a virtual machine has change block tracking (CBT) disabled and there are any existing snapshots on the virtual machine, CBT will not be enabled at the time of backups.This applies to virtual machines residing on vSphere 6.5 and above.

Solution

Please refer to the below Technote from VMware to get more information about CBT

• CBT must be enabled for the virtual machine (see below & by default it is enabled)

https://kb.vmware.com/s/article/1020128

This is a VMware limitation and is documented in VMware VDDK 6.5 Release Notes at the following URL:

https://vdc-download.vmware.com/vmwb-repository/dcr-public/ab4ca212-278a-4221-a4ce-4718dc9370d0/70a0a235-402a-4317-bc7a-b549de00ad3c/vsphere-vddk-65-release-notes.html

To resolve the issue, remove the existing snapshots so CBT can be enabled at the time of the next backup.