VMware Cloud Community
sexconker
Enthusiast
Enthusiast
Jump to solution

Moving a Virtualized Domain Controller to a New Physical Host

We just bought a new server, and the ESXi 4.1 server we're retiring has a domain controller VM on it.

The new server will also run ESXi 4.1.

Is it safe to power down the domain controller VM, then move the files from the datastore to the new server, add it to the inventory, and then power it up?

I know there are tons of hazards when you virtualize a physical domain controller, but this domain controller is already a VM.  Is it safe to just move it and power it up?  Obviously, we won't power up the old VM afterward.

0 Kudos
1 Solution

Accepted Solutions
vmroyale
Immortal
Immortal
Jump to solution

Hello.

Note This discussion was moved from the VMware ESXi 5 community to the VMware ESXi™ 4 community.

Is it safe to power down the domain controller VM, then move the files  from the datastore to the new server, add it to the inventory, and then  power it up?

Yes, this should be fine. Just make sure you understand what happens when the DC is no longer available. Is DNS on this server, is it the only DC, etc. From a VM perspective, you will be fine. The rest of your infrastructure is where to focus on. The hazards of virtual DCs is mostly around trying to snapshot them or operational problems like putting a single DC on a virtual infrasturuture that might rely on it to work properly.

Good Luck!

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com

View solution in original post

0 Kudos
5 Replies
vmroyale
Immortal
Immortal
Jump to solution

Hello.

Note This discussion was moved from the VMware ESXi 5 community to the VMware ESXi™ 4 community.

Is it safe to power down the domain controller VM, then move the files  from the datastore to the new server, add it to the inventory, and then  power it up?

Yes, this should be fine. Just make sure you understand what happens when the DC is no longer available. Is DNS on this server, is it the only DC, etc. From a VM perspective, you will be fine. The rest of your infrastructure is where to focus on. The hazards of virtual DCs is mostly around trying to snapshot them or operational problems like putting a single DC on a virtual infrasturuture that might rely on it to work properly.

Good Luck!

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
0 Kudos
sexconker
Enthusiast
Enthusiast
Jump to solution

Thanks.

Yeah, it's 1 of 2 DNS servers, as well as a file server.

We've got another domain controller that's also the other DNS server and a WSUS server.

In terms of user impact, we'll be doing it after office hours on scheduled downtime so it won't really matter if they can't get to their stuff on the file server while we move the VM.  DNS and logging in will still work fine.

0 Kudos
arianebaluyot
Contributor
Contributor
Jump to solution

Hi were also doing the same thing during off hours time to avoid interruption to the business. I would like to ask if you successfully migrate your domain controller VM to the another Esxi host and what method did you use, is it the vmotion or any other way around?

 

Thank you in advance

0 Kudos
depping
Leadership
Leadership
Jump to solution

You responded to a thread which is 8 years old. Please open a new thread instead.

0 Kudos
arianebaluyot
Contributor
Contributor
Jump to solution

okay sir thanks a lot

0 Kudos