Error converting an Exchange server and a File Server at 95%

[WarlockArg]

Hi,

I'm having problems when I'm trying to convert an Exchange server and a File Server. Both of them are physical servers that I'm trying to convert into an ESX vSphere Advanced infraestructure. The problem is that when the conversion process reach 95% fails and sometime it makes that the physical server reboot. Is there any recomendation to convert and Exchange Server. Because I also have to convert an SQL server and I don't know what to do.

I tell you that these conversions were tryed to be done with both server in production. Could it be the problem? Should I stop all MS Exchange services before begining to convert the machine? Somewhere I found that it is recommended that all users be offline of the server when trying to convert a machine, but I don't know if that is a suggestion or it's an imposition. I thought that perhaps the problem could be that the Exchange database cannot be quiesced and that's because the process is failing.

Can anybody help me with this issue? On the other hand, is there another application that is used to convert a physical machine into a virtual one? I only know the VMware Converter.

Thanks.

Warlock.

[HannaL]

Yes. Turn the services off before the conversion. VMware clearly states this is a best practice, see this kb step 2 in planning:

http://kb.vmware.com/kb/1004588

"If the source is a Microsoft Exchange, SQL or other database server, VMware recommends that the database services be shut down prior to conversion. This minimizes any chance of corrupted database tables or stale data in the destination virtual machine. "

http://www.vmware.com/support/pubs/vcc_pubs.html

Hope this helps

Hanna

[jkumhar75 · Accepted solution]

While doing the P2V conversion, it's always recommended to stop the services related to database,application and tools.This helps the conversion process to complete without errors.

Have you checked the log files from the vmware convertor, for the errors it gives while doing the conversion?

For doing the P2V conversion there is enterprise tool known Platespin.Refer the below link for the more details.

http://www.platespin.com/products/powerconvert/

Jay

MCSE,VCP 310,VCP 410

Consider awarding points for "helpful" and/or "correct" answers.

[WarlockArg]

I attach an image with the error I'm getting and the log file in order to see if someone can help me. I tell you that although the process is failed the VM is created on the ESX but when I start it doesn't find de operation system to boot up. In the image I'm attaching you can see there is being a problem with the reconfiguration process.

Thanks.

Warlock.

[rogard]

You have some TSM backup agents, might be that the convertor couldnt get a lock because of TSM.

Try stopping that and associated backup software

[continuum]

"can't find system volume ..."

I would inspect the boot.ini of the converted VM - it may have a bad entry




___________________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

[MJURADO]

Hi,

Besides stoping all the related services, Install Converter Standalone Client on the server to be clone. Clone using no HD compression and no VMtools installation.

Hope it helps.

[WarlockArg]

Mjurado,

How do I deactivate those options? In the converver wizard? I guess the option to not compress the HD is inside the converter wizard in the screen where you select the HD destination format (when you select to use the minimal size and so on) but I didn't see the option about the VMtools.

Thanks.

Warlock

[MJURADO]

Hi WarlockArg

During the conversion wizard - Step 3 View / Edit Options

Data to Copy - leave original size unchange

Advance options - Install VMware Tools - No

[WarlockArg]

Thanks everybody for helping me with this issue. Actually, the problem was solved activating the boot flag in the VM virtual disk with Gparted (I guess other tools as Partion Magic also would have worked). It seems that when the converter makes the final reconfiguration (the process that was failing at 95%) one of the tasks it does is marking the partion as a boot one. Because that reconfiguration failed the partition had not never been marked as boot.

However, your help was very useful because it helps me for another cases.

Thanks.

Warlock