AAP failing on most VMs since v13 upgrade

[jc711]

Good morning,

It appears this updated hotfix has fixed the applicaiton crashes observed with the job manager process and no further timeout issues have been observed for guest processing on jobs.

@vssoftware unfortunately I don't think there is a way to just get it as Veeam support needs to provide it. It took multiple escalations and pointing to this forum for us to get the initial hotfix. I would suggest bringing it up with them again as they will validate if the errors seen fit the issue.

Thanks,
Jesse

[Mildur]

Hi @vssoftware,

Jesse is correct. You need to contact our customer support team — they will need to confirm whether the hotfix is applicable to your situation before providing it.

Best regards,
Fabian

[muhsinh]

Found this forum post after Googling. Just replied to my support Case # 07989804 to ask for the hotfix

[Daniel_J]

Also encountered this issue and have been provided the hotfix to test. It's slightly annoying that support didn't have this listed on the their notice board as an issue under investigation, and sent us on an alterate path to troubleshoot.
Case #07993586

Does InverseVssProtocolOrder still work in Veeam 13?
With backup VM's being isolated, GIP spends way too much time trying network level interaction, before falling over to use VIX. It would be preferable to switch order of preference if it's possible.

[adamger]

Hi,

redeploying the persistent agent with the deploy kit solved my problem on the DCs.
(https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13)
I think something got mixes up during the initial update of the agent.

Kind regards
Andreas

Hi,

the same problems occuring here, Support Case # 07986517.
Started directly after update to version 13.

Timeouts while machine backup of our Terminalservers from vSphere..
No AAP backup of our DCs.
All other machines unaffected.
No blocked traffic in firewall logs.

Tried a lot of things.
Trusted that an update would solve our problems.

Opened Case, provided logs waiting for support to ask the right questions .

Best regards
Andreas

[david.domask]

Does InverseVssProtocolOrder still work in Veeam 13?
With backup VM's being isolated, GIP spends way too much time trying network level interaction, before falling over to use VIX. It would be preferable to switch order of preference if it's possible.

Yes, it should still work -- are you seeing different behavior when you enable it?

[Daniel_J]

Thanks, support also verified it should still work. Will test further and report back.

[Daniel_J]

Some improvement, but not a solution. Looking at the logs from Guest VM and VBR, it appears the the backup process is taking too long and exceeding the VSS timeout window. It is inconsistent still. Have sent further information to support to invesigate.

[Daniel_J]

It is still inconsistent with the hotfix. Im not sure why but reviewing Guest VM VSS logs amongst different affected jobs; even across different VBR 13 installations; the jobs are encountering excessive SSL Handshake failures with the veeam backup process. Sometimes 30 failures in one job; and this appears to be causing additional delay dring the VSS Freeze window and the completion of the snapshot. Either that or something else underneath not so transparent is still causing addtiional overhead and still causing a wait timeout. Logs have been provided to support.