Information about a secondary domain that is stored in the secondary domain database is considered more current and correct than information about that secondary domain that is stored in the primary domain database. If the primary domain database contains out-of-date information, you can synchronize the primary domain from the secondary domain.
When you synchronize the primary domain database from a secondary domain database, any records the secondary domain owns, such as post offices or users added to the secondary domain, are replicated from the secondary domain database to the primary domain database.
You must use the GroupWise Administration Utility (GWAdminUtil) to synchronize the primary domain from a secondary domain because direct file access to both databases is required.
To synchronize the primary domain from a secondary domain:
From the primary domain server, establish direct file access to the secondary domain server.
On Linux, mount the file system on the secondary domain server to the primary domain server. On Windows, map a drive from the primary domain server to the secondary domain server.
Use the following command to synchronize the primary domain from the secondary domain:
gwadminutil sync --primary /path_to_primary_domain_database --domain /path_to_secondary_domain_database
To ensure that the primary domain database is totally up-to-date, repeat Step 1 and Step 2 for each secondary domain in your system.