I keep important files on my NAS, and use Borgbackup with Borgmagic for backups. I’ve got a storage VPS with HostHatch that’s $10/month for 10TB space (was a special Black Friday deal a few years ago).
Make sure you don’t just have one backup copy. If you discover that a file was corrupted three weeks ago, you should be able to restore the file from a three week old backup. rsync and rclone will only give you a single backup. Borg dedupes files across backups so storing months of daily backups often isn’t a problem, especially if the files rarely change.
Also make sure that ransomware or an attacker can’t mess up your backup. This means it should NOT be mounted as a file system on the client, and ideally the backup system has some way of allowing new backups while disallowing deleting old ones from the client side. Borg’s “append only” mode is perfect for this. Even if an attacker were to get onto your client system and try to delete the backups, Borg’s append-only mode just marks them as deleted until you run a compact on the server side, so you can easily recover.
rsync over ssh (my server is in the next room) which puts the backup on an internal drive. I also have an inotify watch to zap a copy from there to an external USB drive.
For a long time I did 1 hot copy (e.g. on my laptop), 1 LAN/homelab copy (e.g. Syncthing on a VM), and 1 cloud copy … less a backup scheme than a redundancy scheme, albeit with file versioning turned on on the homelab copy so I could be protected from oopsies.
I’m finally teaching myself duplicity in order to set up a backup system for a webdev business I’m working on … it ain’t bad.
Cheap second NAS that I power up every now and again, then I run a dsynchronize profile which replicates the important stuff (video), and all the stuff I could never replace I put on a usb and keep it elsewhere
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I keep important files on my NAS, and use Borgbackup with Borgmagic for backups. I’ve got a storage VPS with HostHatch that’s $10/month for 10TB space (was a special Black Friday deal a few years ago).
Make sure you don’t just have one backup copy. If you discover that a file was corrupted three weeks ago, you should be able to restore the file from a three week old backup. rsync and rclone will only give you a single backup. Borg dedupes files across backups so storing months of daily backups often isn’t a problem, especially if the files rarely change.
Also make sure that ransomware or an attacker can’t mess up your backup. This means it should NOT be mounted as a file system on the client, and ideally the backup system has some way of allowing new backups while disallowing deleting old ones from the client side. Borg’s “append only” mode is perfect for this. Even if an attacker were to get onto your client system and try to delete the backups, Borg’s append-only mode just marks them as deleted until you run a
compacton the server side, so you can easily recover.rsync over ssh (my server is in the next room) which puts the backup on an internal drive. I also have an inotify watch to zap a copy from there to an external USB drive.
Proxmox backs up to pbs and pbs is synced to B2 with rclone.
Other stuff is restic to b2.
Backblaze. Automated with Velero in kubernetes.
deleted by creator
Usb drive
For a long time I did 1 hot copy (e.g. on my laptop), 1 LAN/homelab copy (e.g. Syncthing on a VM), and 1 cloud copy … less a backup scheme than a redundancy scheme, albeit with file versioning turned on on the homelab copy so I could be protected from oopsies.
I’m finally teaching myself
duplicityin order to set up a backup system for a webdev business I’m working on … it ain’t bad.I use borg
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
[Thread #188 for this sub, first seen 5th Oct 2023, 00:05] [FAQ] [Full list] [Contact] [Source code]
deleted by creator
Right now just a spare hard drive on a pi that I rsync too, but I’m looking for better options as well.
Cheap second NAS that I power up every now and again, then I run a dsynchronize profile which replicates the important stuff (video), and all the stuff I could never replace I put on a usb and keep it elsewhere
deleted by creator
Manually plug in a few disks every once in a while and copy the important stuff. Disks are offline for the most part.