Indeed, it's hosted in Lyon, so an issue could happen in many places in the middle ^^

@LoTus111 Hello, I attempted to reproduce the issue without success. Could you please share the logs with us so we can conduct a deeper investigation? Feel free to send them to me via PM.

@pierrebrunet thanks for quick insight/fix, got back to stable to deploy templates, it is working

@Bastien-Nollet many thanks

@Pilow error reporting is a feature in itself . Thanks

@Pilow I will take a look in deep later, but the key/delta and disk usage is set during backup, even if they are merged during LTR retention

But giving your feedback on how you solved it might help many people in the future Thanks!

still having initial issue, even on latest XOA or XO CE

Adding @florent and/or @Bastien-Nollet in the loop

Adding @gregoire in the loop

Adding @clemencebx for review/ideas on this;

I think it's planned for XO 6 adding @gregoire in the loop

@Pilow You might be right, this may be simpler to implement than we imagined. We'll keep you informed when we progress on this.

@Bastien-Nollet nice !

Thanks @Pilow for the test

@Pilow alright, cool! that sounds pretty much like a standard solution, too much options or details usually just confuses the end users

@acebmxer said in Veeam backup with XCP NG: and when not accidentally routing the backups... save 6 min.. [image: 1759373010653-screenshot-2025-10-01-224148.png] host [image: 1759373021630-screenshot-2025-10-01-224223.png] Amazing, that's really impressive. Backups has always taken a long time with XOA once you start to backup a lot of VM's so I hope this will improve the overall backup performance

Adding @pdonias in the loop

@olivierlambert yes Olivier. but I'm in doubt of the correct redirection I have to make in NPM ... Should I port the token part of the url also in the redirected internal part ? or do I miss an nginx parameter to help pass this token 'inside' ?