Hi there again,
thanks to your helpful comments I think I have understood that my original plans were not quite realitistic with restic. But restic seems good for other real-world uses on my systems.
But I have some more more questions about restic’s features. I think they’re somehow important questions and they should probably find a place in the documentation, please.
AFAIR restic does de-duplication. (Is that correct?)
Does it support deleted files?
(That means, will the restore process delete files that are not present in the most recent snapshot?)
Because I’m frequently re-organizing (read: moving) vast amounts of files and it would make me unhappy to find hundreds of copies after restoring a backup. On the other hand, I would not like them being transferred over and over again.
How does restic handle connection interruptions?
I usually have only a dialup connection with an enforced nightly disconnect that can’t exactly be predicted. What happens if the backup gets interrupted? What happens if the restore process gets interrupted? If a 20 hour transfer gets interrupted, do I have to start over?
I know that restic and its authors take much effort in supplying backward compatibility. Nevertheless I have (readable and working) backups that were made more than 25 years ago. With tar and gzip this is no problem, but with a software written in a programming language that is still in development (speaking of Go) and that relies on libraries or routines completely unknown to me (the Gentoo Linux .ebuild lists ~500 files of unknown role in the restic port) it might be a struggle to get that compiled in 25 years onwards.
Is there a usable and implementable documentation about the actual backup format?
(Couldn’t find that on the website.)
Or maybe a C implementation of a flat dumb unpacker?
I say thank you to all of you in this it appears really helpful community.