Skip to main content
Question

Small B&R Hyper-V system. Remove Hyper-V Host & Backup Server from Domain


My inhouse system & handful of remaining customers all have almost identical configurations. They all have Community v12.0 but all will likely go to Foundation. Each has:

  • Production Host Hyper-V Server MS Server 2019
  • Replication Target Hyper-V Host MS Server 2019
  • Win10 Backup Server with Veeam Console
  • Ubuntu Immutable Storage unit. 

Since the Win10 unit is also my local Admin unit it is on the domain. Several of the Production Servers are also on the Domain before I received the info. Problems encountered:

  • When I setup the last Replication Target, I took the previous Production Host and removed it from the domain. It lost all knowledge of Hyper-V and existing VMs. No problem on that as I just resetup from scratch. Don’t want to do that with a Production Host if possible.
  • I’m sure removing the Win10 Backup Server/Console/Admin unit from Domain will make a mess. I don’t mind resetup as I’m going to install Foundation v12.3 but wonder what I should do on existing machines. Remove Hosts from Veeam first? Should I install Console on another user station and keep the existing Veeam configuration?

Sorry to be asking so many questions but I’m concerned about getting all updated. They are way behind  after spending a year recovering from a heart attack so working part time.

2 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8512 comments
  • March 24, 2025

Before you remove Veeam take a configuraton backup and store it somewhere accessible.  Then when you set up the 12.3 instance you can restore it so that it will keep your configurations and hosts.   You then just need to validate in the console they are connected again.


Tommy O'Shea
Forum|alt.badge.img+3
  • Experienced User
  • 125 comments
  • March 24, 2025

Restoring with the configuration file like Chris said is the best course of action. Having your Veeam server on your admin workstation should be avoided to minimize any chance of compromise.

I would highly recommend creating a VM on the Replication Target Hyper-V Host and installing Veeam there, as described in this article that goes over placement best practices.

Lastly, no need to apologize for asking questions! That’s what the community is here for. 


Comment