Posted by: Jan Stafford
P2V, Uncategorized, VMware
While researching P2V migrations, I came across some discussions of problems encountered during the process.
Dave Mast, Geek at Large, learned this lesson about P2V migrations and shared it on his blog:
“This Tuesday we attempted a P2V (Physical-to-Virtual) conversion on our domain controller. It worked, but not as well as I expected. We wound up losing the SYSVOL share (where all your group policy stuff is kept) during the conversion. We still had our physical machine present, so we fired it back up and all was well.”
Mast is prepared for his next P2V experience. “I set up a second domain controller and stuck it in one of the IDFs. Hopefully the domain data will replicate from the new DC to the old, and if not, we can always start from scratch with a new VM.”
Here’s a thread about Exchange problems in P2V migrations. It’s a tale of many crashes.
Another informative P2V migration tale comes from Scott Lowe’s blog. He talks about using VMware Converter. Here’s a tidbit, but you should check out the whole entry:
“The only odd thing we ran into was that Converter refused to log in to VirtualCenter. We tried short hostname, fully qualified hostname, and IP address, and still had zero luck getting Converter to connect to VC. Fortunately, connecting directly to one of the ESX servers using the root account worked without any problems whatsoever, and the overall conversion process took about 1 hour and 20 minutes to move the 12 to 13 gigabytes of data on the source server.”
I’m still looking for P2V migration stories — successes and failures — to help me build a best practices and “beware” guide. Got any tales to tell? Add a comment, please, or send me an email at email@example.com.