If you have the latest version of proxycp.jar you could run the following command

java -jar /usr/local/avamar/bin/proxycp.jar --syncvmnames

Note : This works on >=7.1

This happens all the time in my shop.

The VM guys decide that they should rebuild a server and reuse the same name and IP address.

The backup then fails on a server thats been running fine for weeks or months.

The VMWare team didnt tell me that they rebuilt the server.

VMWare assigns a new GUID to the new server even though its using the same name and IP address.

The backup then fails on a server thats been running fine for weeks or months.

The easier way to fix this is

1. Retire the old name so that the backups stay in the catalog.

2. Add the server into Avamar as if it were a new server.

3. Run an ILB backup during the day so that you can get the base run out of the way.

ILB backups should not affect production.

This will prevent the nightly backup from running longer than expected at night.