We want to synchronize a local folder strucutre to a remote
FTP Server using SyncFTPDir.

The initial synchronization successfully creates the
structure with files in the target.

All subsequent synchronizations fail. The FTP Server returns a
message saying, it can not create an already existing directory.

Files do not get deleted in on the FTP Server, although permissions
are set correctly. The 24x7 logfile confirms the file as deleted.

Caching is turned off.
Running 24x7 V3.4.1

Please upgrade to v3.4.2. This issue has been fixed now.

: We want to synchronize a local folder strucutre to a remote
: FTP Server using SyncFTPDir.

: The initial synchronization successfully creates the
: structure with files in the target.

: All subsequent synchronizations fail. The FTP Server returns a
: message saying, it can not create an already existing directory.

: Files do not get deleted in on the FTP Server, although permissions
: are set correctly. The 24x7 logfile confirms the file as deleted.

: Caching is turned off.
: Running 24x7 V3.4.1

Just installed v3.4.2. but no success. Any more ideas?

: Please upgrade to v3.4.2. This issue has been fixed now.

Please enable tracing and rerun the job. Please check the FTP.log file and the job trace for error and other suspicious messages from the FTP server.
Please let me know what you get in the trace.

: Just installed v3.4.2. but no success. Any more ideas?

The synchronization works now, but finds 100% difference between source and target
on every synchronization, thus uploads all files. I found no susbpicious messages
in the trace. What criteria is used to figure out differences?

: Please enable tracing and rerun the job. Please check the FTP.log file and
: the job trace for error and other suspicious messages from the FTP server.
: Please let me know what you get in the trace.

If a target file has newest date it is not touched; if a file is missing in the target directory it gets uploaded; if it does not exist in the source directory, it gets deleted; otherwise the file gets updated. Of course, the exact behavior depends on parameters passed to the procedure Sync procedure. To find out first which files will be updated you can run the Compare… procedure.
: The synchronization works now, but finds 100% difference between source and
: target
: on every synchronization, thus uploads all files. I found no susbpicious
: messages
: in the trace. What criteria is used to figure out differences?

Thanks for your info. What date is a file date compared against to figure out
the newest date?

: If a target file has newest date it is not touched; if a file is missing in
: the target directory it gets uploaded; if it does not exist in the source
: directory, it gets deleted; otherwise the file gets updated. Of course,
: the exact behavior depends on parameters passed to the procedure Sync
: procedure. To find out first which files will be updated you can run the
: Compare… procedure.

If they do not match then the target file gets overwritten.

Some FTP servers do not support changing file date/time for uploaded files. In such cases uploaded files always have system date/time when were uploaded. Because of that when replicating files 24x7 has no way to know why file date/times do not match. 24x7 does not attempt to perform binary file comparison, as this process is not efficient.
If this is your case and you do not want to replicate same files again and again consider mapping your target directory on the FTP server as a shared network drive so that you can run SyncDir method using network based file processing rather than FTP file processing.

Alternatively, you can install 24x7 Remote Agent on the target computer and run SyncRemoteDir.

: Thanks for your info. What date is a file date compared against to figure out
: the newest date?