9.4 Replacing the Primary Domain Database with a Secondary Domain Database

If the primary domain database (wpdomain.db) has become so damaged that it cannot be rebuilt, and if you do not have a current backup of it, you can replace the primary domain database with the contents of a secondary domain database. You should only do this if you are confident that the secondary domain database is completely synchronized with current GroupWise domain information.

To replace the primary domain database with the contents of a secondary domain database:

  1. Make sure you have full administrative rights to the primary domain database directory.

  2. Stop the MTA for the primary domain.

  3. In ConsoleOne, connect to the secondary domain where the current database is located.

    If you need assistance with this task in a GroupWise system that includes domains on Linux servers, see Section 4.1, Select Domain.

  4. Browse to and select the Domain object for the secondary domain.

  5. Click Tools > GroupWise Utilities > System Maintenance.

    System Maintenance dialog box with Replace Primary with Secondary option available

  6. Click Replace Primary with Secondary > Run.

  7. When prompted, make sure the Path to Database field displays the path to the primary domain.

  8. (Conditional) If an incorrect path is displayed, browse to and select the path to the primary domain database, then click OK.

    ConsoleOne then updates the primary domain database with the current contents of the selected secondary domain database.

  9. When the primary domain database has been replaced, restart the MTA for the primary domain.