Hi @Pilow,
We might improve this in the future, but for the moment you'll have to create two different schedules, one for the day with healthcheck, and another one for the six other days. Then, create two different sequences, one for each schedule.
Developers of Xen Orchestra
Hi @Pilow,
We might improve this in the future, but for the moment you'll have to create two different schedules, one for the day with healthcheck, and another one for the six other days. Then, create two different sequences, one for each schedule.
Hi @Pilow,
We plan to make LTR available also for mirror backups and metadata backups in the future, but we didn't have the time to do it yet.
Smart mode on mirror incremental backups would be a bit tricky to do, as it would require us to handle incomplete chains of backups, for cases when a tag is removed from a VM and then added back. We might still implement it in the future, though.
About the bug you noticed about VMs showing in backup log despite being excluded, I think it was intentional at some point, but now it would make sense to remove it. Thanks for the feedback, we'll change this.
Hi @Pilow,
This is a great idea, we'll plan it so it gets implemented in the future.
@MajorP93 the config should be in ~/.config/xo-server/ of the user running xo-server
It is noted
@Pilow said in Long backup times via NFS to Data Domain from Xen Orchestra:
@florent what if we use XO Proxies ?
te the conf should be on the proxy is /etc/xo-proxy/
A fix has been merged on master, now the LTR should properly pick the first backup of each day, week, month and year instead of the last one: https://github.com/vatesfr/xen-orchestra/pull/9180
@MajorP93 this settings exists (not in the ui )
you can create a configuration file named /etc/xo-server/config.diskConcurrency.toml if you use a xoa
containing
[backups]
diskPerVmConcurrency = 2
@MajorP93
interesting, Note that this is orthogonal to NBD.
I note that there is probably more work to do to improve the performance and will retest VM with a lot of disk
Performance is really depending on the underlying storage.
compression and encryption can't be done in "legacy mode" , since we won't be able to merge block in place in this case.