FYI, we have added this feature to our backlog 
XO Team
Developers of Xen Orchestra
Posts
-
RE: Can .keeper files be deleted from the backup share?posted in Xen Orchestra
they are created to ensure the samba mount is not removed by the os or another thread on XO
I would not delete them , especially since they are 0bytes files -
RE: Feedback on immutabilityposted in Backup
@rtjdamen said in Feedback on immutability:
@florent so this does mean it will never work when a forever incremental is used?
you can't have a immutable forever backup without having a infinite length, and an infinite
It may be possible only if we release the constraints.
The immutable script could release the immutability , merge the disks, but that means : the immutability will be lifted from time to time, and the responsibilities of the immutability script will be greater, and we'll need a way to track the vhd to merge and transmit the information to the immutability script -
RE: Migrating configured backup jobs between XO from sourcesposted in Backup
@ewoudstra Simply updating the git repo and rebuilding should be enough, but it depends a lot of how your previous XO.
The data should be kept across version as they are stored in Redis and in a LevelDB database as long as you are using the same ones.
And, as @olivierlambert said, if you cannot figure out the problem, simply export the config of your previous XO and import it into the new one.
-
RE: Netbox version 4.2.1 not supportedposted in Advanced features
Yes, we'll have to test the new version before bumping the max supported version.
In the meantime, if anyone wants to test it on a non-sensitive instance of XO, you can disable the version check in
xo-server's config:[netbox] checkNetboxVersion = falseBut I think I'm already seeing something that we'll have to handle:
The
siteforeign key field onvirtualization.Clusterhas been replaced by thescopegeneric foreign key. -
RE: Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"posted in XCP-ng
@Bambos A timeout error means that the host did not reply in the expected delay, which, if I'm remembering correctly is 5 minutes.
I suspect a problem on your host but we will take a look further on your support ticket.
-
RE: Feedback on immutabilityposted in Backup
@rtjdamen for the immutability to be useful, the full chain must be immutable and must never be out of immutability
the merge process can't lift/ put back the immutability , and increasing synchronization between process will extend the attack surface.
immutability duration must be longer than or equal to 2 time the full backup interval -1
the retention must be strictly longer than the immutability .for example, if you have a full backup interval of 7 a retention of 14 and immutability duration of 13 , key backup are K, delta are D. Immutable backup are in bold . unprotected chain are
strikedKDDDDDDKDDDDDD worst case, only one full chain protected
KDDDDDKDDDDDDK
KDDDDKDDDDDDKD
KDDDKDDDDDDKDD
KDDKDDDDDDKDDD
KDKDDDDDDKDDDD
KKDDDDDDKDDDDD best case almost 2 full chain protected -
RE: XO Rest APIposted in REST API
Yes, you can use JSON-RPC et REST APIs together for now
We will try to add support for CPU settings soon.
Also, expect things to accelerate in 2025 regarding the REST API.
-
RE: EOL: XCP-ng Center has come to an end (New Maintainer!)posted in News
@propsoft All clear now, thanks! We'll discuss it and see what we can do, but I think this is indeed something that you need to configure in your browser. There should be an option to force the browser to ask where to save the file.
