It’s indeed known and the next issue I’ll tackle aufter the local metadata cache. The workaround is making separate backups of the two directories. Alternatively use the fuse mount, which will list the directories with suffixes -1, -2 and so on.
I’m very sorry but it seems my workaround does not work (any more?), it looks like only the first directory called dir is saved when called like this: restic backup foo/dir bar/dir. So the workarounds are:
Make separate backups like this: restic backup foo/dir; restic backup bar/dir
Backup the parent directory: restic backup .
I’ll see what I can do to resolve this issue near term.
Discourse is an open source project so we didn’t need it to be “done”, we just needed it to be in a releasable beta state. We finally released Discourse 0.8 on February 5th, 2013. Remember, if you don’t release something you’re slightly embarrassed about, you released too late! And it was indeed pretty embarrassing!
So, last point: It’s always a good idea to test a restore and make sure that all data is there, regardless of the technology/implementation used. I’m glad people do that (and stumble on this embarrassing bug)