Skip to main content
Question

Veeam 13.0.1.2067 hanging when accessing database after upgrade

  • April 24, 2026
  • 26 comments
  • 434 views

Show first post

26 comments

  • New Here
  • September 4, 2026

Just a follow up from my v13 upgrade issue a couple of weeks ago:

After (sort of) uninstalling Trellix, definitely making sure it was not running, things still were not working as far as console access. Since there was nothing else to eliminate, the SE suspected something about the domain membership of the server, or the domain account used to install/run Veeam. So I deployed a fresh Win 2022 VM as standalone no domain joining, and got v13 installed and was able to connect to local ports to run the console etc. The SE suspected that with the original domain joined server, there may be something about v13 and my active directory account with local admin privileges were missing certain domain permissions? Either way, the new v13 VBR server is going to stay off the domain although our Windows admins are not enthusiastic about that. I have submitted the AV exceptions list for Defender, and requesting either a full exception to the IO filter security agent, or if they insist that we at least do a test run to confirm whether it impacts VBR functionality and performance (SE mentioned these kinds of agents do tend to cause issues).