Use Duplicati for daily backups #48
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#48
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?
A 1TB Hetzner Storage Box costs 3.81€ per month and can be used by all servers and also includes the ability to make snapshots.
Backblaze B2 is a great service but due to storage constraints on the server itself, I mainly use
rclone rcat
in pipes to export data directly to B2, which unfortunately can fail if B2 dispatched a server with not enough storage for the file - which can happen asrcat
doesn't know what size the file is going to be as it's generated during uploading in the pipe. In the case of a failure, the script will simply not do anything.Also, some services hold large amounts of data (>1GB), which means tarred backup to B2 multiplies the cost by 7 for 7 days retention, even if nothing changed. I do this to be able to an atomic roll back to an earlier version. For some services I decided that was too much storage and therefore just sync the folders directly 1:1, meaning deleted/changed data from the source is kept through Blackblaze's versioning, but previous versions need to be rolled back manually - easy if you know what you are looking for with Szurubooru or Nextcloud, but not really with Gitea :).
Syncing the local data to a Storage Box will keep storage usage low, enables easy roll back through automatic ZFS snapshots and - if there isn't maintenance being done at that moment - shouldn't fail as there is nothing to dispatch.
Monthly atomic backups are still made to Azure with high redundancy, so Hetzner burning down / disabling my account is accounted for. A simple sync to Backblaze would also be easily possible and stop daily backups from failing due to 503 errors, as they can be uploaded from the storage box - with known, predictable file sizes and possibilities to retry.
This would also allow @leon to back up Matrix onto it.
On the other hand, Backblaze currently costs at most <0,50€, solving a problem that at worst increase it to <1,50€ by purchasing something that always costs 3,81€ is kinda stupid. This needs some more thought.
Use Storage Box for daily backupsto Evaluate Storage Box for daily backupsUsing a backup service like Duplicati, that can make incremental backups to object storage and also restore easily (and even through a UI) sounds like a smarter choice.
If these fail, there are always the atomic and simple backups to Azure so...
Duplicati is probably the way to go
Evaluate Storage Box for daily backupsto Use Duplicati for daily backupsClosing this as not planned, as I changed the backups for larger volumes to a
rclone sync
instead of creating an atomictar
-archive.While not being an optimal solution, it works good for the time being and the services hosted. Might re-open later.