2026-10-17 04:14 UTC
Replies (14)
-
@fuckwit_mcbumcrumble@lemmy.dbzer0.com 2026-10-17 04:22
As long as I have space. My backups are on dedicated drives, and as they run out of space the old ones are deleted.
-
@ISOmorph@feddit.org 2026-10-17 04:27
I backup once a week. I have 3 backups. Everytime a new one is created, the oldest is deleted. I figured if I need to roll back something, 3 weeks is more than enough to notice.
-
@Sibbo@sopuli.xyz 2026-10-17 04:59
I have daily backups, weekly, monthly and yearly. All but yearly is deleted after a certain time, but yearly I keep forever.
-
@Reannlegge@lemmy.ca 2026-10-17 05:32
I was backing up multiple places on my LAN but than half of my place flooded, so lamenat and carpet was ripped up, one of my pi 5’s was misplaced with a NVMe drive and another was lost. Than just down the street 3 house went up in flames had the wind been blowing just a little south my condo complex would have been burnt to the ground. After the fire fighters were telling us to get back further and further I had my main pi 5 that had all the backups of everything important on another NVMe drive and a few other things ready to go if the firefighters started banging on my door telling me it was time to leave. I wish I could honestly say that was the day I decided to get a VPS and start my back up, but I was still hoping my father would let me set up a pi with a drive big enough to do back ups at his place. It sounds like he will but he is concerned about security risks about my VPN, funny thing is my back up pi would be the most secure thing hooked up to his modem/router and I wouldn’t want his stuff touching my stuff and with how my LAN and VPN are set up they would have a hard time doing it. Anywho I have a domain hosted by EasyDNS, and just went and looked at their VPS options and got some year long plan and set up cron jobs to take the stuff I want to backup and use age to encrypt it and than it is sent to my VPS each age container is than deleted after there is something of the same name but 3 days iterations older and deletes it.
-
@Zwuzelmaus@feddit.org 2026-10-17 06:04
How long do you keep your backups? Yes, I have that exernal HDD lying around somewhere near the PC, and it was at least 4 or 5 times that I backed up a lot of files on it. I think I keep it for more than 10 years now.
-
@Treczoks@lemmy.world 2026-10-17 07:56
Let me put it this way: I have a removable harddisk with my files from the universities’ VAX 11/780 in storage. Long enough?
-
@NoLemurs@lemmy.world 2026-10-17 09:00
[forget] keep-daily = 10 keep-weekly = 4 Daily backups are cheap because of de-duplication. I keep a few weekly backups in case it takes me a bit to notice something went wrong. I don’t usually back up logs. I could probably drop the weekly backups without much risk, but I’ve got the space.
-
@non_burglar@lemmy.world 2026-10-17 14:10
Daily for 10 days, 4 weekly, 4 monthly. That covers me from broken updates, generally.
-
@miaowoo_lw@lemmy.world 2026-10-18 04:22
The useful split isn’t by time, it’s by data class — your “churn that isn’t real data” observation is the key: Separate repositories for real data vs. app state. Databases, logs, container images, caches in one repo with aggressive expiry; documents, photos, configs in another with long retention. Then “how long” becomes easy per class instead of one uncomfortable compromise. For the churn class, a sane baseline with restic: restic forget --prune --keep-daily 7 --keep-weekly 4 --keep-monthly 6 --keep-yearly 2 Reasoning: most restores are “it broke today/yesterday” — dailies cover those. Weekly+monthly exist for “the corruption was already there and I didn’t notice” (ransomware, a bad deploy 5 weeks ago, silently-degraded RAID). Yearly is only worth it for truly irreplaceable data. Two things worth checking on the borgbase side: Prune actually runs — restic forget without –prune (or borg prune vs borg delete semantics) marks snapshots but never frees repo space. Plenty of people run forget for years and wonder why the repo is full. Restore tests, not just snapshots — quarterly, restore into a scratch VM. A backup that’s never been restored is a hypothesis. “Keep forever” mostly comes from cheap snapshot storage, but with churn-heavy data old daily snapshots are exactly where dedup saves you the least — the churn is your storage cost there.
-
@Greenbeard@lemmy.zip 2026-10-18 04:51
Backups?
-
@JustARaccoon@lemmy.world 2026-10-17 12:47
7 backups, though the frequency they’re taken (daily Vs weekly Vs monthly) depends on the service. Why don’t you exclude logs from your backups? databases sure yes that’s where the real info is (not sure why you don’t consider it real data) but logs are useless outside of the current running instance.
-
@ShortN0te@lemmy.ml 2026-10-17 21:39
As of now, i keep them basically for ever, but granularity gets less over time. (restic forget) Before you go nuts about files you want to exculde the “churn” as you said it, go ahead and actually check how much space this actually takes up. Text and especially logs are highly compressible and will most likely end up taking up almost no space. Be sure you backup everything you actually need, rather backup a file more then a file too less.
-
@lka1988@lemmy.dbzer0.com 2026-10-19 03:25
I just rsync a full backup of my NAS’s entire RAID array every week to a separate machine. I have Proxmox set up with an NFS mount to the NAS where it stores all of the /data volumes that my Docker VMs and LXCs and such use (Proxmox itself is hosted on 3x office PCs, each with i7-7700/500GB SSD/32GB RAM). I don’t bother backing up the containers, so I just document which ones I’m running on occasion.
-
@krypto@lemmy.ml 2026-10-19 06:29
I know I’ll get shot for this, but I stopped backing up a long time ago. I was doing it at home because I do it at work and it’s the done thing. But when I stopped to think about it, I realised I don’t have anything at home that actually matters. If I lose my Plex library it’s ok.