Under the hood DropSync uses a tool called rsync to perform the actual syncing. Two different versions of rsync are provided, one based on the 3.10.x branch and another based on rsync 2.6.9 that has some OSX specific features enabled. For most situations the default (3.10.x) rsync is best.
DropSync displays notifications using Notification Centre. The general options pane provides control over when DropSync issues notifications.
Turn deletions on and off for syncs in specific directions. More detail about how deletions work is available here.
Syncs are normally allowed for both left and right directions. Use this section if you need to enforce syncing in one direction only.
Use this option if you are performing a one-way sync and want super-fast performance. Instead of scanning through files to find changes DropSync will keep track of changed files as they change, and only include those in the sync. Beware that DropSync cannot monitor changes on the right for ssh folder pairs so in that case changes that occur on the right will be missed.
When DropSync updates or copies files it can also set attributes of various types. Support for syncing these attributes varies depending on the nature of the source and destination file systems, and the OS privileges required to set them. DropSync will issue a warning during a sync if it is unable to successfully update a chosen attribute.
Syncing extended attributes differs substantially depending on the version of rsync chosen in the general options pane. In most cases the default is best, however in rare circumstances (e.g., when extended attribute data is very large, or when syncing to a filesystem that does not support extended attributes) you should choose the 2.6.9 version of rsync. Extended attributes synced using rsync 2.6.9 are stored alongside the original file in a hidden companion file whereas extended attributes synced using rsync 3.10.x are attached to the file using the filesystem's native extended attribute mechanism.
Symbolic links are a special type of file that simply points to another file or directory. DropSync lets you choose whether to copy these as they are (treat links as links) or to transform them into the file or directory that they point to (transform links into referent file or dir). Because symbolic links can refer to any file path they might sometimes point outside the syncing root, you can choose not to copy links of this type.
When DropSync performs an update it tries to avoid copying anything that already exists at the destination. This section provides various options for changing the circumstances under which files will be skipped. The default method of matching files is a combination of modification time and size, which is both accurate and fast. On some filesystems, or when communicating with some servers via ssh the modification time matching might be inaccurate (due to different granularity of timestamps or differing clocks). In such cases a fast but rather loose option would be to choose "size only", or a slow but very accurate option would be to compare checksums. Beware that comparing checksums is very slow.
For compatibility with Windows, many USB drives are formatted as FAT32. This is an old filesystem that does not support fine grained timestamps. In order to preserve the ability to skip files based on size and modification time it is necessary to change the accuracy with which times are compared. Entering a value of 1 into the compare mod-times with reduced accuracy box should deal with the issue.
DropSync default settings will usually give excellent performance when syncing. Options available here can be used to tweak performance for special cases. On extremely fast networks, and for local file transfers it can be beneficial to select the Transfer whole files not deltas option. At the opposite extreme, for syncs over a slow network connection it can be beneficial to compress data during the transfer. It is also possible to control which files are transferred based purely on their size.
Relative filter rules written like this *.jpg
apply anywhere within a folder hierarchy (selected folders only). Absolute rules start with a /
and apply matches based on the root folder. For example /*.jpg
would only match jpg files in the root folder, or /subdir/*.jpg
would only match jpg files within subdir.
When using several filter rules together it is important to keep in mind that their order matters. Rules are examined in order (top first) and the first match encountered is used.
Syncing on a timer should only be used if you don't care about syncs running at a precise time. Timers don't sync themselves to a calendar clock so a timer set to go off every 24 hours will gradually shift to a different time of day. At present the only way to schedule syncs at a precise time is to use Applescript and the OSX Calendar.
id_rsa
or id_dsa
or key.pem
) rather than the public key. DropSync will never transmit your private key itself but needs to be able to read the private key in order to authenticate the connection.
~
to the name.Keeping rescue data around can consume alot of disk space if you make frequent changes. If this is the case its probably best to turn off rescue, or perform regular cleaning. To clean out the rescue folder simply open it in finder and drag items to the trash.
Keeping a rescue folder for an SSH Folder Pair can be really useful, but if your SSH server is a production web server it is important to ensure that this folder does not introduce any security issues. The rescue folder should be given the same security considerations as the rest of your system.
Start typing an item (for example to add the Append option start typing --a
) and a list will appear with options that valid options corresponding to what was typed.
DropSync uses these core options. Consider how custom options might function when combined with these.
"--dry-run",--itemize-changes","--recursive","--verbose","--progress","--stats"