Move 2008 DC to a new Server.
- Thread starter GiB
- Start date
the warranty will be running out soon 5 years old and i was going to get a new server with warranty. If its a complete nightmare then i guess i could keep running the server although will have some spare time in the school hols so was thinking it would be the best time if any to do it as I can afford the downtime while no ones in school. But i wanted it so when staff get back they just log in as if nothing happened. Dont fancy a complete rebuild hehe.
Ta
Ta
Man of Honour
- Joined
- 17 Nov 2003
- Posts
- 36,747
- Location
- Southampton, UK
You do not P2V domain controllers, its retarded
So incredibly easy to roll out a new one
Sorry but that is just a stupid statement. Do you know anything more about the environement that box is in? Do we have any details on devices or services which are either reliant on that box by name or IP address? P2V'ing the box is a zero risk option as rolling back to the original device if there is a failure is just a case of turning it back on.
Also running a physical DC these days when we have the option of using a free hypervisor is also not a good one.
I have to agree with n3vermind, p2v is a bad idea (as is any sort of backup/restore for the same reason).
Nothing wrong with virtualising it, in fact I'd reccomend it but it should still be built clean.
A P2V process is still going to have some downtime and the downtime of doing a proper migration wont be much less.
The easy way to do it would be to build it with a new name and IP address (no downtime here) then demote the old one and rename/change the IP of the new one (downtime here is a reboot).
Another way would be to build a new one and change DHCP scopes, other servers DNS settings etc to point to the new one. Then demote the old one and use a secondary IP to ensure you havent missed anything. You might be able to use a DNS alias too but something about that with a DC sounds funny so I'd want to double check it's ok first.
This way has just as little risk in terms of recovery as a P2V provided you have a backup of the original before you start the process. It also gets the job done properly, rather than a quick/easy way.
Nothing wrong with virtualising it, in fact I'd reccomend it but it should still be built clean.
A P2V process is still going to have some downtime and the downtime of doing a proper migration wont be much less.
The easy way to do it would be to build it with a new name and IP address (no downtime here) then demote the old one and rename/change the IP of the new one (downtime here is a reboot).
Another way would be to build a new one and change DHCP scopes, other servers DNS settings etc to point to the new one. Then demote the old one and use a secondary IP to ensure you havent missed anything. You might be able to use a DNS alias too but something about that with a DC sounds funny so I'd want to double check it's ok first.
This way has just as little risk in terms of recovery as a P2V provided you have a backup of the original before you start the process. It also gets the job done properly, rather than a quick/easy way.
NO
I said nothing about running a DC in a VM being a bad idea, you can.. there are recommendations to follow but you can. I do already
But do not P2V it, if you need the same name/ip you demote the old one, create a VM with same name/ip and promote
I was talking about you saying P2V was retarded. I totally disagree with you and for reasons I've stated. What benefit do you gain by not doing a p2v? If the server is shutdown clean, you p2v it properly and comes back ok post P2V then whats the issue. You then remove any additional work you need to do adjusting clients, DNS DHCP etc and have a virtuliased instance of a DC with all the benefits that brings.
So before going and stating its retarded state some reasons why, and try to understand that in the real world this is a tried and tested approach.
P2V is generally not a reccomended approach for production servers, tends to cause issues with remnants of drivers and things left over.
I'd NEVER, EVER P2V a server for a live environment as maybe 50% have given me problems. Let alone something as important as a DC.
New server, promote it, transfer roles, demote old one and rename new one - its a very simple job and really not worth taking risks with to cut corners
P2V is not recomended for production servers? That's 1 of the funniest things I've read on here in ages.
If your getting that sort of failure rate I'd suggest you get yourself a better process as I've done 100's over the last couple of years with a sub 5% failure rate on 1st try and that is usually caused by boot cd issues rather than the P2V process.
If your getting that sort of failure rate I'd suggest you get yourself a better process as I've done 100's over the last couple of years with a sub 5% failure rate on 1st try and that is usually caused by boot cd issues rather than the P2V process.