What does the 3-2-1 rule look like for you?
-
NAS (42tb RAID5), 2x 18tb spinning drives, 5tb SSD as daily driver, proton drive for critical stuff (2tb).
Not exactly 3-2-1 but it covers the same roughly
-
DO NOT follow my lead, my backup solution is scuffed at best.
3:
I have:
- RAID1 array w/ 2 drives
- Photos on the device that took them
- Photos on a random old hard drive pulled from an ancient apple mac.
2:
I've got a hard drive and flash memory?
1:
Don't have this at all, the closest is that my phone is off-site half of the day.
-
Real selfhosters know
-
I've never heard of Borgmatic before... How's it work?
-
3 backups:
- phone data is synced to a nvme drive (1) which holds all the data of my homelab
- This nvme is backed up to a nvme (2) drive on the same device via backrest
- The nvme is also synced via Diplicati to a cloud storage provider (3)
2 locations:
home and cloud1... what was 1 again?
-
My main server is backed up via Kopia to a 5 TB Hetzner Storage Box and to a second server at my parents in law‘s place. I‘ve got additional MDisc backups of old photos, Paperless PDFs and work related files that don‘t change at my mother‘s place as well.
My Linux ISO collection is too big to actually back up. So, I regularly create file lists and in the event of data loss, I will have to spend quite some time to rebuild it. At least, my fiber connection will help me with that.
-
- Maintain three (3) copies of your data: This includes the original data and at least two copies.
- Use two (2) different types of media for storage: Store your data on two distinct forms of media to enhance redundancy.
- Keep at least one (1) copy off-site: To ensure data safety, have one backup copy stored in an off-site location, separate from your primary data and on-site backups.
You have 3 copies, one on your phone and nvme, one on the backup nvme and one in the cloud.
You have 2 media, internal SSD and cloud (your phone would count as a third if it wasn't auto synced)
You have 1 off-site in the cloud -
1 backup on a local, Independence disk.
1 backup on a HDD connected to an OpenWRT router at the other end of the house
1 backup on my remote vps.Restic+backrest
Sftp for remote endpoint
-
My nas is a second copy of all my data, nothing only exists on the nas. The nas is also is slowly uploading to backblaze, data limits are slowing my progress. My photos which I feel are the least replaceable are automatically backed up to my nas , Google photos, and amazon photos, with manual backup to my desktop, and manual backup to an external hard drive that is stored in a fire resistant box.
-
my backup is staring longingly at LTO drives and wishing they would magically be affordable.
-
- Primary ZFS pool with automatic snapshots
- Provides 3+ copies of the files (3)
- Secondary ZFS pool at a different location replicates the primary
- Provides more copies of the files (3)
- Provides second media (2)
- Is off-site (1)
Does this make sense?
- Primary ZFS pool with automatic snapshots
-
I might be the weird one, but I never consider the phone copy as valid for 321. I have so many photos that they don't fit, so most are already not there anymore.
Server/htpc + desktop (with delay, I turn it on sparsely) + b2
-
- Daily incremental (and occasionally full) backup to an external HDD - a full image of my PCs, so that I should be able to restore anything back to what it was in the last ~14 days, assuming no ransomware or fire or...
- All the data I care about gets synced to my Nextcloud (VPS, not home lab) - somewhat ransomware protected as I could restore VPS backups independently from my PC.
- Most precious data (mostly photos) gets backed up regularly to an encrypted zip file and then gets send to a glacier tier S3 bucket. Some manual retention is done on the zip file level, so that I can get a tad older backup restored.
- At least monthly a full backup image of my PCs is created on a separate external HDD which is not stored at home, but in a place I could access 24/7 if I really needed to restore something fast.
Phones, etc? Just sync to the mentioned Nextcloud, PC downloads from there and everything gets then into the aforementioned backups.
Homeserver? See "PC" above. With the caveat that some VMs/containers are not in the backup cycle, as they do not store any valuable data besides temp files, etc. For these, only things like docker compose files, custom config, ansible playbooks,... are in my backup.
-
I don't think this meets the definition of 3-2-1. Which isn't a problem if it meets your requirements. Hell, I do something similar for my stuff. I have my primary NAS backed up to a secondary NAS. Both have BTRFS snapshots enabled, but the secondary has a longer retention period for snapshots. (One month vs one week). Then I have my secondary NAS mirrored to a NAS at my friends house for an offsite backup.
This is more of a 4-1-1 format.
But 3-2-1 is supposed to be:
-
Three total copies of the data. Snapshots don't count here, but the live data does.
-
On two different types of media. I.e. one backup on HDD and another on optical media or tape.
-
With at least one backup stored off site.
-
-
I use Backblaze B2 for one offsite backup in "the cloud" and have two local HDDs. Using restic with rclone as storage interface, the whole thing is pretty easy.
A cronjob makes daily backups to B2, and once per month I copy the most current snapshot from B2 to my two local HDDs.
I have one planned improvement: Since my server needs programmatic access to B2, malware on it could wipe both the server and B2, leaving me with the potentially one-month old local backups. Therefore I want to run a Raspberry Pi at my parents' place that mirrors the B2 repository daily but is basically air-gapped from the server. Should the B2 repository be wiped, the Raspberry Pi would still retain its snapshots.
-
Wow, a lot of variation in this thread!
I get all my data to my server, then from there I have borgmatic do incremental backups to a backup drive on the same machine (nightly cronjob).
From there I use Rclone to get the encrypted borg backup to Backblaze B2 for cloud storage.
So for 3 2 1, my 3 copies are the original, the local backup, and the cloud backup.
My 2 media are local hard drives and cloud storage (I think it's fair to consider this a different kind of media).
And my 1 offsite is the cloud backup.
Now I'm dumb and have a fear of screwing something up so I have also started burning M-Discs of my critical data (everything except TV/movie/music stuff I can redownload). Though this was a lot more expensive than I was expecting, because of aforementioned me being dumb I already screwed up two discs (they are write once). I'm also doing two copies of each disc.
Also I have photos/home videos additionally stored in ente, they are super important to me and I wanted a separated copy someone else is looking after.
-
Its an automation software for borg backup to run on a schedule and keep a certain number of backups while deleting old ones etc.
-
My one other media type is “the cloud”.
I use hard drives, I can’t imagine trying to put something on a disk or something.
One thing I do recommend, I keep one unencrypted hard drive copy in the safest most hidden part of my house. This is in case encryption software disappears, or I just forget my encryption keys or something.
Other than that, one encrypted copy of files in a thumb drive in my wallet (selected files, not everything). One in my car. One in my firesafe. Then daily cloud backup.
-
My main storage is a mirrored pair of HDD. Versioning is handled here.
It Syncthings an "important" folder to a local back up only 1 HDD.
The local Backup Syncthings to my parents house with 1 SSD.
My setup can be better, if I put the versioning on my local backup it'd free space on my main storage. I could migrate to a dedicated backup software, Borg maybe, over syncthing. But Syncthing I knew and understood when I was slapdashing this together. It's a problem for future me.
-
@lka1988 @Lem453 Primarily a frontend tool designed to make your life easier, torsion.org/borgmatic , but I tend to avoid macros, frontend scripts, or even GUIs like this. They may obscure Borg-specific configuration details that, hypothetically, could one day hinder your restoration process.
