@olivierlambert Indeed. That would possibly be a way. I fully understand stand it is tricky to do without making the interface esoteric

@olivierlambert Ja, or better to say the inverse of NOBAK i.e. only backup THIS disk.

Hi there,

we are running XPC-ng and XOA for years and are very happy. Especially since the S3 backend became rock solid (big THANKS!!!) and is getting increasingly faster.
We put our DR backups there and it works like a charm - the health check is also fantastic.

We have one use case though were I am not sure how to do it:

We have an Exchnage server VM with three disks: system 200G, data 500G (user mailboxes), arch 900G (archived user mailboxes).

We exclude the arch disk with [NOBAK] (our connection is not that wide) - with that the backup takes roughly a day.

Now, I wonder whether there is a way to exclusively backup the arch disk from time to time.

Of course I can play atound with the [NOBAK] label, but I'd prefer things to be automated as far as possible.

Kind regards
W. Richter

Hi,

as many I am very much looking forward to natively bakup to S3 using XO.
However, with 3.65 it still doesn't work.
I am getting the following error when backing up to a S3 remote:

Error: Chaining alias is forbidden xo-vm-backups/82684429-7c62-4342-43a6-ffd1910948cf/vdis/1ad81c16-219b-439c-8afc-0ffb7edda3e1/36a05856-90f4-483b-b251-c1c2fa833128/20211201T082244Z.alias.vhd to xo-vm-backups/82684429-7c62-4342-43a6-ffd1910948cf/vdis/1ad81c16-219b-439c-8afc-0ffb7edda3e1/36a05856-90f4-483b-b251-c1c2fa833128/20211201T082244Z.alias.vhd

Do is miss certain settings on the target bucket?

Kind regards