Trying to do a Physical to Virtual Vmware transfer.


We are rolling out VmWare on to our network and we have been using it Since 12/09.  So far so good, with brand new Virtual Machines and Brad new isntallations.  We recently tied doing a 'Physical to Virtual' transfer and that errored out.

I exported the error logs and attached them to this question.  We are working with a consultant that has extensive knowledge in VmWare; but, he is busy at the moment and unavailable.  We are getting nervous waiting for him to be available.  The C: Drive carried over; but, not the D: drive.  I was wondering if anyone can help me figure out:

1.  Why did this 'P to V' error out.
2.  What can we do to correct this?

The Physical Server has the following parameters.
a.  4 GB RAM.
b.  Windows 2003 Server Std.
c.  Has SQL Server 2005 installed.
d.  C: Drive is 9 GB Large (only 530 MB free).
e.  D: Drive is 126 GB large (only 13 GB free).

This Server is an application Server (Microsoft Dynamics Great Plains verison 10.0)
PkafkasNetwork EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are you increasing the disk sizes as you migrate it?  Depending on your VMFS formatting if you are increasing the D: drive larger than 256GB then you could be having an issue.
PkafkasNetwork EngineerAuthor Commented:
No, not htat I know of.  The plan was to increase the disk size after the VM has been created.

Like I mentioned above we have a consultant that is supposed ot help us wit the initial setup to make sure we are setup correctly.  I can ask him about that and notice for next time.
Paul SolovyovskySenior IT AdvisorCommented:
I think the issue is space on c drive since vConverter uses VSS. If it's starts running out of space it will fail.  Clean up the C Drive or move the page file to the D Drive temporarily.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

The coverter wizard gives you a screen where you can choose the drives to be coverted, number NIC to  be availabe on the target etc. It even allows you to resize the drives on the target machine.  If D drive was omitted on that screen, then D drive will not be converted.
PkafkasNetwork EngineerAuthor Commented:
I believe the C: Drive was successfully converted; but, the D: Drive bombed out.

Paul SolovyovskySenior IT AdvisorCommented:
By default the changes for all the drives are on the C drive.  If you have data changing while you're doing the migration you can get this type of error.  Clean the C drive and try again

Another way to do this is to download Symantec Backup Exec System Recovery or Acronis and install.  Make an image of the system and use VMware Converter to convert the image.
Vijay kumar MohanrajCloud ArchitechCommented:
As per the Log say's C drive was cloned sucessfully D drive not sucessfully cloned, what you will do first check the Storage space for the particular ESX server, and make sure the disk space will me more that 150 GB, and start doing the P2V  if is it possible during the p2V reduce the d drive disk space to 30 GB and still it is not sucessfull, please go head and do the cold P2V it will fix the issue.
PkafkasNetwork EngineerAuthor Commented:
The ESX Server has more than enough disk space.  However, Mail2vijay1982, you mentioned to try and reduce the D: Drive to 30 GB; but, on the actualy physical box the D: Drive is I believe 135 GB large.  

Is that a good idea to reduce the D: Drive size to 30 GB if the actual physical D: Drive is 135 GB?  I guess I do not understand how P 2 V works.
PkafkasNetwork EngineerAuthor Commented:
Tried it again and still did not work.  This time we did nto make any changes to the E: Drive (drive space).  All of teh services for SQL were stopped (via the converter) Failed and Volume E:  Any help?  The consultant is kind of stumped.  What can cause this?
PkafkasNetwork EngineerAuthor Commented:
Screen shot.  Looks to be the same thing.
Paul SolovyovskySenior IT AdvisorCommented:
Try imaging it first.  I've done hundreds of these and every once in a while I get a machine that just doesn't want to go.  At that point I image it with Symantec or Acronis and use the VMware converter to convert the image.  It seems to do a good job
You may have to do a cold migration.  You can download the bootable CD from VMware and burn it to a CD.  This will allow you to migrate the server without anything running.  You will need to have an Enterprise license in order to get the ISO though.
An alternative is this:
 But if you can get the converter ISO, I would recommend that path first.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vijay kumar MohanrajCloud ArchitechCommented:
