zlacker

[parent] [thread] 10 comments
1. chaz6+(OP)[view] [source] 2026-01-11 22:39:35
I would really like some kind of agnostic backup protocol, so I can simply configure my backup endpoint using an environment variable (e.g. `-e BACKUP_ENDPOINT=https://backup.example.com/backup -e BACKUP_IDENTIFIER=xxxxx`), then the application can push a backup on a regular schedule. If I need to restore a backup, I log onto the backup app, select a backup file and generate a one time code which I can enter into the application to retrieve the data. To set up a new application for backups, you would enter a friendly name into the backup application and it would generate a key for use in the application.
replies(5): >>dangus+v >>Waterl+H >>PaulKe+d3 >>ibizam+fQ2 >>mlrtim+qL4
2. dangus+v[view] [source] 2026-01-11 22:41:54
>>chaz6+(OP)
I use Pika Backup which runs on the BorgBackup protocol for backing up my system’s home directory. I’m not really sure if this is exactly what you’re talking about, though. It just sends backups to network shares.
replies(1): >>cryost+Uo
3. Waterl+H[view] [source] 2026-01-11 22:42:52
>>chaz6+(OP)
Maybe apps could offer backup to stdout and then you pipe it. That way each app doesn’t have to reason about how to interact with your target, doesn’t need to be trusted with credentials, and we don’t need a new standard.
4. PaulKe+d3[view] [source] 2026-01-11 22:59:16
>>chaz6+(OP)
At the moment I am docker compose down everything, run the backup of their files and then docker compose up -d again afterwards. This sort of downtime in the middle of the night isn't an issue for home services but its also not an ideal system given most wont be mid writing a file at the time of backup anyway because its the middle of the night! But if I don't do it the one time I need those files I can guarantee it will be corrupted so at the moment don't feel like there are a lot of other options.
◧◩
5. cryost+Uo[view] [source] [discussion] 2026-01-12 01:34:46
>>dangus+v
I'm actively in the process of setting this up for my devices. What have you done for off-site backups? I know there are Borg specific cloud providers (rsync.net, borgbase, etc.). Or have you done something like rclone to an S3 provider?
replies(1): >>dangus+Ru
◧◩◪
6. dangus+Ru[view] [source] [discussion] 2026-01-12 02:13:00
>>cryost+Uo
No off-site backup for me, these items aren’t important enough, it’s more for “oops I broke my computer” or “set my new computer up faster” convenience.

Anything I really don’t want to lose is in a paid cloud service with a local backup sync over SMB to my TrueNAS box for some of the most important ones.

An exception is GitHub, I’m not paying for GitHub, but git kinda sorta backs itself up well enough for my purposes just by pulling/pushing code. If I get banned from GitHub or something I have all the local repos.

replies(1): >>cryost+hB
◧◩◪◨
7. cryost+hB[view] [source] [discussion] 2026-01-12 03:00:25
>>dangus+Ru
Good to know! I have shifted more to self hosting, e.g., Gitea rather than Github, and need to establish proper redundancy. Hopefully Borg Backup, with it's deduplication will be good, at least for on-site backups.
replies(2): >>dangus+FU >>dangus+SU5
◧◩◪◨⬒
8. dangus+FU[view] [source] [discussion] 2026-01-12 06:09:02
>>cryost+hB
I am much more in-between. I don’t mind cloud stuff and even consider it safer than my local stuff due to other smart people doing the work. And I’m not looking for a second job self hosting, except for my game servers.

I mostly just don’t want to be stuck with cloud services from big tech that have slimy practices. I’d rather pay for honest products that let me own my data better. With the exception given to GitHub which I guess is out of my own laziness and maybe I should do something about that.

If you’re using gitea you might be interested in Forgejo, it’s a fork and I think it’s well regarded since gitea went more commercial-ish IIRC?

9. ibizam+fQ2[view] [source] 2026-01-12 18:14:12
>>chaz6+(OP)
I’m working on introducing this kind of protocol in NixOS. I called it contracts. https://github.com/NixOS/rfcs/pull/189

The idea is a contract is defined saying which options exist and what they mean. For backups, you’d get the Unix user doing the backup, what folders to backup and what patterns to exclude. But also what script can be run to create a backup and restore from a backup.

Then you’d get a contract consumer, the application to be backup, which declares what folders to backup either which users.

On the other side you have a contract provider, like Restic or Borgbackup which understand this contract and know thanks to it how to backup the application.

As the user, your role is just to plug-in a contract provider with a consumer. To choose which application backs up which application.

This can be applied to LDAP, SSO, secrets and more!

10. mlrtim+qL4[view] [source] 2026-01-13 11:08:08
>>chaz6+(OP)
Why not virtualize everything and then just backup the entire cluster?

Proxmox Backup Server?

◧◩◪◨⬒
11. dangus+SU5[view] [source] [discussion] 2026-01-13 17:05:55
>>cryost+hB
I also learned this exists today: https://www.urbackup.org/
[go to top]