Open dreamflasher opened 6 years ago
Maybe #414 will help you
@TheBestPessimist Neat! This is actually the solution for both problems I described here (symlinks in config folder). This should be mentioned in the wiki -- or rewrite the whole thing to make it more flexible and easier to understand.
There's also my pull request 396, which allows specifying the configuration path with every command. It doesn't allow multiple roots though, so symlinks may still be the best option here.
@TheBestPessimist Are you doing this on Windows with VSS? It looks fairly scary to me and tbh when doing backups I don't want things to look scary. For example I am excluding the config folder where the symlinks are so that I don't get an infinite recursion... Also VSS with symlinks across drives sounds like it's doomed to fail.
i'm doing that and i have no problems on both of my windows machines
I can confirm that this works (apart from the sheer impossibility to backup 3TB with duplicacy, due to several bugs, which I reported on the go).
Currently it's not possible to backup multiple drives on Windows, because the .duplicacy file specifies the root of the backup. Furthermore, having a config file in each drive is slightly annoying, it would be a lot nicer if it were possible to put all config files into one folder. Configuration files shouldn't fly around somewhere on the hard disc, but actually in a folder where they can be found later, orderly at one place.
My suggestion: Put the .duplicacy config file in the .duplicacy config folder, and specify in the .duplicacy file the roots (multiple!) of the backup. For Windows this would require that paths are specified as
/c/Downloads/
, so that one can have filters that fit for the drives. Then for the backup command one specifies the .duplicacy config folder.