One-Way versus Two-Way sync
By design, a sync definition represents a one way sync. That means,
there is a source or (master) folder where you do your work. This folder is active, it changes. Then, on the receiving end of the sync, there is a passive
destination folder that (hopefully) does not change, it simply receives changes from the source folder.
So, how about when both source and destination get edited? In other words there is no "master"
folder and we want the changed files in both folders to get synced into the other, much like phones do?
This is one of the most recurring questions. One must realize that a computer folder is not a telephone directory
where contact records can be synced both ways. In a computer where files have naming conflicts and many other problems
a two-way sync is not really feasable, it is simply too dangerous.
There is nothing to stop the user right now to set up two sync defs that are opposites of each
other, that in fact would be a two way sync, but it is something we would not recommended at all! A two way sync is the fastest way to accidentally lose the files you
are working on.
What is the solution then? It is to reorganize your work a bit... make sure you do not work on the same file
on both locations, and if so, then use source code control like cvs or something similar.
Name your folders/files differently in each location then you lessen the chance of files overwriting each other. The best way to deal with a two way sync is simply to avoid it altogether.
I have files in the destination folder that should not be overwritten if they are newer then the source! Is there a setting for this?
AASync cannot guarantee that newer files in the destination folder will not be overwritten. Why, because such a guarantee
is simply not possible. You must realize that file modification dates cannot be compared between
two different systems, since their time/date/timezone settings as well as clock states are different. Currently
UNIX does not have a facility for this. Anybody who promises such a feature is simply lying. Not to mention the fact that FTP servers trash modification dates anyway, and even on an nfs or samba mounted external filesystems you cannot trust that the mod dates can be reliably compared with your client host.
So, is there an answer? Yes. look the above answer and reorganize your work so backup/sync becomes manageable.
I am publishing our website through FTP. I get errors like this:
Failed to load folder /Volumes/MyProject/[08-145]website/web/images/thumbs, ignoring...
Two important caveats about backing up your files: You must make sure your source folder does not have unreadable folders, because they defeat the purpose of a backup sync. Also, you must consider that certain characters like quote, square brackets, star etc.. etc.. are legal on osx in filenames, but illegal in FTP, so if you want to back your files through ftp then those characters cannot be used in filenames in the source folder.
I have a choice how to reach the destination folder: a local nfs mount, FTP or SFTP. Which one should I choose?
SFTP is always the best choice. AASync will use an ssh shell, archivers and many other utilities to get the best result. It sounds strange, but an nfs/samba mount may not be the best choice, in many cases they impose restrictions, there are characterset problems and many other unforeseen complications. FTP is also very limited, it should be used if the other two protocols are not available.
How do I move my sync definitions to a new machine?
Your sync definitions sit in AAsync's document directory. You can find this directory in the path YOURHOME/Library/Application Support/AASync_3.5 . Find this folder in the Finder, select it, then use the "File/Compress AAsync_3.5" menu. This will zip up this folder. Move it to the new machine in the same path in your new home directory. Your passwords are sitting on your keychain, you either move those too using the Keychain Access App, or manually run the syncs on the new machine and enter the passwords as AASync asks for it.