We have old VMs (Debian which replicates without problems.
But the replication on new VMs (Debian 9) is corrupted, half of the services like SSH or UFW no longer open.
The only difference is that the old VMs are Thick and the new ones are Thin.
Is it possible that VEEAM Free does not support Thin VM replication? If yes, what can I do?
Page 1 / 1
Hi @mathieuEQT
Veeam has no issues with replicating Thin Disks. It should work like thick disks.
And veeam supports all VMs with OS that are supported by vmware. If Debian 9 is supported with your esxi Host, then the replication will work.
Are the service which cannot boot all network related? Does the replicated vm has a network link?
I‘m not a linux expert, but you could try to check the services logs. They should be stored in /var/log/*
Can you try something?
Create a snapshot of the vm
create a new vm from the snapshot
boot the vm with a isolated vswitch
Does the services start up?
What happens when you access via console?
Odds are that this isn’t a VMware/Veeam issue at all, but instead a config issue for the OS.
Are you seeing the services aren’t starting? Any relevant output from the logs?
Typically what I would expect to see is the MAC address wherever the VM is replicated to being automatic and because the MAC address is changing, any IP/MAC bindings not matching and then the IP config not matching etc.
If you can confirm your services are starting and the IP config is matching what you’re expecting etc and then report back.