Issues with VSS app-aware after V11 upgrade

[kwinsor]

Hi,
We have random VSS app-aware issues since upgrading to V11. Both with Exchange and SQL we get the following randomly across backup jobs.

Exchange

Code: Select all

2021-05-11 7:28:05 PM :: Unable to truncate Microsoft Exchange transaction logs. Details: Failed to call RPC function 'Vss.FinishSnapshot': Error code: 0x800706ba. Failed to invoke func [FinishSnapshot]: The RPC server is unavailable..  

SQL

Code: Select all

2021-05-12 1:10:49 AM :: Failed to perform post-backup application-aware processing steps Details: Failed to call RPC function 'Vss.FinishSnapshot': Error code: 0x800706ba. Failed to invoke func [FinishSnapshot]: The RPC server is unavailable..  
2021-05-12 1:10:49 AM :: Unable to truncate Microsoft SQL Server transaction logs. Details: Failed to call RPC function 'Vss.TruncateSqlLogs': Error code: 0x800706ba. Failed to invoke func [TruncateSqlLogs]: The RPC server is unavailable..  

We have a case open for a while but it's going nowhere. Support had us increase the guest snapshot timeout with no luck. Doing a app-aware guest creds test checks out fine for both RPC and VIX.

Anyone else having similar issues?

[veremin]

Can you share a ticket number with us, so we can ask R&D team for further assistance? Thanks!

[kwinsor]

Sure no problem.......it's Case #04768640
Thanks.

[Andreas Neufert]

Maybe helpful here:
https://answers.microsoft.com/en-us/win ... b4e6cf6275

[Andreas Neufert]

Do you use any load balancing sofrware with your SQL server? For example Windows NLB-Cluster?

[ChrisWilkinson]

I haven't opened a case yet but I also have this issue after a v11 upgrade. It was working fine before

[Egor Yakovlev]

The issue seems to be infrastructure specific, so support will need some active troubleshooting to find a root of it. Please do open the case when you can.
Error itself is linked to RPC timeouts, and maybe KB2825 will solve it.

[ChrisWilkinson]

I've put the registry key suggested in KB2825 in the affected server. I'll check tomorrow to see if it helps. If not I'll log a case with that already out of the way

[ChrisWilkinson]

My case number is #02371578