Maybe I state the obvious here but anyway:
Tonight I found a super comfi way to browse and restore data from Borg repositories. In vorta you can add any existing borg repository and mount the containing backups in a very functional GUI. Until now I somehow assumed you could only deal with backups created in vorta which is not true.
For context let me explain why I find that so useful: I am using a wonderful Borg / Borgmatic container from the borgmatic collective. It works super reliable. But for restoring files you have to mount the backup in the container and deal with the files inside the container. This can be difficult i.e. when looking for a specific file in a folder with a lot of files (like a foto collection where you accidentally deleted one file).
If any Borg users are out there: I would be interested what your workflows look like.
borgmatic dev here. First of all, if Vorta is working well for you to recover files, then by all means use Vorta! Right tool for the job and all. Having said that, a couple of thoughts on using borgmatic in Docker and recovering files:
borgmatic has a search feature that makes finding a particular file in an archive or across archives pretty easy. So that might be step one in restoring an accidentally deleted file.
Once you’ve found the file and archive to restore, you can either use
borgmatic extractorborgmatic mount. Withextract, you copy one or more files out of a backup archives. The challenge though is that with borgmatic in a container, by default there’s not an easy way to copy those files into their original locations. However I think the “fix” is to mount your source volumes as read-write instead of (the documented) read-only. That way you can easily copy extracted files back to where they belong.As for
borgmatic mount, you’ve got a similar challenge and fix. You can presumably mount backup archives (or a whole repository) within the container, but then you need to copy your recovered files out of that mount into their original source volumes. So that probably also means those volumes need to be mounted read-write.Let me know if you have any questions!
Is there a way to have an ssh remote without borg installed on the target?
Nope! Borg always requires Borg on the remote side. It’s Borg’s biggest strength and weakness versus competing backup systems IMO. Strength, because it can do pretty smart stuff with its own code running on both sides. Weakness, because it means it doesn’t work natively with cloud object storage like S3. It’s a tradeoff like anything else.