|
|
|
The best practice is to avoid making any changes to Domain Management Server databases during the upgrade process. If your business model cannot support management downtime during the upgrade, you can continue to manage Domain Management Servers during the upgrade process.
This creates a risk of inconsistent Domain Management Server database content between instances on different Multi-Domain Servers. The synchronization process cannot resolve these database inconsistencies.
After successfully upgrading one Multi-Domain Server, you can set its Domain Management Servers to the Active state, while you upgrade the others. Synchronization between the Domain Management Servers occurs after all Multi-Domain Servers are upgraded.
If, during the upgrade process, you make changes to the Domain Management Server database using different Multi-Domain Servers, the contents of the two (or more) databases will be different. Because you cannot synchronize these databases, some of these changes will be lost. The Domain Management Server High Availability status appears as Collision.
You must decide which database version to retain and synchronize it to the other Domain Management Servers. You then must re-enter the lost changes to the synchronized database.
