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

[robi]

@doodlemania2 I think that's a setting before you create the bucket.

[scooke]

@robi Unfortunately it is so. Not sure when they will enable the setting.

[doodlemania2]

@scooke anyone know a contact? Would like to stay with them but no public buckets...lol - maybe they can bit flip it for me?

[doodlemania2]

went with their main tech support email

[robi]

@scooke all regions?

[d19dotca]

Noticing that tgz of about 35-40 GB GB (well that’s the size after compression, it’s really compressing closer to 60+ GB uncompressed data) and it’s nearly double what it consumes in storage because at least the first backup has that snapshot directory too which is a duplicate of the latest backup. My IDrive e2 bucket shows a total usage of 70 GB currently after one system backup.

I notice if I use rsync the backup times are anywheres between about 20-70 minutes, however when using tgz it’s closer to 120 minutes. That’s about the same performance when using Wasabi and even better than Backblaze in my tests so far.

The downside to rsync is it takes forever to delete so many (tens of thousands of) different files from s3 storage, which means Cloudron cleaning it up or even just me doing it manually to purge older data is a real time sink. Makes me want to use tarballs instead however the upload rate seems to be much less performant. I suppose it is maybe a moot point to some degree because it’d normally be done in the middle of the night when time isn’t really a factor, although it will mess things up for two hours during Cloudron version updates if I (which I would) do system backup prior to that task as the maintenance would be so much longer.

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?

I should note I’ve seen next to zero improvements or changes at all whether I use a part size of 128 MB or 1 GB, doesn’t seem to change anything performance wise.

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