DPA Avamar reporting discrepancy

We have a VM that was renamed in vSphere after it was setup in Avamar.  Avamar has picked up on the fact that the VM was renamed and is referring to the client using the new VM name.  DPA reports still refer to the VM using its old name.  This is causing an automated process we have setup to fail.  The process compares the output of the backup client configuration report to an export of computer accounts from Active Directory.  How can we get DPA pick up on the fact that the name of this client has changed?