A little help would be appreciated
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?
+12
Hi
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?
Does the services start up?
Hello Mildur,
thank for your reply,
The issue is the compatibility with Debian 9 on EXSI 6.0.
How can I solve my problem on VMware?
+12
Hello Mildur,
thank for your reply,
The issue is the compatibility with Debian 9 on EXSI 6.0.
How can I solve my problem on VMware?
Hi
Debian 9 should be supported on ESXI 6.0:
VMware Compatibility Guide - Guest/Host Search
+22
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.
I notice my problem is related to the transmittion between my two EXSI (6.0)
I also notice is that the compatibility on VMware is Debian8 X64 (There is no Debian9 X64)
When I open my terminal, I have different problems.
Boot messages
For the Mac address, I see both same (with the main VM an the replication)
I share my journalctl
+22
Thanks for sharing, can you confirm all the disks are being replicated and none are set to independent (those can’t be snapshoted)
The errors are all talking about issues reading data from disk.
I confirm that my drives are not in independent mode.
I enable : application-aware processing: I have some problems corrected
I share my journal
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
