Hi tinto1970,
Regrettably we won't be able to troubleshoot it over the forums and given the out of support nature of the environment, agents were going to be my suggestion as well. I'm not sure older Veeam versions will be the answer here personally as seems like a VDDK error, so it would require log investigation to solve.
Similarly, I imagine VMware's VMware converter in v2v mode could do this with downtime and a bit of scripting, but I get your caution on this.
If you want to try to investigate the logs yourself, check the source agent vmdk logs for the job that failed, usually the errors there are fairly clear as it's about the datamover agent talking to the VMware environment through VDDK library. For issues like file locks, connectivity errors, permissions, etc, the errors are usually quite clear.
Regrettably we won't be able to troubleshoot it over the forums and given the out of support nature of the environment, agents were going to be my suggestion as well. I'm not sure older Veeam versions will be the answer here personally as seems like a VDDK error, so it would require log investigation to solve.
Similarly, I imagine VMware's VMware converter in v2v mode could do this with downtime and a bit of scripting, but I get your caution on this.
If you want to try to investigate the logs yourself, check the source agent vmdk logs for the job that failed, usually the errors there are fairly clear as it's about the datamover agent talking to the VMware environment through VDDK library. For issues like file locks, connectivity errors, permissions, etc, the errors are usually quite clear.
Statistics: Posted by david.domask — Apr 02, 2025 11:01 am
