Storj instead of Backblaze #30
Labels
No Label
Breaking
Domain
komu.boo
Domain
langrock.info
Domain
libre.moe
Involves
Documentation
Involves
Security
Involves
Testing
Kind
Bug
Kind
Enhancement
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Service
Drone
Service
Element
Service
Gitea
Service
Matrix
Service
Nextcloud
Service
Szuru
Status
Abandoned
Status
Acknowledged
Status
Blocked
Status
Duplicate
Status
Invalid
Status
Need More Info
Status
Won't Fix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: KomuSolutions/igot99issues#30
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Possibly migrating from Backblaze B2 to Storj DCS.
Storj is priced at just 4$/TB (with some additional segment fees) for storage, in comparison to Backblaze's 6$/TB + VAT.
While a decentralized backup might seem a bit risky, Storj appears to be very solid and has a good track record. According to them, they have never lost a single file.
Currently needing to evaluate if:
rclone
can be used, as in its P2P mode, it seems to only make 65 shards instead of 80Testing of a testfile (~90 MiB) showed consistency in MD5 sums regardless of using the Web UI or rclone.
Utilizing Storj would require a custom solution for managing lifetime of old/deleted objects: https://docs.storj.io/dcs/buckets/object-versioning
Closing this as
Abandoned
as workload required does not seem worth it.Further ideas: Scaleway Glacier for backups, as it's just 2€/TB, no minimum retention periods, cheap API calls, located in a literal bomb shelter in Paris