VM Backups fail intermittently

refresh your connection to what ever vm software you are using.

for example VMWare

I have had to do this on occasion when the VM guys do something to VMware

Administration/Services tab

Utility node

find you vm connection and do a restart

might or might no help, but worth a try

Restart services, restart Avamar, resync vCenter... Nothing works...

Hello,

This issue may be related to the network settings between the Avamar Proxy and the Avamar Server.

The logs extract you provided is a bit limited, to look at the big picture we would need the see the full backup log.

Please review the "Avamar for VMware Guide" along with the "Avamar Security guide" where all the network requirements and basic configurations are described, links available on he support site.

If the issue persists I recommend to open an Avamar SR ticket, you will be better assisted.

I agree with you about the imited log, but there is no more on logs...

After this message, Avamar server still think that backup is running.

I also agree about networks settings but why sometimes it works and sometimes not ?

And last, I've opened a ticket.

Regards

Hello,

Check following things -

> VC connection is up. This can be checked from Administration GUI. If it is up and other backups from same VC are running fine, no need to restart the connection.

> From proxy, ping VC and Avamar. Check hosts file on proxy is updated with FQDN of Avamar server and DD if it is in use.

> On Proxy, run "yast", check network settings to ensure correct DNS and Gateway IPs are used.

Hope this will resolve the issue.

Regards,

Pawan

We're finding the exact same error is occurring against Linux and Windows filesystem backups, so i do not believe this is application specific, but rather something inside GSAN.

Each client can manually run successfully, but if the group policy is executed then we get failures with the exact same messages as described above.

This is a new ave deployment v7.4.1-58.

Any assistance would be greatly appreciated.

Thank you J.H., we have about 25 Linux clients running filesystem backups.  But, i don't believe this is specific to any application (VMware, Filesystem, 3rd Party) given the identical messages in the log, but rather something going on inside the GSAN where the job request cannot close due a certificate/credentials failure.

I had the same problem and opened an SR.  The resolution is that the Avamar proxy name needs to be added to DNS (forward and reverse) or the hosts file of all Avamar Utility/Storage nodes.  This is because of a new security feature on version 7.3 that does mutual authentication and that requires name resolution from the grid nodes back to the client IP.  I'm not sure if this is only part of the Avamar Security Package or if it's part of the base product as we have the Security Package installed.

I added hosts entries for all proxies on the 1 x utility, 3 x storage nodes, and 1 x data domain (using the Ethernet, Settings, Hosts Mapping).

On the plus side, you can go ahead and setup the DDBOOST ACL on the Data Domain after doing this.

There is also an internal article for this on the support site:

Backup could fail with 'Timed Out - Response' or MSG_ERR_AUTH_FAIL due to DD Boost Token slowness

Article Number 000499805

If you have a multiple ethernet interface scenario on the Avamar VM Proxy (vCenter on one, Avamar/DD on another), you have to the IP that is on the Aavamar/DD network to the hosts file on the Avamar nodes and also into the Data Domain (can be done via GUI on Ethernet screen).

What is the Fix for this issue ? Finally Support engineers fix the issue? Please explain about the resolution steps so that everyone will get the befit. We have placed a Ticket too .. but still they are keep on asking for logs and still issue persist since past 3 weeks.