Object Storage or Block Storage for backups of growing 60+ GB?

[girish]

@d19dotca said in Object Storage or Block Storage for backups of growing 60+ GB?:

I’m curious though… is there a way to improve the tarball performance? Why is it so dang slow? I assume concurrency but what prevents concurrency from taking place when using tarball? @staff, any suggestions here? Anything I can do or any specific recommendations?

One idea might be to measure just uploading via other tools to see how much the performance difference is. While the tgz code uploader is slow, it's not substantially slower than native tools (from what I have tested). Try to do a tar cvf - upload of the same data directory as the app to the backup storage and measure.

[scooke]

@robi I checked most (all non-US ones, 4 US ones) and the Public radio button stayed greyed out.

[robi]

@scooke let's see what support says.. unless they have a status page where one can see a portion of their services being offline (which provides this public access to a private bucket).

[doodlemania2]

@scooke So I heard back from email based support - they turned public buckets on for my account!

[marcusquinn]

@d19dotca Thanks for your R&D sharing on this, just trialing it, and the 1 year deals save a lot of money compared to any other S3, including Wasabi.

Really like the UI/UK, much easier for anyone to work with than Wasabi too, as you don't need to create Policies in JSON like you do with other.

from me, definitely recommended for all home users, and most SME needs too!

@d19dotca said in Object Storage or Block Storage for backups of growing 60+ GB?:

Interesting. I decided to test something with a local Datacentre closer to my VPS called IDrive e2 (seems like a recent s3 competitor from mid-2022 which promises high speeds).

[d19dotca]

FYI, got an email today from IDrive which announced the public buckets for people looking for that, mentioning it here as I know a few people were asking about that feature.

They’ve also made some serious performance tweaks. I noticed before I was seeing it take about 55-75 minutes for a 30+ GB upload in tarball, and now it’s closer to 45-50 minutes for the same size (in fact possibly even larger of a file now to boot as I have a couple more apps deployed now too and email continues to grow larger).

[robi]

@d19dotca said in Object Storage or Block Storage for backups of growing 60+ GB?:

I noticed before I was seeing it take about 55-75 minutes for a 30+ GB upload in tarball, and now it’s closer to 45-50 minutes for the same

It may be related to lower traffic and usage over the end of year holidays.

[d19dotca]

@robi said in Object Storage or Block Storage for backups of growing 60+ GB?:

It may be related to lower traffic and usage over the end of year holidays.

Entirely possible although I was discussing with them in a support case about the general speed of things and they did say they had recently implemented a change to their service which should speed things up and in my experience it does seem to be improved.

[doodlemania2]

@d19dotca I also noticed an increase in performance. One thing I did notice though - my public buckets were part of the beta and included anonymous root "viewing" of sorts - it generated an XML file of the contents of each public bucket. A quick email to support and they had me turn the bucket to private, then back to public to correct. Something to check if you or someone you love may be an early public bucket adopter there!

[marcusquinn]

@d19dotca We're noticing some significant slowdowns with IDrive backup uploads now. (We have lots and lots of small files and over 1TB). Just wondering if you'd experienced anything that might seem like throttling?

[scooke]

@marcusquinn Oh oh... too good to be true?

[marcusquinn]

@scooke Maybe, trying their support.

[MooCloud_Matt]

@marcusquinn
idk what tech is behind their stack, but if it is just HDD with no NVMe for caching metadata or any kind of index.
100% that it will be slow if they grow too much.

[marcusquinn]

Changing strategy to Tarball and that seems to complete in a few minutes. Might just have to be the trade-off for our apps, that have lots and lots of small files. More S3 storage usage but faster to backup and restore, and more self-contained for each backup not relying on files from others.

[robi]

@marcusquinn yes, that is the more optimal format for object storage, plus incremental diffs.

We discussed elsewhere on the forum a hybrid option inbetween rsync by file and large tgz.

[marcusquinn]

Yeah, I'm gonna call this, any backups >100GB or >100,000 files is likely to get impractically slower for most budget S3 storage. Might be worth a note/tooltip in the settings to suggest tarball for Cloudron servers over these numbers.

TBH I think the compression and minimal numbers of files being uploaded, with a sensible retention policy, is going to offset any storage-saving from using rsync. Rsync is a nice idea in theory for smaller directories, but I feel the file count costs are higher than storage costs for local compression and uploading that for each backup run.

[d19dotca]

@marcusquinn I haven’t noticed that myself but been using tgz the whole time and it’s been quite fast overall so far.

[marcusquinn]

To confirm on my R&D inspired by this thread. We're happy now with:

• IDrive on the introduction offer pricing
• Tarball for the backup method
• IDrive and Tarball encryption
• 7 Daily, 4 Weekly, 12 Monthly retention policy

[vansens]

@marcusquinn how happy are you with idrivee2 these days? I started a trial on Thursday and all was working well, but since Friday I am getting errors left right and center. Opened a support call and it's with their back end team. I am waiting for a response from them, hopefully Monday.

[marcusquinn]

@vansens Still seems to be working. You followed the above settings? (I doubt Rsync will work)