![]() If you find that you don't like the change you made, no sweat, just, in the configuration file listing, click on another configuration, or click in some empty space in the listing - FFS will then ask if you want to save the configuration you just modified to test. Well you can modify the configuration in FFS, then test your change. Now let's say at a later time you want to experiment with changing something for that configuration - just so you can test something out. ![]() Let's say you have a configuration set up the way you would like it to be and that you have saved that configuration. The configuration file only gets saved when you physically give expressed permission for it to be saved. The errors won't make any difference to your configuration file. I assume that since there were four Error Code 3s, there was a separate error code 3 for each of the four backup folders.Įrror Message 1 Error Message 1.png (18.07 KiB) Viewed 3779 times Error Message 2 Error Message 2.png (31.3 KiB) Viewed 3780 times Error Code 3: The system cannot find the path specified. Then there were four Error code 3s stating "Cannot read the attributes of "D:\". I received an error message that my four target backup folders could not be found (paths were listed). Second error: For the same saved configuration as above, I clicked compare without any backup drive connected to the laptop. The message at the bottom was that the folders are created automatically when needed. I received a warning that "The following folders do not yet exist" and then the paths to the four target backup folders were listed. My questions is whether my saved configuration would have remained intact and whether it can be safely used for continued synchronizations without having been corrupted.įirst error: I have a saved configuration containing four folder pairs and clicked "compare" with the wrong backup drive connected to my laptop. ![]() P.S.: Syncronizing D:\A directly with a Boxcryptor encrypted \\webdav\A is very very slow, so that this is no solution.I made 2 errors. I suspect deleting X:\B\A\sync.ffs_db, as I tried as first solution, is not so useful as it would slow down FreeFileSync or make the synchronization not optimal? If not, the only way I can think of is to rename the file D:\B\A\sync.ffs_db (from Sync 2) before starting Sync 1 and rename it again afterwards. My question is now if whether it is possible to configure FreeFileSync to use a name other than sync.ffs_db for its database? So, the above error probably occurs because X:\B\A\sync.ffs_db references two files - and probably the newest. ![]() If you look at X: there is only one file X:\B\A\sync.ffs_db. Sync.ffs_db.bc (from Sync 1) and sync.ffs_db (from Sync 2). If I run Sync 1 twice in a row without Sync 2 in between, no error occurs. ![]() When I press "repeat" in the error message box, then it resumes and continues without an error.Īlso, if I delete the file X:\B\A\sync.ffs_db before starting Sync 1, no error is reported. Įnglish translation: Error code 183: A file can not be created if it already exists. In German: Fehlercode 183: Eine Datei kann nicht erstellt werden, wenn sie bereits vorhanden ist. X:\B\A\_tmp cannot be moved to X:\B\A\sync.ffs_db Wenn I run Sync 1, then Sync 2 and again Sync 1, Sync 1 reports an error that With a webdav device (webdav is here an abbrevitation for the real name) If you look at D:\B\A, all files are encrypted and have the ending. the encrypted files are emulated so that they look like and can be handled as normal files. X: is a virtual device, encrypted by Boxcryptor, i.e. I have a little bit complicated configuration: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |