![]() |
Startup | Registration
Console | Timer | Multiple | Filters | Exclude | Conflicts | Automount Volumes | AppleScript | Settings
Backup the Boot Disk | Exact Sync | Log | Scheduling | Preview | Preferences | FAQ
| Conflicts: | ![]() Picture 1: The Conflict panel. ![]() Picture 2: The Conflict Ask panel. If you marked the check-box "Ask", during the sync or backup (if the task has not been launched by the timer), you will be shown this panel. Here you will be able to make your choise in case of a given conflict. Also, you will be able to open and inspect the content of the two files (clicking on the "eye" icon) and to reveal them in the Finder. In case the task is a sync and if both the files exist you will be able to invert the directions of the copy (clicking on the orange/violet arrow icon). |
|
|
Go to the Conflicts window choosing the Conflicts item from the Option menu, or clicking on the Y icon on the console. You will be shown the picture 1 aside.
In any of these 7 cases (grouped in four) the first choise makes FS behave such a way to execute a standart backup or a standard sync.
If the Sync/Backup had been launched by a timer (or by the Sync&Quit timer), FS would not display the dialog for asking, but it will behave as specified by the radio-buttons in the Conflicts panel. |
||
We kindly invite you to read the following sample. A sample about the Exact Sync (case "d2" above): let's suppose you have a subfolder "A" either in the main source folder and in the main destination folder. Both the folders "A" contain the files "y" and "z". You have already "exact synchronized" earlier the main folders. Now, if you delete the subfolder "A" (and its content) from the main source folder, and your colleague adds a file "x" to the destination subfolder "A" (or modifies here an existing file), FS at the next "Exact Sync" shouldn't know what to do. Since it's an Exact Sync it could decide to delete the destination folder "A" too. Many sync software use to do that. If so, you should lose the file "x" that your colleague created inside the destination folder "A". Forever. Other hand, if instead of deleting the destination folder "A" (and its content), FS copied the whole destination folder "A" back to the source folder (with the files "x", "y" and "z"), you could not agree, because you want the file "y" and "z" deleted from your disks. Thus you have to define the proper behaviour. You have two choises:
The PDF User manual contains more detailed information. |
||