Novell Home

How to do a Top Down Rebuild on GroupWise 6

Novell Cool Solutions: Tip

Digg This - Slashdot This

Posted: 30 Oct 2002
 

This procedure is usually recommended whenever a GroupWise system is experiencing domain or postoffice database issues or a GW system server is experiencing frequent abends or some other system critical failure in which there is a potential of compromising the integrity of your GW data. The GroupWise system Top Down Rebuild is also recommended for periodical maintenance and before any upgrades, i.e. version or patch implementation.

NOTE: Before proceeding, it is a good idea to make sure that you have a current backup of the entire GroupWise system.

The Top Down Rebuild process requires the use of ConsoleOne with the GroupWise 6 snapins installed. The Stand-alone version of GWCheck for GW 6 will also be needed to complete this procedure. For most GroupWise 6 systems, GWCheck is located in your patched GW6 Software Distribution Directory under the ..\ADMIN\UTILITY\GWCHECK folder.

When performing a top down rebuild, do it in the following manner, all steps below are done under GroupWise System in ConsoleOne...

  1. Connect to your Primary Domain. Leaving all agents up and running, right mouse click each secondary domain under GroupWise System view and from the drop select GroupWise Utilities > System Maintenance > Sync Primary with Secondary > Run > OK to the path given in the Database Path dialogue. Do this on each secondary domain before rebuilding the Primary domain.

    Note: If the following error is displayed: "Error: Access denied. Caller is not allowed access to a file", unload any GroupWise Gateways that are accessing the domain database file (GWIA, WebAccess, API, etc.).

  2. Rebuild the primary domain but do not rebuild in place, i.e. right click the Primary Domain object and select GroupWise Utilities > System Maintenance > Rebuild Database > Run, then on the Database Path dialogue in the Path to Database field, change the path to C:\temp, and click OK (Note: This path must exist.). This will create a new domain database in C:\temp. When the rebuild has completed, close out of ConsoleOne and shut down all your GW agents, i.e. MTA and POA for this domain, as well as any gateways you may have running within the primary domain. (Note: Closing ConsoleOne is only necessary after rebuilding the primary domain because you are connected to that domain and it holds the wpdomain.db open preventing the renaming of it.) In the domain dir. rename wpdomain.db to wpdomain.old and "MOVE" not "COPY" up the new wpdomain.db from your c drive, this will remove the new wpdomain.db off your hard drive so you won't accidentally copy it up to another domain. Then rename the queue directories, wpcsin to wpcsin.old, wpcsout to wpcsout.old and mslocal to mslocal.old. Bring up just the MTA and reload ConsoleOne.

  3. Repeat these steps for any secondary domains in your system. Stay connected to the primary domain when rebuilding all secondary domains.

  4. Repeat the rebuild steps respectively for your Post-offices, except you will need to be connected to the owning domain when rebuilding a post-office database. Note that the POA for any Post-office must be down before it can be rebuilt. You may also wish to rebuild any PO's in your primary domain before continuing on to rebuild all secondary domains.

  5. To do this while connected to the owning domain, right click the Post-office object and choose GroupWise Utilities > System Maintenance > Rebuild Database > Run, then on the Database Path dialogue in the Path to Database field, change the path to C:\temp, and click OK. When complete go to your PO dir. and rename wphost.db to wphost.old and "MOVE" not "COPY" the new one from your "C" drive, this will remove the new wphost.db off your hard drive so you won't accidentally copy it up to another post-office.

  6. After rebuilding each Post-Office, rename the queue directories, wpcsin to wpcsin.old, wpcsout to wpcsout.old then bring up your POA agents and run the following Stand-alone GW6 GWCHECK's against each post-office.

    Note: The following steps can be done over time but steps 1-6 should be done before calling it a night.

  7. Standalone GWCHECK Maintenance Utility for GW6

    Database Type: Post Office
    Database path: (Path to PO dir.)
    Post-office Name: Name of PO object
    Object Type: Post Office
    Databases Tab: User > Message
    Action: Analyze / Fix Databases
    Checked Options:
    First Run; Structure > Index Check > Fix Problems
    Second Run; Contents > Fix Problems

  8. When you complete each post-office go to the POA screen for that PO on the server and do the following key command... press CTRL |> Shift > Q this will recreate the PO index..

See TID10070541 for more information or updates.

Related Links:


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell