IT_Timo wrote:I already noticed that Windows Server 2016 will bring its own native implementation of CBT. Yet it will take some time until release and afterwards updating hosts. So if it's possible for Veeam to store CBT on the CSV, this might be a solution?
Does that happen to all VMs or just to VMs that were moved? Also, if full read occurs that's an expected behaviour.when the next backup is run a full backup is taken
Each host is aware of changes happened to other host's VMs. CBT data has to be cleared after VM migration thus causing full read (not full backup) during next backup run. The fact that you have full backup means that something went go wrong with VM ID. Normally Hyper-V cluster does not change VM's ID, so I suggest you to open a case with support team and post your case ID in this topic.because the CBT information is stored per host in HyperV , and as the VMs are moved onto the new host, no existing CBT information exists.
Users browsing this forum: No registered users and 13 guests