Skip to main content
Solved

Advice: migrating VBR between hypervisors

  • March 23, 2026
  • 6 comments
  • 32 views
M
Forum|alt.badge.img+1

I have a single VBR server, using a Data Domain as a repo, and it’s running on VMware. We are migrating from VMware to Nutanix AHV. We’ve already migrated a couple hundred VMs already, and now I’m getting down to needing to move the Veeam server.

Doing the migration results in some downtime - the migration process requires that new NIC drivers, etc be installed on the VM. I can easily set the services to manual for that duration, and then restart them when it’s done. 

BUT … is that the best way to do this? I considered installing a new VBR server natively on Nutanix, and then (somehow) migrating all jobs, etc to it. But the problem is, I only have 1 repo, and I know that multiple VR servers shouldn’t share the same repo. Don’t wanna risk corrupting anything.

Has anyone else done this? (migrate a VBR server from one hypervisor to another) If so, what did you do? What should I look out for. Any advice appreciated.

Best answer by CMF

Hi ​@MikeLeone ,

You could install a new Server and just use the configuration backup on the new VM. In this case i would disable all jobs, take a new config-backup and then use the “migrate” option when restoring the config backup.

This would lead to a new installation with all configurations from the old VBR Server.

    6 comments

    CMF
    Forum|alt.badge.img+8
    • CMF
    • Veeam Legend
    • Answer
    • March 23, 2026

    Hi ​@MikeLeone ,

    You could install a new Server and just use the configuration backup on the new VM. In this case i would disable all jobs, take a new config-backup and then use the “migrate” option when restoring the config backup.

    This would lead to a new installation with all configurations from the old VBR Server.

    Chalid Mohamed Fathallah | Veeam Legend | VMCE 2024 | VMCA 2025 | VCP-DCV | VCE-vSan
      Chris.Childerhose
      Forum|alt.badge.img+21

      The easiest method is as Chalid mentioned - take a configuration backup and store that somewhere.  Install a new VBR server which will allow you to update it if needed to Win2025 and then do the config restore.  Power down the old VBR server, and you will then have access to the repo, etc. from the new server.  This method is the easiest and simplest way to move servers/hypervisors.

       
       
       
      Chris Childerhose (Enterprise Architect) - VMCA | VMCE | VMCE-SP | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 7* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
        kciolek
        Forum|alt.badge.img+1
        • kciolek
        • Influencer
        • March 23, 2026

        Yes - I’ve done this in my lab using the method Chalid mentioned. Very easy and didn’t run into any issues. Just took time re-scanning all of my backup repositories. 

        Ken Ciolek | SHI Labs Data Protection & Storage Lead | Object First Ace | Commvault Global Ambassador
          M
          Forum|alt.badge.img+1
          • MikeLeone
          • Author
          • Comes here often
          • March 23, 2026

          Hi ​@MikeLeone ,

          You could install a new Server and just use the configuration backup on the new VM. In this case i would disable all jobs, take a new config-backup and then use the “migrate” option when restoring the config backup.

          This would lead to a new installation with all configurations from the old VBR Server.

          That does seem easy! That’s what worries me … LOL … So would you use Win 2025 for the new server? I haven’t had good experiences with Win 2025 using different MS configurations (specifically, it doesn’t reliably work with Windows failover clusters, and it gave us all kinds of grief when I tried to use it as a domain controller). It seems to be OK for other (non-MS) applications, I have it running there.

          So after restoring the config with this “migrate” option, would I need to re-configure any clients or proxies I have running? I have 2 Nutanix sites, so I have 2 proxies for that, and I have 2 tape servers (each with it’s own partitioned tape library). Plus a mount server for restores. and another proxy server for general use. So there’s a number of servers in my Veeam environment.

          Also, I would have to continue using v12.3, because (from what I read) v13 doesn’t support the old version of VMware I am still running (6.7). We’re going to be upgrading the VMware as well, but until then, I would need to be able to back it up using Veem.

            Iams3le
            Forum|alt.badge.img+12
            • Iams3le
            • March 23, 2026

            Hi ​@MikeLeone ,

            You could install a new Server and just use the configuration backup on the new VM. In this case i would disable all jobs, take a new config-backup and then use the “migrate” option when restoring the config backup.

            This would lead to a new installation with all configurations from the old VBR Server.

            +1

            [Microsoft MVP 3x | Veeam Vanguard ("26) | vExpert 6x | Cisco Champion 3x | Object First Ace 2x] | Veeam Legend ('21 -'26)
              CMF
              Forum|alt.badge.img+8
              • CMF
              • Veeam Legend
              • March 23, 2026

              if names can still be resolved, and the new IP is not blocked by a firewall everything should be working fine. I have used this method a couple of time when updating OS versions at numerous customers so it should be an issue. 

              you could test it because if you use the same version there will be no updates pushed by the new installation to proxys or repositories. So install the new Server and import the Config Backup. Then you can check the whole environment before enabling the jobs on the new Server. And failback is to just enable all jobs on the old server. 

               

              Chalid Mohamed Fathallah | Veeam Legend | VMCE 2024 | VMCA 2025 | VCP-DCV | VCE-vSan
                Terms & ConditionsAccessibility statement