Managing File Conflicts

<< Click to Display Table of Contents >>

Navigation:  Peer Global File Service Help > File Collaboration Jobs > Running and Managing a File Collaboration Job >

Managing File Conflicts

Files conflicts can occur for the following reasons:

A file is already opened by a user when a File Collaboration job is started and the file size and timestamp does not match the other target hosts.

A file is already opened by two or more users when a File Collaboration job is started.

Two or more users open a file at the same time before all files can be locked down by the running File Collaboration job.

A file was modified on two or more hosts between job restarts or network outages.

A general I/O failure occurs on the source host after the file has been modified, but before the file is synchronized to all target hosts. In this case, the file is automatically quarantined.

When a file conflict is detected, the file is placed in the File Conflicts list and assigned a conflict status, which determines how the conflict is resolved.  The File Conflicts list is displayed in the File Conflicts view.

For an elaboration on conflict scenarios, see file conflict scenarios.