Resolving object conflicts

When objects are synchronizing and an object with that name already exists on the vault 2, conflict resolution occurs.

Conflicts are resolved based on which object has the latest time among the objects’ last_modified, last_changed, last touched times.

• When versioning is disabled and no permanent versions exist in either objects' metadata, the object written last stays.
  • If the vault 1 object is more recent, then the vault 2 site reads the object from the vault 1 and replaces the existing content.
  • If the vault 2 object is more recent than the vault 1, then the vault 1 site reads the object from the vault 2 site and replaces the existing object.
• For standard vaults only, when versioning is enabled or suspended and permanent versions exist in the version history of either object, then the metadata of both objects must be merged to create new metadata that then is written to both vaults. The version history of the new object must be interleaved in chronological order to ensure proper versioning is preserved.
• Protected Mirrors do no support Versioning.