Avamar was backing up a virtual machine disk consistently with status “Completed” and then changes to “Config Files Only” at next backup.
This issue is caused by Avamar’s dataset being configured to point to a single disk on a virtual machine instead of the entire virtual machine image and then a storage vMotion is performed. This then creates a dead link to the disk as it no longer resides where the dataset is looking. Avamar attempts the backup and sees the virtual machine, but can not see the data causing the “Config Files Only” in the status column.
Solution is to edit the dataset to point to the new storage and re-perform the backup.