asked on

vCenter Converter (P2V) converting errors.

Hi, We are having a problem with converting our physical machine to virtual using VMware vCenter.

Our version of vCenter is the Converter Standalone version 4.0.1 build 161434. The converter is installed on a networked local machine, connecting via i.p. address to the source and target computer.

The Server we are having problems with is a front-end exchange server running:

Windows server 2003.
Kaspersky Anti-Virus V 6
Microsoft Exchange 2003.

The following is an example of the error that occurs:

FAILED at 95%.
FAILED: Unable to find the system volume, reconfiguration is not possible.

Here is the log highlights:

Completed cloning volume 'C:'.
Updating the boot sectors on the target machine.
Updating drive letters for the target volume layout.
Starting reconfiguration.
Processing the reconfiguration datastore.
Error: Reconfiguration failed.

We have the "Synchronize changes that occur during cloning" set to "Yes".

Has anyone had this problem before? What can be causing this problem?

jramsier

It sounds like it is a config you set after you move the to the Virtual. Check your settings.

Other things to try.
Install the p2v software on the local machine.
ensure you restart before you p2v.
disable av
use as few settings changes as you can in the p2v software.
use old 3.5 p2v software if you have it (this worked once for me)

ASKER CERTIFIED SOLUTION

coolsport00

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

mbudman

ASKER

Thank you for the suggestions. Do you have an idea how long it should take to virtualize a server with a single partition (300 Gig) with less than 150 Gig of data?

Thanks,

Mark

coolsport00

Quite a while...that's a big chunk of data. A 30GB host can take about 45mins to an hour, so times that by 10. Another option, if you can do so, is to add another volume to house your DBs. Unmount your SGs, and move your mailbox DBs/logs to the new volume. Then, do a P2V of just your system volume and once complete, add a VMDK (virtual disk) of the size you need for your DBs and do a restore of the DBs to those new VM virtual disks. Keep in mind though having that much data is going to take a bit of time..even 150GB. Depending on what your traditional b/u & restore solution is, de-dup may come into play and restore will more than likely not take that long (we use Avamar). It's another option though.

~coolsport00

ryder0707

I doubt stopping services will allow the p2v to complete
From the error msg, most likely the converter unable to interpret the partition table of the source machine, i've encountered this problem before and the only way to solve this problem is to p2v is via cold conversion.

-vExpert 2010

coolsport00

Maybe so...but worth a shot 1st since that's always what VMware recommends. When it happened to me, it didn't work either, but for others I've assisted on here, it has. :) Also, VMware doesn't recommend configuring options at the end of the conversion wizard which is my initial suggestion outside of stopping the services. I still don't understand why though...VMware never gave me a good reason, they just 'highly suggested' to not configure options (auto install Vmware Tools, etc.). If you have any ideas as to why that is Ryder...I'm all ears! :P

As a last resort, if the above doesn't work, imaging the box with Acronis/Symantec can be attempted, then the attained image converted.

Regards,
~coolsport00

mbudman

ASKER

Thank you.

Cheers,

Mark