We have a VM that was renamed. Avamar picked up on this change nicely per the GUI (pleasantly surprised how seamless this was). However, it is sending the former client name to DPA. DPA support advised us to remove the client and force an update from DPA. We did this and the former client name returned (e.g. gridfqdn:Avamar:/vcenterfqdn/VirtualMachines/domainname:vmname-test_uid). The VM was renamed from vmname-test to vmname. Our DPA reports which we are attempting to use for automated reconciliation against Active Directory are thrown off by this name mismatch.
No, I have not tried restarting MCS. I hate loosing the easy access to the last few days of job history when we do that. Do you think it would help in this case?