VMWare Converter Fail 98%

[djaburg]

In reading many posts regarding converting Debian 9 and it failing, I've also seen that "some" people have been able to work with the converted VM despite the failure.  I've further seen reference to disabling the converter from deleting the destination VM in the event of failure.  How would one do this?  The error message I'm getting at 98% is "cannot find source file /mnt/p2v-src-root/lib64/libc.so.6 during file copy (return code 1)". This is NOT a production scenario at the moment, so if I create a situation where I have to reload something, I can.  We're in a testing situation where we'd like to virtualize a production server for disaster recovery purposes and I've completely backed up the server and am working isolated from our production network.

The ultimately goal is to convert to VMWare and then export as a .OVA file for upload/deployment to AWS.  Any assistance would be greatly appreciated.

[Alex_Romeo]

Hi,

Converting a Debian almost always causes problems.

I want to give you another solution. With Veeam backup & Replication you have the possibility to backup also on physical servers.

You can back up your Debia computer and then convert the backup to vmdk format to be mounted as a disk in a new specially created vm without disk.

https://helpcenter.veeam.com/docs/backup/cloud/cloud_connect_disk_restore_agent.html?ver=95u4moving from linux physical server to VM - Veeam Community Forums

Exporting Disks - Veeam Agent for Linux User Guide

Veeam Backup & Replication 9.5 (free version)

Backup software for virtual, physical and cloud - Veeam Backup & Replication https://www.veeam.com/it/vm-backup-recovery-replication-software.html

other info...

How to restore Linux agent backup on VMware Sphere - Veeam Community Forums

ARomeo

[djaburg]

I certainly appreciate your response and will consider that as an option.  I'll be downloading VEEAM to see how the whole process works.  What I like about the VMWare option is the automated configuration for their platform in a single step...kind of.  I still would like to be able to see the destination VM at the point that it fails to see what's involved in getting it running before I head off in a different direction.  I'd really like to think that disabling the deleting of the created VM after a failure would not be all that hard to do.  I'm just not sure where to look.  Again, thanks for your response and I'll certainly look at that option.