Skip to content

Synchronization settings

If you have selected the User-defined configuration, you can make the synchronization settings for each element directly after selecting it. With the Express configuration, you make the synchronization settings for all elements.

Figure: Configuration selection dialog, custom configuration option

Direction of synchronization

In the top dropdown menu, you can select the source server and the target server and thus define the direction of synchronization.

Handling of synchronization conflicts

In the second dropdown menu, you can select which of the two servers involved in the synchronization is the dominant one. If a certain element already exists on both synchronization partners, the following applies:

  • If the source server is the dominant one, the state of the element is transferred from the source server to the target server.
  • If the target server is the dominant one, the state of the element is retained on the target server.

Info

Main rule of conflict handling: Changes are always made on the target server.

You have the following entries to choose from here:

  • Server1 wins: If the synchronization direction Server1 - to - Server2 has been selected, elements that already exist on Server2 are overwritten with those from Server1. If the synchronization direction is reversed, the state of the elements on Server1 is retained.
  • Server2 wins: If the synchronization direction Server2 - to - Server1 has been selected, elements that already exist on Server1 are overwritten with those from Server2. If the synchronization direction is reversed, the state of the elements on Server2 is retained.
  • The newer version wins: If there are conflicts, the timestamp of the element on the two servers is queried. If the element on the target server is the older one, it is overwritten by the newer one. Otherwise, the state of the element on the target server is retained.
  • No winner: The conflict remains unresolved. Elements on Server1 remain on Server1, elements on Server2 remain on Server2. If elements have been deleted on one server and there are still elements on the other server, this state is also retained.

Info

This option is not available for the Internal event log element. Only Target server wins are possible here.

Delete elements on the target server that no longer exist on the source server

If you select this checkbox, elements that existed on both servers are treated as follows:

  • An element that was deleted on the source server is also deleted on the target server during synchronization.
  • An element that was deleted on the target server but still exists on the source server is restored to the target server during synchronization.

Info

This does not apply to the Internal event log element. The Event log of the source server is added to the target server. The entries in the Event log of the target server remain on the target server. The entries in the Event log of the source server are copied for this purpose.

Define paths of the components to be synchronized

If you have selected Components when selecting the elements, you can specify here which components are to be synchronized.

To synchronize only individual components or directories, proceed as follows:

  1. Click on the button Icon Add.
  2. The server archive opens.
  3. Select the component you want to synchronize.
  4. The path of the selected component is displayed in the field.

To exclude individual components from synchronization again, select the component and delete it using the button Icon Delete.