Typically, damage to databases in a post office can be repaired using the database maintenance tools provided in ConsoleOne or using GroupWise Check (GWCheck). See Section 26.0, Maintaining Domain and Post Office Databases, Section 27.0, Maintaining User/Resource and Message Databases, and Section 34.1, GroupWise Check.
If damage to the post office was so severe that rebuilding databases is not possible:
Stop the POA for the post office.
Use the backup software for your platform, as listed in Section 31.2, Backing Up a Post Office, to restore the various databases into their proper locations in the post office directory.
Time-stamp the restored user databases so that old items are not automatically purged during nightly maintenance:
In ConsoleOne, browse to and select the Post Office object, then click .
On the tab, select , then click .
To update the restored post office database (wphost.db) with the most current information stored in the domain database, rebuild the post office database, as described in Section 26.3, Rebuilding Domain or Post Office Databases.
To update other restored databases such as user databases (userxxx.db) and message databases (msgnnn.db) with the most current information stored in other post offices, run Analyze/Fix Databases with selected, as described in Section 27.1, Analyzing and Fixing User and Message Databases.
Restart the POA for the post office.