12:45:50.646 WARN OPEN_FAILURE Failed to open file for reading: open D:\backup_software_test\duplicacy repo/c_link/Users/crist/AppData/Local/Microsoft/Windows/SettingSync/remotemetastore/v1/meta.edb: The process cannot access the file because it is being used by another process. 12:45:50.604 WARN OPEN_FAILURE Failed to open file for reading: open D:\backup_software_test\duplicacy repo/c_link/Users/crist/AppData/Local/Microsoft/Windows/SettingSync/remotemetastore/v1/edb.log: The process cannot access the file because it is being used by another process. I have no desire to learn batch scripts and CLI just to do something the GUI can mostly do already.12:45:50.604 WARN OPEN_FAILURE Failed to open file for reading: open D:\backup_software_test\duplicacy repo/c_link/Users/crist/AppData/Local/Microsoft/Windows/SettingSync/metastore/meta.jfm: The process cannot access the file because it is being used by another process. I'm aware that I can do this through CLI, but scheduling and emailing of logs from GUI is very helpful. Same request here, need to be able schedule backup of multiple repositories on same PC through GUI. So for CLI, you would suggest in order to handle multiple backup directories, instead of symlinks, to have unique 'repository ids' for each directory root and then to iterate over them in a batch file say? This does seem better considering the current issue surrounding VSS on other volumes. Yea I'm aware of the github talk re terminology. Our terminology is somewhat confusing because the meaning of repository is different from what is usual for other backup tools.Īha ok. What JarnoP meant was to backup two directories to the same storage. I'm currently evaluating the CLI at the moment and thought I knew how it worked. After init, does backup have to be run from each directory? My first thought is the snapshot state will get nuked by the other. Wait, how does 1) actually work (CLI)? Two different repository directories but with the same repository id? This configuration doesn't seem to be mentioned in any of the docs. Hope that this will lead to a more mature product eventually :) It has calmed down a bit so I started to have more time on development. Yes, there had been a sudden surge on emails, issues, posts, etc. What is the "Crashplan effect"? I mean, I know what happened to CP, but are you overwhelmed with support due to this? Just curious. The new estimate is end of October if nothing special happens again before then. It has been going slow due to recent Crashplan effect. When I will be able to backup more than one directory with the GUI version? Thanks, I went to read the design docs more carefully and went to test #1. Duplicacy is very flexible in this regard due to the lock-free deduplication approach. For the CLI version 1) is recommended.Īnd yes, you can backup different directories on the same or different computers to the same B2 bucket. If the approach #1 also works, can I backup partially overlapping repositories from different computers to the same backup Storage? I mean the case were some computers have only subset of the total content in a repository.īoth 1) and 2) should work, although 2) is more of a workaround for the GUI version since it can only backup one directory. I would like to backup the both directory trees to the same backup destination (B2 Bucket) to save in data transfer time in case documents get moved form one directory-tree to another.ġ) init the backup two times (once for each directory) for the same repository ?Ģ) Use symlinks and create a separate (artificial) "root" directory and place the symlinks there pointing to the root of both the directories? I have few directories containing documents that sometimes get moved from one to another. All issues How to backup multiple directories to the same backup destination?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |