Limitations

SyncDat is not able to perfectly replicate all files in all circumstances.  Following is a list of limitations to SyncDat's functionality.  Additional limitations are listed in the Known Issues chapter.

Special Files

SyncDat is designed to operate on regular document files.  It is not intended for replication of boot disks or operating system special files.  Irregular file types, such as devices, pipes, sockets, virtual file systems, invisible files, and network mount-points may be ignored or copied as zero length files.

Multi-User Files

If a file is changed while it is being updated, it may become corrupted.  Some operating systems may prevent files from being accessed in this way, but others do not.  It is recommended that you ensure no other persons or programs are using files while they are being synchronized.

Long Paths

Pathnames longer than about 1024 bytes are not supported.  See Maximum Path Length for details.

Renamed Files

If a file's name or location within a synchronized folder is changed, SyncDat sees only that the old name has been removed and a new name has appeared.  Therefore it may delete the old name from the other folder and transfer the file as though it were brand new.  The exact behavior and order of operations will vary depending on the options selected and the location of the names within the directory tree.

Status Changes

At present, a file is only updated if its size or modification date have been updated.  Other changes, such as permission modes or ownership, will not trigger an update even though they will be preserved should an update occur.

Directory Dates

The modification date stamps of directories are not preserved: they will be set to the last time the contents of that directory were updated.

Back-Dated Files in Peer Mode

If a file is changed, but its modification date is set to a time earlier than the last synchronization, the change may not be noticed or the file may be overwritten when running in Peer Mode.

System or Network Disruption in Peer Mode

If the system or network is disrupted during a Peer Mode file transfer, such as by a power outage, one or more files may be left in an incomplete or corrupted state.  Because the date stamp may be wrong, the next synchronization could mistake the corrupted file for an update.  SyncDat will attempt to identify interrupted operations, but you should always use caution (and Safe Mode) after a disruption to Peer Mode.