GroupWise uses two repositories for directory information: Novell Directory Services (eDirectory) and the GroupWise FLAIM or GDS databases (as discussed in Chapter 3, "Understanding the GroupWise Directory"). Maintenance of Novell Directory Services (eDirectory) is beyond the scope of this book. Suffice it to say that if eDirectory is messed up, it can cause problems for GroupWise. This section focuses on maintaining the WPDOMAIN.DB and WPHOST.DB files. Our experience is that these files do not get corrupt nearly as often as information-store databases. This is probably because they are not being written to as often as the information-store databases. Thus, it is not as critical that you run regular rebuilds of domain or post office databases. The most important thing is that your WPDOMAIN.DB filesfor all domainsare backed up regularly. Ideally, you should have this file backed up every day. Don't bother backing up the post office databases (WPHOST.DB), however. These files can be regenerated from the WPDOMAIN.DB file of the domain that owns the post office. The single most important file in a GroupWise system is the primary domain's WPDOMAIN.DB file. We recommend that you run a recover-and-index rebuild of the primary domain monthly. This cannot be automated. Fortunately, you don't have to bring anything down in order to do this. Here are the steps for a monthly maintenance of the primary domain's WPDOMAIN.DB:
These operations are simple and take very little time to perform. Consider creating a monthly task item to remind you to perform these operations on the primary domain's WPDOMAIN.DB. |