@utopianfish Or look for deals in places like amazon.com or bestbuy.com or even Ebay.com.

@peo without deleting, the CBT can fail, but XO can still compute the changed blocks before previous release, the fallback was hidden if you didn't look at the size the CBT issue is on the hypervisor storage side . But at least , the replication issue is fixed, we are back to the good old issues

Hmmm that's a possibility. An interesting lead to explore. Ie trying to do it yourself to see if the result if the same?

@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.

@acebmxer Hello, We’re aware of the Backblaze rate limits and this isn’t the first time it’s been raised. We’ll be looking into this on the XO side, studying different options such as caching restore points to reduce API calls. Longer-term improvements, possibly tied to advanced XO6 dashboards, are more of a 2026 horizon. Thanks for bringing this up!

Partly, I will see when back from vacation Anyway, unrelated to XO

@jimmymiller i just noticed one of your pics of the backup had NDB enabled. (says exporting content of VDI shifter through NBD. Can you check in your backup job if NDB is on? [image: 1755550405681-f90df5d8-81e6-4404-ba28-c337c0702aad-image.png] I would turn it on and off a few times and leave it off then save the job and retry. There was issues with NDB gui in prior version that might be still affecting your test backup job.

@cairoti you should be able to add it as a remote ( not as a storage repository on xcp-ng)

@Danp Thanks... Just ticked that off and they are migrating. I'll try backup again but something tells me the backup issue will still persist. I'll send logs once that fails.

@Nephilim ?Yes I also did save mine. However, it seems to be useless trying to import it into the 8.3 release. Having to set up my pool interfaces and storage again would be pain in the but. for me.

Good luck and keep us posted!

@arovella74 said in Definition backup full & incremental.: Our S3 bucket fills up with objects. Set up retention and deletion rules on your bucket so your bucket is cleaning this out. @arovella74 said in Definition backup full & incremental.: We want a full backup to be performed every two incremental runs, so we can keep the S3 bucket in check. Without more details I'm not sure how you could do that, besides alternating schedules, specifically run an incremental bi-weekly (for simplicity) and then run a full every 3 Saturday.

Hi, It goes via XOA, which is piping the export of host A to host B import.