Right now I’m creating a nightly restic snapshot of my server on borgbase and on some spare drives, and keeping the snapshots forever. There’s a ton of daily churn in my data though, between databases and logs and other files that don’t constitute ‘real data’ but might be needed to restore the app.
Always last daily, weekly, monthly. The others are pointers (hardlinks). How many years, i’m not there yet.
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.
I just
rsynca 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/[userdata]volumes that my VMs and LXCs use; Proxmox itself is hosted on 3x office PCs, each with i7-7700/500GB SSD/32GB RAM, and set up for replication in case one goes down. On occasion I’ll actually document which services I’m using, so I don’t really bother backing those up since the userdata itself can be remapped to a new instance.Most of what I would use proxmox for doesn’t even require backing up. A copy of each VM when it is setup and possibly update that every few years would be plenty.
I think you can export the whole VM? Using virtualbox currently which has import/export appliance. Doing that on an infrequent basis is pretty much what I would need.
Proxmox has backup stuff for VMs and containers which uses whatever storage youbadd (local, NFS,), and has retention settings. iirc those will always be full backups. for incremental and more, proxmox backup server (PBS VM using backupNAS as destination for me)
where we’re going, we don’t need backups!
For frequently changing data hourly up to 24, daily up to 7, weekly upto 4, monthly up to 12.
For daily changing data daily up to 7 and etc. as above.
For seldom changing data a backup every 3 days with rotation based on a storage quota, and retention of manually held samples.
Backups?
Removed by mod
Removed by mod
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.
I use nightly backups. I keep them 2 weeks.
After that I keep a weekly backup for 2 months.
After that I keep a monthly backup for 2 years.
I keep my yearly backups forever.
Daily for 10 days, 4 weekly, 4 monthly.
That covers me from broken updates, generally.
came to say something like this but not sure why you would do daily for 10 days. Your doing weeklys so why not 7. I would rather increase the monthly to 7 or do 6 bi monthly and keep a yearly.
Your doing weeklys so why not 7
They are all daily backups, those schedules I pointed out are for pruning. And I don’t understand the question… How would keeping 7 instead of 10 dailies help me?
because your last weekly would be a max of 7 days out
How am I going to restore day 8, day 9, or day 10 backups if I only keep 7 days?
How do you restore on day 11, 12 or 13 if you only keep 10 days?
I don’t need days after 10. I need days up to 10.
look im not that committed to a different scheme. Just seems to me once you get to a week and do a weekly you are good on days. heck I would do 6 daily ones and have the weekly one just be the 7th day of the week. free up yet another deep backup.
Haha OK bud
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.
I didn’t really want to poke through each containers files to figure out where it stores logs, plus it adds risk that I’m not backing up something I should.
When I say databases aren’t real data, I’m more talking about them changing every day despite nothing happening. Even if I haven’t taken any photos or opened the app, today’s db dump of immich is not the same as yesterday’s db dump so restic stores it as a new unique file.
I did mean to ask, why restic into Borg instead of just Borg?
on the logs thing that’s fair enough, most of the stuff I use has a clear “logs” folder I can exclude, and I checked what the backup contains Vs what the container data folder has before calling it a day
I use bormatic, I can go back about 60 days and have needed to a few times in the past due to my own mistakes. Server is in the basement, it backs up toy living room TV pc which is on the top floor. My upload speed is too slow for offsite backups.
My VPS gets a weekly rsync to my home server. I keep ten deduplicated copies for weeks gone by. The current week also gets synced off-site with encryption.
I just buy new HDDs.
Unironically how I use LTO-6 tapes.
2.5TB of storage for ~$5/tape on ebay.
Never delete anything. If the authorities ever come after me, discovery is going to be hilarious.
What’s the catch, why don’t we use those? I/O speed? Limited read/write cycles? I imagine it sucks if you need files on opposite ends of the tape.
The drives are crazy expensive if you want to use a somewhat recent generation.
