Vmware converter 3.02

I am getting errors when attempting any Vmware backups. I saw on this forum that I should attempt to use vcbmounter commands to see if the snapshots work that way, and I got the output pasted on the bottom of this message. Two questions on this: 1. Should I be concerned about the SSL messages, or can they be ignored? Labels: Labels: 7. All forum topics Previous Topic Next Topic.

You can ignore the SSL messages, I get them also but get successful backups. Then watch out, for this dedicated vcbuser account. Won't work! In regards to your problem, about failed to open the disk, I'm at a loss there. As you say the disk is seen in Disk Administrator OK There is a vcb SAN debug command you could try vcbsandbg. Post Reply. Preview Exit Preview. You must be signed in to add attachments. Additional options Associated Products. You do not have permission to remove this product association.

Yes, then you only have to worry if the VMware converter created any issue and then if whatever tool you use to convert from vmdk to vhd created any issue.

I have used Starwind's tool to convert from vmdk to vhd on a number of Linux machines and it has worked fine. But my preference would have been to not have to convert. Since the place he works for seems incredibly cheap and shortsighted Server , won't pay for a Acronis license It's the best suggestion I have to offer.

I've never had an issue going vmkd to vhd provided I stop all the unneeded services and don't install the VM Tools. Actually it is pretty straightforward for the Windows operating systems that understand virtualization.

The recommendation is to still rebuild the host instead of converting, just like the recommendation is a clean install instead of an upgrade, but for Windows Server and later, P2V is pretty straightforward. It would have been unbelievably forward thinking on Microsoft's part to build the changes into the operating system that and later have that makes P2V of those so much cleaner. Just look through this forum at all the other posts of people having difficulties P2V'ing Windows Server It is a gamble at best.

Some configurations simply cannot be converted. The only 'guarantee' is to rebuild from scratch. And, since is no longer supported, the recommendation is to not only rebuild from scratch, but the rebuild onto a supported operating system. What is the system running? Why not rebuild from scratch onto a supported operating system?

If so, unless you run the VM on the exact same piece of hardware from which you are converting it, you would be breaking your license terms. And since most of the physical machines that were in existence when came out did not support hardware virtualization, you might have problems there, too.

I can't rebuild from scratch the server for a simple reason. Some of client's compagny are using again this system though we tried to move him.

It is based since years that's why I would to do a P2V. There is no problem with the software Disdk2VHD. My only problem is I have no keyboard and mouse when i start my VM after with hyper -v. Don't have spare space to carve a LUN, but have an iPhone? I don't make this stuff up. Don't have an iPhone? To continue this discussion, please ask a new question. Anunta Followers - Follow.

Kelly for Anunta. Get answers from your peers along with millions of IT pros who visit Spiceworks. Probably a silly question, but better to be safe than sorry. Best Answer. Ghost Chili.