I do run XOA on its own dedicated host/dedicated pool, so the xcp-ng cpu scheduler does not cause issues with other busy production VM's while backup tasks are happening. this also allows XOA to use 100% of cpu cores making backups (especially with compression on) faster. xoa does DR back up to the primary pool in case something happens to the host its running on.

Thanks everyone! I’ll let you know if we have any issues.

Use CR instead of DR then, it will send only the diff to the other host, so it will be faster.

@gofm not sure on windows but on linux the walltime is written in UTC to the CMOS when you shutdown or when you explicitly call hwclock command. the time written in the virtualized CMOS should contain an offset to the host clock so when the VM start it read the host time plus the offset. I suppose that if you disable the time sync in windows, set the time and reboot you will come up with a correct clock. I have no link to point you at, this is just a sum of things I remember but may be dated and/or wrong still if you can reboot your Windows VM could be worth testing.