111–120 of 124 posts
BorgBackup user here and really happy. It was a set and forget for me and after 7 years, the deduplicated backup is still working flawlessly each week. I recommend pairing it with borgmatic [1], which helps to design away some of the complexities of the underlying borg backup. [1]: https://github.com/borgmatic-collective/borgmatic
Does someone know a good Android client?
That and being able to have multiple machines writing to a shared repository at the same time is handy. I have the kids' Windows computers both backing up to the same repo to save a bit of storage. (Now if only Kopia supported VSS on Windows without mucking around with dubious scripts.)
BorgBackup user here and really happy. It was a set and forget for me and after 7 years, the deduplicated backup is still working flawlessly each week. I recommend pairing it with borgmatic [1], which helps to design away some of the complexities of the underlying borg backup. [1]: https://github.com/borgmatic-collective/borgmatic
My problem is I learn some tool like this, set it, and then indeed forget it. Then I avoid testing my backups because of the work it takes to un-forget it. Because of this, I'm leaning more and more towards rsync or tools that have GUI frontends.
Personally I automate restore testing with cron. I have a script that picks two random files from the filesystem: an old one (which should be in long term storage) and a new one (should be in the most recent backup run, more or less), and tries restoring them both and comparing md5sums to the live file. I like this for two reasons: 1. it's easy to alert when a cronjob fails, and 2. I always have a handy working snippet for restoring from backups when I inevitably forget how to use the tooling.
IMO alerting is the trickiest part of the whole setup. I've never really gotten that down on my own.
Earlier quoted context omitted.
My problem is I learn some tool like this, set it, and then indeed forget it. Then I avoid testing my backups because of the work it takes to un-forget it. Because of this, I'm leaning more and more towards rsync or tools that have GUI frontends.
At a minimum you need backup, regular restore tests, and alerts when backups stop or restore tests fail. Personally I automate restore testing with cron. I have a script that picks two random files from the filesystem: an old one (which should be in long term storage) and a new one (should be in the most recent backup run, more or less), and tries restoring them both and comparing md5sums to the live file. I like thi…
On another VM, I used postfix to email logs after cronjob (failed or passed), which also works great.
Earlier quoted context omitted.
Yeah with enough scripting, you can rebuild a slow equivalent to a real backup program, that will also use 10x the disk space.
Yep. But it works and has worked for over 20 years. Various backup software has come and gone in that time but rsync has been a rock.
Earlier quoted context omitted.
My problem is I learn some tool like this, set it, and then indeed forget it. Then I avoid testing my backups because of the work it takes to un-forget it. Because of this, I'm leaning more and more towards rsync or tools that have GUI frontends.
At a minimum you need backup, regular restore tests, and alerts when backups stop or restore tests fail. Personally I automate restore testing with cron. I have a script that picks two random files from the filesystem: an old one (which should be in long term storage) and a new one (should be in the most recent backup run, more or less), and tries restoring them both and comparing md5sums to the live file. I like thi…
Not an endorsement, just a happy user.
Earlier quoted context omitted.
At a minimum you need backup, regular restore tests, and alerts when backups stop or restore tests fail. Personally I automate restore testing with cron. I have a script that picks two random files from the filesystem: an old one (which should be in long term storage) and a new one (should be in the most recent backup run, more or less), and tries restoring them both and comparing md5sums to the live file. I like thi…
I use ntfy.sh for sending push notifications from scripts and such. It's open source and free (they have paid plans as well now, but I didn't encounter any limitations in the free plan). Not an endorsement, just a happy user.
BorgBackup user here and really happy. It was a set and forget for me and after 7 years, the deduplicated backup is still working flawlessly each week. I recommend pairing it with borgmatic [1], which helps to design away some of the complexities of the underlying borg backup. [1]: https://github.com/borgmatic-collective/borgmatic
Or, if you're using a desktop environment and prefer a GUI, Vorta has been treating me well. https://vorta.borgbase.com/
Then everything gets backed up to my local server which then syncs out to remote storage. It's great.
Can't wait for Borg 2 to hit stable. The transfer command solves so many problems
Earlier quoted context omitted.
Yep. But it works and has worked for over 20 years. Various backup software has come and gone in that time but rsync has been a rock.
Fwiw, Borg is coming up on 10. 12 if you include the project it forked from. I like the simplicity of rsync approaches, but Borg seems to have longevity and widespread use.
Does anyone have an up-to-date comparison of Borg vs Restic? Or a compelling reason to switch from Restic to Borg? I've previously used Borg, but the inability to use anything other than local files or ssh as a backend became a problem for me. I switched to Restic around the time it gained compression support. So for my use-case of backing up various servers to an S3-compatible storage provider, Restic and Borg now s…