@farokh one backup job should leave one snapshot. this is the way. to differentiate from previous backup the data to be put in the delta, it has to refer to this snapshot. delete it and you get a full backup ongoing. if you have two snaps on your VM, either you have a manual one, or you have multiple backup jobs backuping this VM (check the backup tab of the VM ?)

@olivierlambert that is a discrepancy between what was planned ( a vm delta backup) and what we can do with the data available ( a full ) . In this case, it's only one disk that fell back to full We have to improve how to show the information with mixed state

Probably in a next release (before the end of the year ideally)

@yaroz it loosk like there is an issue with some error not stopping the job as expected, I am currently working on this In the meantime , you can restart XO , it will forcefully close all running jobs

I had to bring the VM offline and do a VM copy, now the new one can snapshot/backup.

@florent and @olivierlambert I think it can wait until XO6. I dont have sperate test servers at the office so if I need to spin up a test machine i may want to back it up for testing but not to cloud backup as its only test. Tagging would make this easy since you have tagging implanted. As a work around i could create separate backup jobs for those less important vms.

@Pilow This one should be doable, I am adding it to our backlog

different platform have different internal , and so different edge case. We are here to help to bridge the gap.

No problem, you are welcome!

@Pilow Double checked. There's no filter in place and no new VM.

@florent It seems the Type: delta display during Backup fell back to a full may just be a display issue as it does seem to run a full copy.

@olivierlambert not by me

Impossible to tell yet, more in few months.

thanks for advice, i'll keep my minIOs running

@Bastien-Nollet Thanks as always @florent

@CodeMercenary hello and thanks for this idea! We will discuss about it with @clemencebx and see what we can propose on new XO-6 design and workflow.

Sometimes it when asking questions as well as hallucinating ChatGPT, can respond with results based on old versions (not updated for an up to date code base). So if any past in development or experimental code branch, had its code and was mistakenly released. Then the mistake was found and fixed, it can have found its way into the training data set. Can also be an example of training data set poisoning, forcing it to give misleading or mistaken responses, due to it hallucinating as a result.

Thanks everyone for their help. I believe I have a way forward now.

Thank you everyone for your feedback, really appreciated!

That sounds interesting, the backups are on a new remote on a new Minio-instance so the issue is handled for now. I guess we will see over time if the backup times increases.