Skip to main content
Question

Protection group for Failover Cluster does some installation despite being set to "automatic upgrade = no"

  • January 22, 2026
  • 3 comments
  • 17 views
Michael Melter
Forum|alt.badge.img+12

Just a heads up combined with the questions if others noticed the same:

At a customer we have an quite important Windows Failover Cluster (2 VMs) being backed up via managed agents through a protection group. For good reasons the protection group is set to “automatic agent upgrade = no”. 

After the upgrade of the VBR to V13.0.1.1071 we did rescan the protection group to have it notice the now outdated agents.

Instead of just detecting this, the rescan immediately decided to re-install the transport service.

This is quite dangerous IMHO as we specifically did not want to trigger any installation tasks without actively starting from the GUI. 

Did anyone else see this behavior?

Thanks,

Michael

Michael Melter - #VeeamLegend #veeam100 | VMCT | VMCE9 | VMCE2020 | VMCE2023 | VMCE2021 | VMCAv1 | VMCA2022 | VMCA2024 | VCP | MCP | DCIE | PhD | VDST TL3

    3 comments

    Andanet
    Forum|alt.badge.img+12
    • Andanet
    • Veeam Legend
    • January 22, 2026

    Oh WOW! This automatic update is really dangerous. 

    I have a client with more than 30 database cluster in V12.3. I haven't yet been given the go-ahead to move to v13, but this information is very valuable. I think you should open a case. 

    Antonio D'Andrea | VMCE 2021 | VMCA 2022 | VMTSP2024 | Veeam Legend | VUG Italy Leader | Object First Ace | VCP6-DCV | I want it written on my tombstone "Please start a restore to the last valid backup"
      Michael Melter
      Forum|alt.badge.img+12
      • Michael Melter
      • Author
      • Veeam Legend
      • January 22, 2026

      Oh WOW! This automatic update is really dangerous. 

      I have a client with more than 30 database cluster in V12.3. I haven't yet been given the go-ahead to move to v13, but this information is very valuable. I think you should open a case. 

      As we did not see any issues the customer refrained from opening the case.

      I cannot get any logs from the system, we’ll have to skip filing a case this time. But maybe someone from the Veeam side reads here and checks with dev if its really possible to do updates without being allowed to update. 

      If you read closely in the screenshot it says “repairing”. But there was nothing to repair. It did it on both nodes and the agent ran just fine before the upgrade.

      Michael Melter - #VeeamLegend #veeam100 | VMCT | VMCE9 | VMCE2020 | VMCE2023 | VMCE2021 | VMCAv1 | VMCA2022 | VMCA2024 | VCP | MCP | DCIE | PhD | VDST TL3
        coolsport00
        Forum|alt.badge.img+21
        • coolsport00
        • Veeam Legend
        • January 22, 2026

        Oh wow...that is interesting behavior Michael. Maybe worth bringing this up in the Forums maybe?

        Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
        Terms & ConditionsAccessibility statement