Resynchronizing a Restored Broker with its Territory

If you have restored a Broker Server that hosts a Broker that is a member of a territory, you must ensure that the restored Broker is synchronized with the other Brokers in the territory. Review the following points and perform the steps that apply to your situation.

If you know for certain that the backup was created after the last metadata change was made to the territory (that is, the restored Broker has exactly the same set of client groups and document types as the other Brokers in the territory), you do not need to take any additional steps.

If you are not certain that the restored Broker has same set of client groups and document types as the rest of the territory and that Broker does not host a gateway, you can perform the following steps to resynchronize it with the territory.

1. Remove the Broker from the territory as described in Removing a Broker from a Territory.

2. Add the Broker back to the territory as described in Adding Brokers to a Territory.

This action causes the Broker to resynchronize itself with the territory. Its client groups and document types will be brought up to date. Additionally, the subscription lists that it maintains for the other Brokers in the territory will be regenerated.

If you are not certain that the restored Broker has same set of client groups and document types as the territory and if the Broker hosts a gateway, you will need to manually update its set of client groups and document types to match those in the territory. One way to do this is to export the definitions from one of the Brokers in the territory and import them into this Broker. For procedures, see Managing Client Groups.