VMware converter going EOL for P2V workload

VMware converter going EOL for P2V workload

Since VMware announced that the last release of vCenter Converter Standalone 6.2 entered the end of general support on late 2019, you may consider the below workarounds if you still have a couple of machines configured as physical and you cannot re-deploy them:

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-lifecycle-matrix.p...

1st Machine is disks are hosted on an external storage array

              In that scenario; introduce the machine LUNs to any ESXi with access to the array and map them as RDM to a new VM then, perform a storage vMotion to convert them to VMDK files.

2nd Machine disks are hosted on local disks.

              In that scenario, you will need to install ESXi server on another storage  “SD, FC, or maybe a free local disk”, join the new host to vCenter then create a VM with the disks introduced as RDMs and perform storage vMotion to the vSphere datastore.

This may be a way out if you are unable to convert using VMware converter or third party converters.

Below links can introduce some information on the steps of migrating the VM after attaching the disks as RDM:

How to Convert RDM to VMDK - The Ultimate Guide

VMware Knowledge Base

Version history
Revision #:
1 of 1
Last update:
‎04-29-2020 02:02 PM
Updated by: