What is the problem you are having with rclone?
Problem is trying to decide on how rclone interacts with dfferent types of backups and therefore how this will effect the cost of using certain provider AWS, Wasabi and Backblaze b2
that's what I want to figure out
Hi all, I'm new to online backups and have traditionally used a very basic system of onedrive to backup important files on my pc's. I now run a business and use Restic to make weekly backs ups from each of my computers to a removable drive. I now want to complete my backup process by having a cloud back up of my restic repos. Currently I have 3 Restic Repos that I update weekly, each repo is around 150GB and has around 20,000 files in each repo.
My plan is to use Rclone once per week to sync the updated repos up to a cloud provider (AWS, Wasabi or Backblaze b2). My concern is api call and early deletion costs. If using AWS then based on Storage costs it only makes sense to use Glacier class which has a 90 day early deletion period and api call costs. Wasabi also has a 90 day early deletion period but no api call costs, backblaze has no early deletion period but api call costs. Ideally I would prefer to use AWS directly, cutting the middle man as it were.
My understanding of Rclone sync is that it will make 240,000 API calls to check the data (20,000 files per repo x 3 caried out 4 times per month) then depending on how many files need updating a put for each updated file and a delete call for the original file that was updated. Because Restic repos are encrypted my guess is that this will be a really high number of changes to the files so my guess is in total could be around 1million api calls per month? I know I can use
--fast-list to limit the calls but here would still be a large number of changes needed? So that is one consideration for cost and points to Wasabi being the favourite option.
However, next is the early deletion costs, syncing 60,000 files, 4 times per month, will mean a lot of early deletion costs. If the repos are changing each week, my understanding is the rclone sync would be deleting and replacing a lot of the destination repo files every time I run a sync, so I would very high have monthly early deletion charges. If the data is being overwritten every month, then my understanding is that the the early deletion costs of using AWS Glacier and Wasabi just make them absolute non-starers? It appears to me that this type of backup strategy of weekly updating incremental backups simply cannot be run on Glacier and Wasabi due to early deletion limitations or am I missing something?
The cost estimate for s3 standard 500GB with 600k api calls is around $15 per month. Backblaze B2 is $5 for 1TB plus around $5 in call costs (1million per month).
These costs seem pretty high to me for disater back up data that I will hopefully never have to access so I'm really thinking that I must have this wrong somehow? It cost me about half that for 1TB of onedrive space that automatically syncs for me with no worry about api call costs or deletion fees, so I'm now thinig I really must have this all wrong. All I need to do is zip my repos to container and replace them on onedrive (any alternative such as sync.com) and it is all taken care off at half the price, so what am i missing. I really want to be able to get a good, cost effective cloud backup solution but think I am have gone wrong somewhere in my understanding and calculations of how it all works.
I would really appreciate if someone could help explain where i am going wrong with my understanding and pricing estimates.
Edit: Just to expand on this a little further, even if I just decided to buy 2TB on aws Glacier with 4 calls per month, just to upload complete copies of the repos and then delete after the deletion period it would still costs more than the ondrive/sync.com example. AWS would cost around $10 per month while sync.com is $8 for 2TB and all syncing taken care off. This can't be right?