--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools



Would you like to sponsor this site?
Or buy me a beer?:

Recently Changed Pages:

View All Pages
View All Q Pages

View All Tags

Sign up for Q to post comments.

WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.

Terms And Conditions for Q users

Pages with comments

2019/06/22 10:36 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 3 Comments
2017/04/20 15:28 1 Comment
2017/04/20 15:23 1 Comment
2017/04/19 14:44 1 Comment
2017/04/17 20:10 1 Comment
2017/04/17 20:07 1 Comment
2017/04/17 19:58 1 Comment
2017/04/17 19:52 1 Comment

View All Comments


GroupWise Top Down Rebuild

Prior to performing major and or minor updates and upgrades to your groupwise system, and when your groupwise system is having trouble, you should perform a top down rebuild of your groupwise system. This is to ensure that all of your data is correct and you experience no corruption. This is especially important before support packs upgrades and version upgrades. They could convert your database to a new version which could spell disaster when there is corruption. The manual given here is tested on a single domain and postoffice groupwise 7, also giving the times it took on various sizes of the database, and taken from the Novell TID found at the bottom. Before major operations (like this one), always make a copy/backup of your data!

DOMAIN Rebuild

Unload all groupwise agents and start consoleone. Go to your primary domain, and select System Maintenance:
Select Rebuild Database:
Then change the path the rebuild database is written to:
On a brand new groupwise system, updated from groupwise 7 to SP2 to SP3 it took only a few seconds. On a 60 MB domain in an environment where there are a lot of changes and a secondary domain it still took just a few seconds, 10 at most. Afterwards you have to close consoleone, rename the old gwdomain.db, and move the new gwdomain.db to your domain directory.


Keep your agents closed and restart consoleone. Go to your post office and select System Maintenance:
Select Rebuild Database:
Then change the path the rebuild database is written to:
On a postoffice with only 5 users with each only a few emails it took only a few seconds. On a postoffice with 200 users and a database over 80 GB it still took just a few seconds, 10 at most. Afterwards you have to rename the old gwpo.db, and move the new gwpo.db to your post office directory.

Don't forget to start your agents again, and test them.

Source: Novell TID

Secondary Domains and Post Offices

After you've rebuild your primary domain you can also rebuild your secondary domains. For the domain everything is exactly the same, but before you van rebuild your secondary post office please make sure you connect to your secondary domain first. To do so, in ConsoleOne select your GroupWise System and click on Tools → GroupWise System Operations → Select Domain.

You could leave a comment if you were logged in.
groupwisetopdownrebuild.txt · Last modified: 2013/04/30 14:40 by sjoerd