Effort to migrate five real servers to two virtual servers running Windows Server 2008 (Hyper-V)

Forums › IT Pro and developers › Effort to migrate five real servers to two virtual servers running Windows Server 2008 (Hyper-V)

lchiu7

6521 posts

Uber Geek
+1 received by user: 543

Trusted

#34506 25-May-2009 11:18

Just tryin to get a handle on this.

This is an environment that has 5 real servers running Exchange, File/Print, SQL (only one application), ISA and OWA. Might add one or re-use one for a BES.

Want to migrate the workload to two real servers running 5 VM's probably just using 2008 and Hyper-V. Not sure there is a need for any add ons since the workload one each machine is predictable and fairly constant. At the same time might remove most of the DAS and install a SAN (iSCSI) to store all the content apart from boot drives.

Backups of all servers exist.

This doesn't sound like a huge project and just wondered if folks could provide an idea of the amount of effort it would take to do this? I think if we built one 2008 server, it could be cloned for the rest. Then it would just be a matter of installing Exchange on one box, SQL on another and migrating the data from either the existing servers drives (for file and print) or restore database backups from SQL.

One quote was provided but it seemed pretty excessive but since I don't do this for a living just wanted to get a reality check.

Thanks

[Moderator edit (MF): moved to correct forum]

Staying in Wellington. Check out my AirBnB in the Wellington CBD. https://www.airbnb.co.nz/h/wellycbd PM me and mention GZ to get a 15% discount and no AirBnB charges.

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#217613 25-May-2009 11:23

Alternatively you could get something like Symantec Backup Exec System Restore 8.5 Server Edition, complete a full backup of a server and use the same tool to convert it to a VHD.

Create a Hyper-V VM using that VHD, install Integration Services and see how it goes. This way you preserve your whole setup.

However, make sure the Hyper-V host itself is not part of a domain if the domain is running on a Hyper-V client on that same machine - bad things would happen if you lose your domain controller, you know...

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

lchiu7

6521 posts

Uber Geek
+1 received by user: 543

Trusted

#218147 26-May-2009 21:25

Thanks. Looks like the shop uses VMWare so that there is software from VMWare that can do the P2V migration. So the idea will be to create a bunch of LUN's on the SAN I guess, do the P2V and and reboot the servers on the virtual infrastructure.

Now if the new environment is going to be Hyper-V I think the Symantec solution might be an option. And I will take your note about the DC into account!

Staying in Wellington. Check out my AirBnB in the Wellington CBD. https://www.airbnb.co.nz/h/wellycbd PM me and mention GZ to get a 15% discount and no AirBnB charges.

jaymz

1136 posts

Uber Geek
+1 received by user: 76

#226277 18-Jun-2009 14:14

There sure is! VMWare converter (version 4.0 now) is a free download from vmware.com. You will need to register for the download but its free.

I have done several P2V conversion projects and there are a few things to note when doing it.

When you have run the P2V you should boot to Directory Services Restore mode (or Safemode) on each machine to remove the hidden NIC's from your servers (set devmgr_show_nonpresent_devices=1) That way you are able to avoid the DC (or other server) from attaching to another NIC and causing a DNS headache.

Have you run through a P2V before?