is that you are doing P2V from VC server are different server and let me know which version P2V converter you are using,and check once physical machine of hardware having any issue or not ?
Vijay kumar MohanrajCloud ArchitechCommented:
do one thing add this server for "guided consolidated" on VC server, wait for  2 day and it will analysis and suggess you can able to convert this machine to virtual or not from there it self you can able to convert this sever to virtual
PkafkasNetwork EngineerAuthor Commented:
We will try a cold migration Monday night.  We do not presently have any imaging software.
Vijay kumar MohanrajCloud ArchitechCommented:
ok so you can download the latest version of vmware convertor from Vmware
below i have given the link, for downloading this you have register your id from VMware
vmwarun - ArunCommented:
Is the Workstation from where the VMware vConverter is running and the physical Server in the same subnet or different subnet ?
PkafkasNetwork EngineerAuthor Commented:
1.  I discovered that the Physical Box had a bad CD-Rom (D: Drive).  I just swapped a new CD-Rom in the Physical Server.  Now the CD-Rom works.  Would that have caused the 'P to V' to not work?

2.  The Converter is running on a VM, that is on a different subnet from the Physical box.

3.  We did not try the cold migration yet.  The consultant could nto make it yesterday.  Hopefully soon.
vmwarun - ArunCommented:
Disable simple file sharing and check whether Ports 137,138 (UDP) and 139,,445 (TCP) are opened between source and destination.
PkafkasNetwork EngineerAuthor Commented:
We wil try again next week.  Please stay tuned.
PkafkasNetwork EngineerAuthor Commented:
The cold migration did not work.  Pelase see the logs.

After an hour it bombed out.
PkafkasNetwork EngineerAuthor Commented:
Another log.  We used the cold migration - Vmware cvonverter.

BAck to teh drawing board and the deadline is approaching.  Should we juast gove up? And use a normal server?
Paul SolovyovskySenior IT AdvisorCommented:
You can download a trial version of imaging software, either Symantec Backup Exec System Recovery or Acronis True Image.
PkafkasNetwork EngineerAuthor Commented:
Hello,  Out consultatn staes the follwoing:

"Unfortunately, I don't see a specific error in the logs.  It gives a 5666 error, which is generic, but usually indicates a problem with the volume that is being cloned, or a problem with the network.  Since it's failing at about the same point regardless of whether we use cold clone or warm clone, I think we may be dealing with a problem with the volume.  "

The plan now is to try a cold boot again; but, 1st I will move the physical server, to be on te same switch as the VmWare Servers are (gigabit switch).  

"If it fails again, then we will have to move it over with only the C: drive active, then create the E: drive on the virtual server, and then do a separate image or backup and restore of the E: drive to the virtual server. "

What do you guys think of this plan?
vmwarun - ArunCommented:
The above mentioned recommendation was what paulsolov suggested.
PkafkasNetwork EngineerAuthor Commented:
Is that what "... and then do a separate image or backup and restore of the E: drive to the virtual server.  ..."  means.

OK, thanks.  So we will need to use some imaging software.  What if I use a backup from Symantece backup exec (of the E: Drive).  Will that work instead (to move the E: drive over?
Paul SolovyovskySenior IT AdvisorCommented:
If you use the imaging software you can then use vmware converter to convert the entire image to a VM.  Using backup exec to do system drive and then restore using BEU is complicating things.  Just keep it simple.
PkafkasNetwork EngineerAuthor Commented:
The exact reason for success was that we created 1 disk instead of 2 seperate disks.  The original Box had 1 parttion with 2 logoncal drives.  There was a Raid 5 stripe across both logical drives (on 1 partition).  I di dnot mention that before and no one bothered t ask.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Tax / Financial Software

From novice to tech pro — start learning today.