EnderChest VS Rdiff-backup

I'm never buying another console again. PC ports or emulation from now on. Steam is super convenient, but honestly my ideal ecosystem would be DRM-free titles that don't phone home. I have the technical knowhow to do my own "cloud" saves and config syncs (though the package I wrote to do it is currently mid-rewrite).

If by some chance your PC is running macOS or Linux, this is going to be absolutely trivial once you learn the syntax. I actually have a github project that does this specifically for Minecraft (while also keeping mods and settings synchronized between different instances on the same computer).

I've been working on a project that syncs my minecraft worlds, mods, resource packs and configs between five different computers, one of them being the Deck. It's command-line based and only really tested on Linux/macOS, but it has the advantage of being config-less (everything is handled by filenames alone) and will work in principle with any launcher. Transfers are also pretty fast since it uses rsync to just perform incremental backups--my world file is about 4GB right now, and it takes under a minute to check in and sync a play session across all my devices (I have a separate project that also does version control to roll back a creeper explosion a borked save caused by a corrupted mod)

Idk, I really dislike the Curseforge launcher so when I booted up GD I noped back out of it pretty fast. To each their own, and I do need to spend some more time with it, though, as I'm working on an asset manager that should be launcher-agnostic, and a lot of folks really do love GD (and Curseforge and Lunar and Badlion and the official Mojang launcher...).

Working on it and would be happy to accept contributions and feedback.

Hmm... how is ssh support on Windows machines these days? Will the scripts I use to backup and synchronize my Minecraft instances work on Windows 11? And what are the good free nonlinear video editors for when I want to edit and post gameplay footage?

Interesting. I've never had a problem with MultiMC or any of its forks. It sounds to me like you probably just needed to allocate more RAM (as a rule I typically set the default Xmx to half the total system RAM, or 8GB in the case of the Deck). In any case, thanks for clueing me into an alternative launcher. I'm working on a project to keep mods, configs, resource packs, worlds, etc. synced across different instances and different computers, and eventually I'll want to make sure I support as many launchers as possible.

For starters it has a tendency to paint itself into a corner on ENOSPC situations. You won't even be able to perform a restore if a backup was started but unfinished because it ran out of space. There's this process of "regressing" the repo [0] which must occur before you can do practically anything after an interrupted/failed backup. What this actually must do is undo the partial forward progress, by performing what's effectively a restore of the files that got pushed into the future relative to the rest of the repository, which requires more space. Unless you have/can create free space to do these things, it can become wedged... and if it's a dedicated backup system where you've intentionally filled disks up with restore points, you can find yourself having to throw out backups just to make things functional again - even ability to restore is affected.

That's the most obvious glaring problem, beyond that it's just kind of garbage in terms of the amount of space and time it requires to perform restores. Especially restores of files having many reverse-differential increments leading back to the desired restore point. It can require 2X the file's size in spare space to assemble the desired version, while it iteratively reconstructs all the intermediate versions in arriving at the desired version. Unless someone fixed this since I last had to deal with it, which is possible.

Source: Ages ago I worked for a startup[1] that shipped a backup appliance originally implemented by contractors using rdiff-backup. Writing a replacement that didn't suck but was compatible with rdiff-backup's repos consumed several years of my life...

There are far better options in 2024.

[0] https://github.com/rdiff-backup/rdiff-backup/blob/master/src...

[1] https://www.crunchbase.com/organization/axcient

and that should install the latest version, rdiff-backup-2.2.4-2.el8.x86_64.rpm. This is all described in the rdiff-backup README file.

Rdiff-backup - close to what you do currently but at least provides versioning. Based on rsync

as in just a copy of your files? This I would barely consider a backup, more of just a mirror from a point in time. What're you missing by doing this? versions of files, deduplication, and encryption (last one being very important for the best kind of backups, which should be off-site). Just because it's not files doesn't mean it's proprietary. Proprietary would mean secret and undocumented. There are many great options. Borg is my favorite but Kopia is probably better if you use windows, urbackup is an option if you want centralized management of backups and rdiff-backup is if you want something kinda what you have currently but adding versioning but lacks deduplication and encryption.

If you're comfortable with the cli and you want to have your backup in a plain file format with some incremental backups, there's rdiffbackup. It uses rsync under the hood and has worked quite well for me.

Rdiff Backup - Reverse differential backups that uses rsync, linking, and can tunnel via ssh. You get a full current backup with increments available to restore any version of the file with minimal storage space used.

borg is great. we've been using it for the past 3 years to archive hundreds of file-level backups of servers, database dumps and VM images. average size of each borg repo is few GB but there are few outliers up to few hundreds of GB.

borg replaced https://rdiff-backup.net/ for us and gave:

Robocopy is great if you don't have access to rsync. If rsync via WSL2 for instance is an option, I'd personally go with rdiffbackup.