-
kopia
Cross-platform backup tool for Windows, macOS & Linux with fast, incremental backups, client-side end-to-end encryption, compression and data deduplication. CLI and GUI included.
I used to use restic with scripting, then I discovered resticprofile, and swiftly replace all my scripts with it.
https://github.com/creativeprojects/resticprofile
I also use Kopia as an alternative to Restic, in case some critical bugs happen to either one of them.
https://kopia.io/
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
timeshift
System restore tool for Linux. Creates filesystem snapshots using rsync+hardlinks, or BTRFS snapshots. Supports scheduled snapshots, multiple backup levels, and exclude filters. Snapshots can be restored while system is running or from Live CD/USB. (by linuxmint)
-
Rsnapshot
a tool for backing up your data using rsync (if you want to get help, use https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss)
-
I prefer using openSUSE, which is tightly integrated with snapper[0], making it simple to recover from a botched update. I've only ever had to use it when an update broke my graphics drivers, but when you need it, it's invaluable.
Snapper on openSUSE is integrated with both zypper (package manager) and YaST (system configuration tool) [1], so you get automatic snapshots before and after destructive actions. Also, openSUSE defaults to btrfs, so the snapshots are filesystem-native.
[0]: http://snapper.io/
-
I use a series of scripts to make daily Borg backups to a local repository: https://github.com/gchamon/borg-automated-backups
Currently the local folder is a samba mount so it's off-site.
The only tip I'd have for people using Borg is to verify your backups frequently. It can get corrupted without much warning. Also if you want quick and somewhat easy monitoring of backups being created you can use webmin to watch for the modifications in the backup folder and send an email if there isn't a backup being sent in a while. Similarly, you can regularly scan the Borg repo and send email in case of failures for manual investigation.
This is low tech, at least lower tech than elastic stack or promstack, but it gets the job done.
-
systemd-boot has relatively recently added support for loading filesystems, https://github.com/systemd/systemd/blob/71e5a35a5be99a1f244d... meaning you should be able to set up something similar. I wouldn't describe it as "easy" yet.
-
For home backup, I have a similar setup with dedup, local+remote backups.
Borgbackup + rclone (or aws) [1]
It works so well, I even use this same script on my work laptop(s). rclone enables me to use whatever quirky file sharing solution the current workplace has.
[1]: https://github.com/kmARC/dotfiles/blob/master/bin/backup.sh
-
Nixpkgs is the largest and most up to date package repository according to https://repology.org/
I'm honestly curious what packages you have a problem with
-
I use btrfs-assistant with Kubuntu because I can't get Timeshift to work properly. It's basically some kind of front-end for snapper and btrfsmaintenance.
[0]: https://gitlab.com/btrfs-assistant/btrfs-assistant
-
I used to use restic with scripting, then I discovered resticprofile, and swiftly replace all my scripts with it.
https://github.com/creativeprojects/resticprofile
I also use Kopia as an alternative to Restic, in case some critical bugs happen to either one of them.
https://kopia.io/
-
For me, these traits made restic initially attractive:
- encrypted, chunk-deduped, snapshotted backups
- single Go binary, so I could even backup the binary used to create my backups
- reasonable versioning and release scheme
- I could read, and understand, its design document: https://github.com/restic/restic/blob/master/doc/design.rst
I then just tried using it for a year and never hit any issues with it, so kept going, and now it's 6+ years later.
-
-
ixnay
Ixnay is a Nix shell wrapper that I'm writing as I learn about Nix and how to do various operations.
> but from my perspective the NixOS model is so obviously the "correct" way of doing an OS that it really annoys me that it's not the standard for every operating system
- Literally every person who's read the Nix paper and drank the kool-aid thinks this lol.
I STILL don't completely understand every element of my nix config but it's still quite usable. Adding software requires adding it to the large-ish config file, largely because I created overlay namespaces of "master.programname", "unstable.programname" and "stable.programname" (with the default being "unstable" in my case) but those would all ideally be moved out into 2 text files, 1 for system level (maybe called system_packages.txt) and one for a named user (perhaps called _packages.txt) and if those could be imported somehow into the configuration.nix, I think that would make things a bit easier for end-users, at least initially.
The commandline UI (even the newer `nix` one) could still use an overhaul IMHO. The original CL utils were CLEARLY aimed directly at Nix developers, and not so much at end-users...
I've been working on my own wrapper to encapsulate the most common use-cases I need the underlying TUI for https://github.com/pmarreck/ixnay < and that's it so far.