Converter / P2V Pointers

[number1vspheref]

Hi,

I've used Converter once or twice before to import virtual appliances but I'm effectively new to the whole P2V process in a physical to virtual infrastructure migration so I'd appreciate some pointers on using VMware Converter in this scenario ...

I've looked over at viops.vmware.com and also in the Converter documentation, both of which contained useful information... however, there are a couple of things that I'm unclear on ... some of these are as much process issues as Converter issues:

:smileyinfo: How do I know how much downtime to schedule for a P2V? Is there any rule-of-thumb (e.g. rule of thumb for typical roles / applications such as Domain Controller / SQL / Exchange)?

(ii) Are there any applications that can / should be hot-cloned (e.g. Domain Controller / SQL / Exchange)?

(iii) Are there are applications that can't / shouldn't be hot-cloned (e.g. Domain Controller / SQL / Exchange)?

(iv) Assuming hot-cloning is an option for some VMs, can P2V be done without any service interruption (i.e. no down-time) to users? If so, how can something like IP address changes / migrations etc be dealt with?

Any pointers on the above and indeed generally useful info on Converter / P2V'ing would be much appreciated.

Thanks,

number1vspherefan.

[vmroyale]

:smileyinfo: How do I know how much downtime to schedule for a P2V? Is there any rule-of-thumb (e.g. rule of thumb for typical roles / applications such as Domain Controller / SQL / Exchange)?

This will depend on a variety of specific environmental factors. Network types/speed, storage systems, congestion/traffic on either of them and many other things will make these times vary in different ways. The best bet would be to do a couple of P2Vs on test systems during different times. This will allow you to develop a guesstimate of the time involved. If you are considering hot and cold migrations, then test both.

(ii) Are there any applications that can / should be hot-cloned (e.g. Domain Controller / SQL / Exchange)?

It depends on the consistency levels you wish to achieve when complete. You can hot clone SQL or Exchange with the SQL/Exchange services stopped and get great results. With the services running, you could have problems.

(iii) Are there are applications that can't / shouldn't be hot-cloned (e.g. Domain Controller / SQL / Exchange)?

I would personally stay away from converting domain controllers hot or cold. There can be major problems with converting these. With other app servers, you will want to strive for application consistency. I prefer to schedule downtime and either stop the application services or bring the server down completely and do a cold migration. The P2V conversion is the one chance you may have to get this done right, and you should take every effort possible to get the most consistent images possible. You will likely be living with this converted system for a long time, and it is never good to start off with doubts about whether or not it was consistent to begin with.

(iv) Assuming hot-cloning is an option for some VMs, can P2V be done without any service interruption (i.e. no down-time) to users? If so, how can something like IP address changes / migrations etc be dealt with?

Doing a P2V with no service interruption would be very difficult, if not impossible, to pull off. At some point, you have to bring the virtual machine up on the network. There will be some time between the live machine going offline and the virtual machine coming online again. It could be one or two seconds, but again the thing to think about is consistency. The P2V left you in one state of consistency. Then you had to reconfigure and/or clean up and prepare the newly converted virtual machine. Time will have passed in between these steps. Also, any active sessions and/or connections would be dropped, when you made the switch. For me, there are just too many possibilities for something to get missed or noticed. Scheduled downtime is a good thing for P2Vs.

Good Luck!

[number1vspheref]

Hi,

Thanks for that vmroyale.

In relation to the statement "I would personally stay away from converting domain controllers hot or cold." - so is the best option to return the server to a member server role in AD before P2V'ing (it needs to be P2V'ed as it is providing some other services) and deploy a new VM, then dcpromo that to domain controller role?

Thanks,

number1vspherefan.

[vmroyale]

so is the best option to return the server to a member server role in AD before P2V'ing (it needs to be P2V'ed as it is providing some other services) and deploy a new VM, then dcpromo that to domain controller role?

In my opinion, the best option would be to create a new virtual machine to be a domain controller and provide no other services. Set up a local backup job to grab the system state and save it off somewhere else. Then you have a virtual DC with a simple configuration and also a supported backup and restoration option.

After the new DC is built, demote the current physical DC and then P2V it in to the virtual environment. This is my ideal approach, but if licensing and/or other cost factors are at play, then your approach will also work.