Troubleshoot Multi-Site Deployment

For information about managing a multi-site deployment, see Managing a Multi-Site Deployment.

Symptom	Resolution
During configuration sync, objects are unexpectedly deleted or changed at facilities.	Synchronization of folders and objects is configured at both HQ and facilities. Also, synchronization can be configured for an object type within a folder or for an individual object. If an object is created at HQ with synchronization enabled and is replicated to a facility, then by default synchronization is enabled for the object the corresponding object at the facility. If synchronization is enabled for an object at a facility, but is disabled at HQ or the object does not exist at HQ, then when synchronization occurs the object will be deleted from the facility. At a facility, if you manually add or modify an object in a synchronized folder, it is recommended that you disable synchronization for that object at the facility. Otherwise, the object or your changes will be deleted when synchronization occurs. At HQ, if you are changing the object types to synchronize that will apply to a folder that already exists at a facility, carefully consider the impact on the facility. If synchronization is enabled for an object at a facility, but is disabled at HQ or the does not exist at HQ, then when synchronization occurs the object will be deleted from the facility. For more details, see the following table.
The configuration sync is not working.	The Loftware Enterprise SP version (including major, minor, and any hotfix) must be the same at headquarters and at each facility for the synchronization to succeed.

Symptom

Resolution

During configuration sync, objects are unexpectedly deleted or changed at facilities.

Synchronization of folders and objects is configured at both HQ and facilities. Also, synchronization can be configured for an object type within a folder or for an individual object.

If an object is created at HQ with synchronization enabled and is replicated to a facility, then by default synchronization is enabled for the object the corresponding object at the facility.

If synchronization is enabled for an object at a facility, but is disabled at HQ or the object does not exist at HQ, then when synchronization occurs the object will be deleted from the facility.

At a facility, if you manually add or modify an object in a synchronized folder, it is recommended that you disable synchronization for that object at the facility. Otherwise, the object or your changes will be deleted when synchronization occurs.
At HQ, if you are changing the object types to synchronize that will apply to a folder that already exists at a facility, carefully consider the impact on the facility. If synchronization is enabled for an object at a facility, but is disabled at HQ or the does not exist at HQ, then when synchronization occurs the object will be deleted from the facility.

For more details, see the following table.

The configuration sync is not working.

The Loftware Enterprise SP version (including major, minor, and any hotfix) must be the same at headquarters and at each facility for the synchronization to succeed.

Effect of Configuration Sync on an Object

Although it is recommended that synchronization be managed by object type at the folder level, you can also manage synchronization for individual objects.

Tip: In most cases, disabling synchronization for an object at a facility prevents headquarters from synchronizing that object with that facility. However, if the object is moved or renamed at the headquarters, then the object at the facility is likewise moved or renamed, but is not otherwise altered. Also, if there is a conflict (not just a difference) between the headquarters and a facility, the object configuration from headquarters overrides that of the object at the facility as required to resolve the conflict.

Synchronization setting		Effect of configuration sync on object at facility
At HQ	At facility	Effect of configuration sync on object at facility
	Object does not exist	No change. No object exists at the facility and HQ is not synchronizing the object.
	Object does not exist	The object at HQ is replicated to the facility.
		No change. An object of the same name exists at both HQ and the facility, but they are managed separately.
		The object at the facility is updated to match the corresponding object at HQ.
		No change. An object of the same name exists at both HQ and the facility, but they are managed separately.
		The object at the facility is deleted because it is configured to be synchronized, but the corresponding object at HQ is not configured to be synchronized.
Object does not exist		No change. The object exists only at the facility.
Object does not exist		The object at the facility is deleted because the corresponding object at HQ has been deleted or does not exist.