One particularly interesting problem is that WebDAV on Apache has a slight race condition, where it will list a file as “existing, downloadable, and correct” and afterwards delete the file:įor this reason, Duplicati uses random filenames, and does not overwrite an existing file. Having seen the error reports from the 1.x users, I know this is just not the case. When I wrote Duplicati 1.x I also had the same approach: of course the storage works, otherwise they will (should?) fix it. In particular, his statement about trusting the backend is very enlightening: So in the script I just create this little file inside the temporary folder for which I’m going to download the test files.įYI, the duplicacy developer made a nice summary of this topic. (no key, password, nothing, just the path) In the repository ( d:\myprojects) there is only one. I have a centralized folder of settings, in which there is a subfolder for each repository: I have the d:\myprojects folder that I want to back up (it’s a “repository”, by the nomenclature of Duplicacy) And in this format, there is only a small file in each repository that contains only one line with the configuration path in the centralized folder. a centralized folder with all configurations of all repositories.a “duplicacy” folder inside each repository (unpractical …).No, it is not necessary to initialize from scratch.ĭuplicacy has two ways of storing the settings for each repository (the local folders) and the storages for which each repository sends the backups: I suppose that is what your script is doing (initialize a new repository)? And I guess I overinterpreted that as basically meaning “you can’t restore to a new location”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |