https://docs.xcp-ng.org/appendix/cli_reference/#appliance-commands

This problem has since been resolved. The issue related to running pfSense as a VM when using an additional IP form OVH Cloud. When using an OVH additional IP on pfSense the MAC address of the additional IP needs to be entered in the WAN configuration. [image: 1764708934016-428e2149-dc16-4f6f-8d60-8f681dd8ab63-image.png] When we restored this pfSense VM from CR and then migrated it to our production host the MAC address had been changed in XO. Once the correct MAC address was reentered into pfSense everything worked again. This is a real gotcha when running pfSense as a VM using CR on a host that is not part of the main pool.

@Bastien-Nollet The delta backup job saves to srv04-incremental and srv12-incremental. The incremental mirror job has srv04-incremental as source and srv12-incremental as destination. The VM that showed no data to copy message was a the "Incremental backup every 4 hours - 8 days retention" backup job. Originally I only had one remote, srv04. I created srv04-incremental and renamed srv04 to srv04-full and used the mirror backup feature to copy all delta backups to srv04-incremental (as I did not want to attempt to move the data on the NFS backend side). Then, I set up srv12-incremental and srv12-full and created mirror jobs to copy from srv04-full and srv04-incremental. Once the mirror backups were completed I switched the normal backup jobs to store backups on both backup servers. I can set up a support connection if you want to remotely check this.

I hope someone will reply to my post here about how to check status on this but I believe I've resolved the main issue: I disabled and re-enabled the whole task itself yesterday and it ran this morning as scheduled.

@bvitnik Thanks for your reply! Yes, all of the XCP-ng hosts have been restarted since I started monitoring the /var/log directory due to package upgrades. I also restarted the toolstack 2 or 3 times in the time frame so I think the issue was not caused by some sort of stuck process or similar. I did some research in this regard and also noticed that most people that have an environment of my scale do not encounter this issue (I currently have 105 VMs running). So I also suspect that there is something unusual happening in my pool. I thought about circumventing this issue by implementing a remote syslog server (like graylog) that has enough storage and letting all my XCP-ng hosts write to it. I would really prefer to fix the underlying issue though. Does anybody possibly know some common things that could cause this that I could check? That would be really awesome. Thanks and best regards

@henri9813 yes thank you for correcting my message