Developers of Xen Orchestra
As the named are greyed-out, could you confirm that the delta backup job saves the backup to remotes srv04-incremental and srv12-incremental, and the mirror backup job copies the backups from srv12-incremental to srv04-incremental? (or at least confirm these are the same couple of remotes)
Also, could you tell me if the VM with which you got the "No new data to upload for this VM" message was backed up by your backup job "Incremental backup every 4 hours - 8 days retention"?
@henri9813 yes thank you for correcting my message
Thanks @Forza,
I'll try on my own with a similar configuration.
I confirm that this is the current behaviour, as @pilow reported here https://xcp-ng.org/forum/post/99446
We might change it in the future to make it better, but it won't be trivial to change.
@ph7 Thanks for all the feedback! We took notes of everything, and we're already fixing some of them 
@jr-m4, @probain and @acebmxer We were eventually able to reproduce the VDI name bug, we'll fix that!
@Davidj-0 said in 
️ XO 6: dedicated thread for all your feedback!:
Should we add this to https://docs.xen-orchestra.com/installation#installing-dependencies ? Or will it not be necessary after the next release?
It won't be necessary after we merge this PR, which should be very soon.
Hi @Forza,
Could you send us a screenshot of your backup job configuration so we can try to reproduce?
@jr-m4 Thanks for the feedback! I tried to reproduce that but I don't seem to get the same behaviour. Let me make sure I understood:
Could you confirm that?
@marcoi Thanks @acebmxer for answering, we'll make a change very soon so that you no longer have to do that.
@pilow Our precise backlog is private but here's the short-term roadmap:
@ph7 If we answered your other messages, most likely we have it in our backlog. But just to make sure we're not missing anything, you can indeed put the links here and we'll check them. Thanks again!
you can uncheck the "Merge backups synchronously" in the advanced view of the backup job to have it run inside the backup job, thus making it visible
(we are reworking the internal design for better observability, but there is a lot of job before)
Hi @k11maris,
I think the situation you showed in your screenshot where both options are selected but are both greyed out should not happen.
We will try to reproduce it on our side and fix it.
End of November:
XOA admin users on the latest channel will see a new option in the left-hand menu to access XO 6. XO 5 will remain the default interface, but you can begin testing XO 6 whenever you like.
Users running XO from source will transition to XO 6 by default, with a link in the interface to return to XO 5 when needed.
End of December:
XOA's latest channel will also move to XO 6 as the default interface. XO 5 will also remain accessible whenever you need it.
Stable channel will remain on XO 5 by default.
