Solved CR tag ignored (kind of) in smart backup
Indeed, this is an XO bug, incomplete VMs should be ignored by smart mode, we'll fix it in the next releas.
Thanks again, now CR works as expected!
I experienced something similar.
I created a CR job and made it run. It's ~6TB and takes longer that a day (so I had to edit the timeout value). On the receiving end the backup job (using smart mode) started and was also backing up the CR VM (while it was still being transferred for the first time).
I checked the new VM and it dit NOT have the CR tag. After the job completed it had the CR tag.
Shouldn't it get the tag as soon as the VM is created to prevent it from begin backuped yet again?
I'm using XOCE xo-server 5.68.0 xo-web 5.72.0
It still backupped my VM...
I created a workaround now.
I added a new tag to the source VM (CRbackupBLOCK). This tag is transferred over directly.
The backup job on the receiving server has this tag blocking the VM from being backed up.
Thank you all for your feedback, I'll fix it ASAP
I've created a PR for this issue, feel free to test this branch: https://github.com/vatesfr/xen-orchestra/pull/5341