The most severe response occurs in the presence of Hard Links and NTFS Reparse Points. If a file / folder associated with either of these features is detected in a protected share, replication will stop. The System Administrator must then take remedial action to remove the affected file or folder from the protected file set before restarting replication, as described in
If an existing file or folder, associated with a Hard Link or NTFS Reparse Point, is moved or copied into a protected share, Neverfail for File Server may begin to synchronize the file / folder before the unprotected feature is detected. In this case, the file / folder will fail to synchronize, and multiple alerts will be triggered in respect of this. Firing these alerts may substantially increase the time required by Neverfail for File Server to stop Replication.
It is strongly recommended that Administrators avoid the use of Hard Links and the various implementations of NTFS Reparse Points (other than Windows 2003 DFS Reparse Points) within the Neverfail protected file set - which will include all user shares on the active server.