Index of files stored in git pointing to a remote storage. That sounds exactly like git LFS. Is there any significant difference? In particular in terms of backups.
Git LFS is 50k loc, this is 891 loc. There are other differences, but that is the main one.
I don't want a sophisticated backup system. I want one so simple that it disappears into the background.
I want to never fear data loss or my ability to restore with broken tools and a new computer while floating on a raft down a river during a thunder storm. This is what we train for.
Actual invocation is this huge hairy furball of an rsync command that appears to use every single feature of rsync as I worked on my backup script over the years.
Support for S3 means you can just have minio server somewhere acting as backup storage (and minio is pretty easy to replicate). I have local S3 on my NAS replicated to cheapo OVH serwer for backup
Index of files stored in git pointing to a remote storage. That sounds exactly like git LFS. Is there any significant difference? In particular in terms of backups.
Definitely similar.
Git LFS is 50k loc, this is 891 loc. There are other differences, but that is the main one.
I don't want a sophisticated backup system. I want one so simple that it disappears into the background.
I want to never fear data loss or my ability to restore with broken tools and a new computer while floating on a raft down a river during a thunder storm. This is what we train for.
Is this a joke?
I don't see what value this provides that rsync, tar and `aws s3 cp` (or AWS SDK equivalent) provides.
How do you version your rsync backups?
I use rsyncs --link-dest
abridged example:
Actual invocation is this huge hairy furball of an rsync command that appears to use every single feature of rsync as I worked on my backup script over the years.
3 replies →
Dirvish
1 reply →
Uh, who has the money to store backups in AWS?!
Glacier Deep Archive is the cheapest cloud backup option at $1USD/month/TB.
Google Cloud Store Archive Tier is a tiny bit more.
Both would be pretty expensive to actually restore from, though, IIRC.
1 reply →
To quote the old mongodb video: If you don't care about restores, /dev/null is even cheaper, and its webscale.
Depends how big they are. My high value backups go into S3, R2, and a local x3 disk mirror[1].
My low value backups go into a cheap usb hdd from Best Buy.
1. https://github.com/nathants/mirror
Support for S3 means you can just have minio server somewhere acting as backup storage (and minio is pretty easy to replicate). I have local S3 on my NAS replicated to cheapo OVH serwer for backup