Novell GROUPWISE 7 Databases
VIII
Databases
Chapter 25, “Understanding GroupWise Databases,” on page 373
Chapter 26, “Maintaining Domain and Post Office Databases,” on page 377
Chapter 27, “Maintaining User/Resource and Message Databases,” on page 385
Chapter 28, “Maintaining Library Databases and Documents,” on page 391
Chapter 29, “Synchronizing Database Information,” on page 395
Chapter 30, “Managing Database Disk Space,” on page 399
Chapter 31, “Backing Up GroupWise Databases,” on page 407
Chapter 32, “Restoring GroupWise Databases from Backup,” on page 411
Chapter 33, “Retaining User Messages,” on page 419
Chapter 34, “Standalone Database Maintenance Programs,” on page 423
novdocx (en) 11 December 2007
VIII
Databases
371
novdocx (en) 11 December 2007
372 GroupWise 7 Administration Guide
25
Understanding GroupWise
novdocx (en) 11 December 2007
Databases
Your GroupWise® system includes numerous databases where vital information is stored.
Section 25.1, “Domain Databases,” on page 373
Section 25.2, “Post Office Databases,” on page 373
Section 25.3, “User Databases,” on page 374
Section 25.4, “Message Databases,” on page 374
Section 25.5, “Library Databases,” on page 374
Section 25.6, “Guardian Databases,” on page 375
25.1 Domain Databases
The domain database (wpdomain.db) in each domain contains all administrative information for
the domain, including:
Address information about all GroupWise objects (such as users and resources), post offices,
and gateways in the domain
System configuration and linking information for the domain’s MTA
Address and message routing information to other domains
25
The first domain you create is the primary domain. In the primary domain, the wpdomain.db file
contains all administrative information for your entire GroupWise system (all domains, post offices,
users, and so on). Because the wpdomain.db file in the primary domain is so crucial, you should
back it up regularly and keep it secure. See Section 31.1, “Backing Up a Domain,” on page 407.
You can re-create your entire GroupWise system from the primary domain wpdomain.db file;
however, if the primary domain wpdomain.db file becomes unusable, you can no longer make
administrative updates to your GroupWise system.
Every domain you create after the primary domain is a secondary domain. The contents of
secondary domains are automatically synchronized with the primary domain.
For the location of the domain database, see “Domain Directory” in GroupWise 7 Troubleshooting
3: Message Flow and Directory Structure. For additional domain information, see Section 40.3,
“Information Stored in the Domain,” on page 606.
25.2 Post Office Databases
The post office database (wphost.db) in each post office contains all administrative information
for the post office, including a copy of the GroupWise Address Book. This information is necessary
for users to send messages to others in the GroupWise system.
For the location of the post office database, see “Post Office Directory” in GroupWise 7
Troubleshooting 3: Message Flow and Directory Structure. For more post office information, see
Section 35.3, “Information Stored in the Post Office,” on page 464.
Understanding GroupWise Databases
373
25.3 User Databases
Each member of the post office has a personal database (userxxx.db) that represents the user’s
mailbox. The user database contains the following:
Message header information
Pointers to messages
Personal groups
Personal address books
Rules
When a member of another post office shares a folder with one or more members of the local post
office, a “prime user” database (puxxxxx.db) is created to store the shared information. The
“prime user” is the owner of the shared information.
Local user databases and prime user databases are stored in the ofuser directory in the post office.
Because resources are addressable just like users, resources also have user databases.
novdocx (en) 11 December 2007
For the location of user databases in the post office, see “Post Office Directory” in GroupWise 7
Troubleshooting 3: Message Flow and Directory Structure. For more post office information, see
Section 35.3, “Information Stored in the Post Office,” on page 464.
25.4 Message Databases
Each member of the post office is assigned to a message database (msgnnn.db) where the body
portions of messages are stored. Many users in a post office share a single message database. There
can be as many as 255 message databases in the post office (numbered from 0 to 254). Message
databases are stored in the ofmsg directory in the post office.
Outgoing messages from local senders are stored in the message database assigned to each sender.
Incoming messages from users in other post offices are stored in the message database with the same
name as the message database assigned to the sender in his or her own post office. In each case, only
one copy of the message is stored in the post office, no matter how many members of the post office
it is addressed to.
For the location of message databases in the post office, see “Post Office Directory” in GroupWise 7
Troubleshooting 3: Message Flow and Directory Structure. For more post office information, see
Section 35.3, “Information Stored in the Post Office,” on page 464.
25.5 Library Databases
A library is a collection of documents and document properties stored in a database system that can
be managed and searched. You do not need to set up libraries unless you are using GroupWise
Document Management Services (DMS). See Part VII, “Libraries and Documents,” on page 291.
The databases for managing libraries are stored in the gwdms directory and its subdirectories in the
post office.
The dmsh.db file is a database shared by all libraries in the post office. It contains information
about where each library in the post office is located.
374 GroupWise 7 Administration Guide
Each library has its own subdirectory in the gwdms directory. In each library directory, the
dmxxnn01-FF.db files contain information specific to that library, such as document properties
and what users have rights to access the library.
For the location of library databases in the post office, see “Post Office Directory” in GroupWise 7
Troubleshooting 3: Message Flow and Directory Structure. For more post office information, see
Section 35.3, “Information Stored in the Post Office,” on page 464.
The actual documents in a library are not kept in the library databases. They are kept in a document
storage area, which consists of a series of directories for storing documents. Documents are
encrypted and stored in BLOBs (binary large objects) to make document management easier. A
document, its versions, and related objects are stored together in the same BLOB.
A document storage area might be located in the post office itself, or in some other location where
more storage space is available. If it is located in the post office, the document storage area can
never be moved. Therefore, storing documents in the post office directory structure is not usually
recommended. If it is stored outside the post office, a document storage area can be moved when
additional disk space is required.
See Chapter 22, “Creating and Managing Libraries,” on page 299 and Chapter 23, “Creating and
Managing Documents,” on page 335 for more information about Document Management Services.
novdocx (en) 11 December 2007
25.6 Guardian Databases
The guardian database (ngwguard.db) serves as the master copy of the data dictionary
information for the following subordinate databases in the post office:
User databases (userxxx.db)
Message databases (msgnnn.db)
Prime user databases (puxxxxx.db)
Library databases (dmsh.db and dmxxnn01-FF.db)
The guardian database is vital to GroupWise functioning. Therefore, the POA has an automated
back-up and roll-forward process to protect it. The POA keeps a known good copy of the guardian
database called ngwguard.fbk. Whenever it modifies the ngwguard.db file, the POA also
records the transaction in the roll-forward transaction log called ngwguard.rfl. If the POA
detects damage to the ngwguard.db file on startup or during a write transaction, it goes back to
the ngwguard.fbk file (the “fall back” copy) and applies the transactions recorded in the
ngwguard.rfl file to create a new, valid and up-to-date ngwguard.db.
In addition to the POA back-up and roll-forward process, you should still back up the
ngwguard.db, ngwguard.fbk, and ngwguard.rfl files regularly to protect against media
failure. Without a valid ngwguard.db file, you cannot access your e-mail. With current
ngwguard.fbk and ngwguard.rfl files, a valid ngwguard.db file can be rebuilt should the
need arise.
The ngwguard.dc file is the structural template for building the guardian database and its
subordinate databases. Also called a dictionary file, the ngwguard.dc file contains schema
information, such as data types and record indexes. If this dictionary file is missing, no additional
databases can be created in the post office.
Understanding GroupWise Databases 375
novdocx (en) 11 December 2007
376 GroupWise 7 Administration Guide
26
Maintaining Domain and Post
novdocx (en) 11 December 2007
Office Databases
Occasionally, it is necessary to perform maintenance tasks on domain databases (wpdomain.db)
or post office databases (wphost.db). The frequency depends on the reliability of your network
and your own experience of how often problems are likely to occur. The following tasks help you
maintain the integrity of your domain and post office databases:
Section 26.1, “Validating Domain or Post Office Databases,” on page 377
Section 26.2, “Recovering Domain or Post Office Databases,” on page 378
Section 26.3, “Rebuilding Domain or Post Office Databases,” on page 381
Section 26.4, “Rebuilding Database Indexes,” on page 383
NOTE: Unfortunately, damage to databases cannot be prevented. A power outage can occur in the
middle of a write to a database. A hard drive can fail. However, the GroupWise
damaged databases are very effective and should be able to resolve most damage to GroupWise
databases.
To further protect your GroupWise system against loss of domain and post office information, see
Chapter 31, “Backing Up GroupWise Databases,” on page 407 and Chapter 32, “Restoring
GroupWise Databases from Backup,” on page 411.
®
tools for repairing
26
To ensure that the same information exists in all domain and post office databases throughout your
GroupWise system, see Section 29.5, “Synchronizing the Primary Domain from a Secondary
Domain,” on page 398, Section 29.4, “Synchronizing a Secondary Domain,” on page 397, and
Section 29.2, “Synchronizing a Post Office,” on page 396.
26.1 Validating Domain or Post Office Databases
You can validate the data in the domain and post office databases at any time without interrupting
normal GroupWise operation. The frequency can vary depending on the size of your system and the
number of changes you make to users, resources, and distribution lists.
1 Make sure you have full administrative rights to the domain and post office database directories
you are validating.
®
2 In ConsoleOne
to validate the database.
3 Click Tools > GroupWise Utilities > System Maintenance.
, browse to and select the Domain object or Post Office object where you want
Maintaining Domain and Post Office Databases
377
4 Click Validate Database > Run.
5 When prompted, make sure the Path to Database is correct. If an incorrect path is displayed,
browse to and select the path to the database being validated. Click OK.
You are notified if there are any physical problems, so you can then recover or rebuild the
database.
See Section 26.2, “Recovering Domain or Post Office Databases,” on page 378 and
Section 26.3, “Rebuilding Domain or Post Office Databases,” on page 381.
novdocx (en) 11 December 2007
26.2 Recovering Domain or Post Office Databases
The database recover process corrects physical problems in the database structure, but does not
update incorrect information contained in the database.
If you receive an administrative message informing you that an internal database error has occurred,
or if you detect database damage and don’t want to take users out of GroupWise, you can recover the
database. If no errors are reported after the recover process, you do not need to take further action.
The recover process is run against a copy of the domain database (wpdomain.db) or post office
database (wphost.db). Therefore, while the recover process is running, you can continue to
access the database through ConsoleOne and you do not need to stop the MTA or the POA.
As the copy of the database is created, the recover process skips invalid records. If the number of
records in the original wpdomain.db file or wphost.db file is different from the number in the new,
valid copy, GroupWise sends an administrative message informing you that data has been lost.
When the recover process is completed, the backup database is deleted.
378 GroupWise 7 Administration Guide
Figure 26-1 The Database Recovery Process
novdocx (en) 11 December 2007
wpdomain.db
Check the number of
records (X) in wpdomain.db.
wpdomain.db
recover.ddb
Rename wpdomain.db
to recover.ddb.
creating.ddb
Read and copy records from
recover.ddb into creating.ddb. Skip
invalid records. Check the number of
records (Y) in creating.ddb.
Delete creating.ddb.
Rename recover.ddb
to wpdomain.db.
Notify the administrator
that wpdomain.db
could not be recovered.
Try rebuilding
wpdomain.db.
NO YES
creating.ddb
recover.ddb
wpdomain.db
Successful?
NO YES
wpdomain.db
wpdomain.db
Notify the administrator
that information has
been lost in the
recovery process.
recover.ddb
Delete recover.ddb.
creating.ddb
wpdomain.db
Rename creating.ddb
to wpdomain.db.
X=Y?
wpdomain.db
wpdomain.db
is useable.
wpdomain.db has been
successfully recovered.
For convenience, the agents are configured by default to automatically recover domain and post
office databases whenever a physical problem is encountered. See “Recovering the Domain
Maintaining Domain and Post Office Databases 379
Database Automatically or Immediately” on page 654 and “Recovering the Post Office Database
Automatically or Immediately” on page 526.
To recover a specific database in ConsoleOne:
1 Make sure you have network access to the domain or post office directory for the database you
are recovering.
If you have administration rights in the primary domain, you can recover the primary domain
database, the post office databases in the primary domain, and any secondary domain
databases.
From a secondary domain, you can recover the secondary domain database and the post office
databases in the secondary domain.
2 Make sure you have sufficient disk space for the copy of the database that is created during
recovery.
3 In ConsoleOne, browse to and select the Domain object or Post Office object where you want
to recover the database.
4 Click Tools > GroupWise Utilities > System Maintenance.
novdocx (en) 11 December 2007
5 Click Recover Database > Run.
6 When prompted, make sure the Path to Database is correct. If an incorrect path is displayed,
browse to and select the path to the database being validated. Click OK.
If recovery is successful, the backup database is deleted, and the new domain database is renamed to
wpdomain.db, or the new post office database is renamed to wphost.db.
If recovery fails for any reason, the backup database is copied back to wpdomain.db or
wphost.db. If any data was lost, you are notified by an administrative message.
You have several options for retrieving lost data from other sources:
If data has been lost from the primary domain, you can synchronize it with a secondary domain
that is known to contain current information. See Section 29.5, “Synchronizing the Primary
Domain from a Secondary Domain,” on page 398.
If data has been lost from a secondary domain, you can synchronize it with the primary domain.
See Section 29.4, “Synchronizing a Secondary Domain,” on page 397.
380 GroupWise 7 Administration Guide
You can also rebuild the database at a later time when you have exclusive access to the database
where the data has been lost. See Section 26.3, “Rebuilding Domain or Post Office Databases,”
on page 381.
26.3 Rebuilding Domain or Post Office Databases
In addition to correcting the physical problems resolved by the database recover process, the rebuild
process updates user and object information in a domain database (wpdomain.db) or post office
database (wphost.db). However, the process requires that no users or GroupWise agents (MTA or
POA) have access to the database during the rebuild process.
You should rebuild a domain or post office database if you encounter any of the following
conditions:
Objects are not being replicated between domains.
The agent that writes to the database went down unexpectedly.
The server where the database resides went down unexpectedly.
novdocx (en) 11 December 2007
You receive an administrative message informing you that an internal database error has
occurred or there is database damage and you think there might be data loss.
You ran the recover database process and received a notification of data loss.
When you rebuild a secondary domain database, information is retrieved from the primary domain.
When you rebuild a post office database, information is retrieved from the domain it belongs to.
During the rebuild process, a backup of the domain or post office database is created as well as a
new wpdomain.db or wphost.db. The records from the primary domain database are copied
into the new wpdomain.db. There should not be any data loss. When the rebuild process is
complete, the temporary database and the backup database are deleted.
Maintaining Domain and Post Office Databases 381
Figure 26-2 The Database Rebuilding Process
novdocx (en) 11 December 2007
wpdomain.db
Delete creating.ddb.
wpdomain.db remains
unchanged.
Primary Domain
wpdomain.db
NO YES
creating.ddb
wpdomain.db
creating.ddb
Successful?
Copy records from the primary
domain wpdomain.db
into creating.ddb.
Delete wpdomain.db.
creating.ddb
wpdomain.db
Rename creating.ddb
to wpdomain.db.
Notify the administrator
that wpdomain.db
could not be rebuilt.
wpdomain.db
Restore wpdomain.db
from backup.
wpdomain.db
wpdomain.db has been
successfully rebuilt.
To rebuild a database:
1 All GroupWise agents that might access the database must be stopped during the rebuild, as
described in “Stopping the MTA” on page 649 and “Stopping the POA” on page 520.
2 If you are rebuilding a post office database, all users should exit and you should disable the post
office before the rebuild, as described in Section 12.7, “Disabling a Post Office,” on page 195.
3 Make sure you have sufficient disk space for the copy of the database that is created during the
rebuild process.
4 In ConsoleOne, browse to and select the Domain object or Post Office object where you want
to rebuild the database.
5 Click Tools > GroupWise Utilities > System Maintenance.
382 GroupWise 7 Administration Guide
6 Click Rebuild Database > Run.
7 When prompted, make sure the Path to Database is correct. If an incorrect path is displayed,
browse to and select the path to the database being rebuilt. Click OK.
novdocx (en) 11 December 2007
26.4 Rebuilding Database Indexes
Each domain database (wpdomain.db) and post office database (wphost.db) contains three
indexes that are used to determine the order of the Address Book: the system index, the domain
index, and the post office index. When you display the system Address Book, the system index is
used. When you display a domain-level Address Book, the domain index is used, and when you
display the Address Book for a post office, the post office index is used.
The GroupWise client uses the post office database to list users. If you are in the GroupWise client
and the indexes for listing system, domain, and post office users are different than the domain
database indexes, you should rebuild the post office database indexes. The most common cause of
incorrect indexes in a post office is that the post office database was closed when you set up the list
information.
To rebuild a database index:
1 Make sure you have administrative rights to the database whose indexes you are rebuilding.
2 In ConsoleOne, browse to and select the Domain object or Post Office object where you want
to rebuild the database index.
3 Click Tools > GroupWise Utilities > System Maintenance.
Maintaining Domain and Post Office Databases 383
4 Select Rebuild Indexes for Listing, then click Run.
5 When prompted, make sure the Path to Database is correct. If an incorrect path is displayed,
browse to and select the path to the database being whose indexes are being rebuilt. Click OK.
novdocx (en) 11 December 2007
384 GroupWise 7 Administration Guide
27
Maintaining User/Resource and
novdocx (en) 11 December 2007
Message Databases
It is sometimes necessary to perform maintenance tasks on user and resource databases
(userxxx.db) and message databases (msgnnn.db). The frequency depends on the reliability of
your network and your own experience of how often problems are likely to occur. The following
tasks help you maintain the integrity of your user and message databases.
Section 27.1, “Analyzing and Fixing User and Message Databases,” on page 385
Section 27.2, “Performing a Structural Rebuild of a User Database,” on page 387
Section 27.3, “Re-creating a User Database,” on page 388
NOTE: Unfortunately, damage to databases cannot be prevented. A power outage can occur in the
middle of a write to a database. A hard drive can fail. However, the GroupWise
damaged databases are very effective and should be able to resolve most damage to GroupWise
databases.
To further protect your GroupWise users against loss of mailbox contents, see Chapter 31, “Backing
Up GroupWise Databases,” on page 407 and Chapter 32, “Restoring GroupWise Databases from
Backup,” on page 411.
To ensure that the same information exists for users and messages throughout your GroupWise
system, see Section 29.1, “Synchronizing Individual Users or Resources,” on page 395.
®
tools for repairing
27
27.1 Analyzing and Fixing User and Message Databases
The Analyze/Fix option of Mailbox/Library Maintenance looks for problems and errors in user and
resource databases (userxxx.db) and/or message databases (msgnnn.db) and then fixes them if
you select the Fix Problems option. You can analyze databases individually or you can analyze all
user, resource, and/or message databases in one or more post offices.
To analyze and repair user, resource, and/or message databases:
®
1 In ConsoleOne
individual users or resources.
or
Browse to and select one or more Post Office objects to select all user and/or message
databases in the post office.
2 Click Tools > GroupWise Utilities > Mailbox/Library Maintenance.
, browse to and select one or more User or Resource objects to check
Maintaining User/Resource and Message Databases
385
3 From the Action drop-down menu, select Analyze/Fix Databases.
novdocx (en) 11 December 2007
4 Select from the following options:
Structure: When a user experiences a problem that is related to the user, message, or library
databases, you should perform a structure check. The structure check verifies the integrity of
the databases and reports the amount of space that could be recovered. If there is a structural
problem, the databases are rebuilt with free space reclaimed.
Index Check: If you select Structure, you can also select Index Check. You should run an
index check if a user tries to open a message and gets a read error, or when sent items that show
a delivered status in the Properties window do not appear in the recipient’s mailbox. An index
check can be time-consuming.
Contents: The user databases (located in the ofuser directory) do not contain user messages.
Messages are contained in the message databases under the ofmsg directory. However, the
message databases do not contain the message attachments; these are located in the offiles
directory. A contents check analyzes references to other items. For example, in the user
database, Mailbox/Library Maintenance verifies that any referenced messages actually exist in
the message database. In the message database, it verifies that any attachments that are
referenced actually exist in the attachment directories.
Collect Statistics: If you selected Contents, the Collect Statistics option is available to collect
and display statistics about the post office, such as the number of messages and appointments in
the post office and the average number per user. In addition, you can display any user
mailboxes that have more than a specified number of items. This can help determine if some
users are using an excessive amount of disk space. If this is a problem, you might want to
encourage users to delete unneeded items or to use the Archive feature in the GroupWise client
to store messages on their local drives. You can also limit the amount of disk space each user
can have. See Section 12.3, “Managing Disk Space Usage in the Post Office,” on page 182.
Fix Problems: This option tells Mailbox/Library Maintenance to fix any problems it finds.
Otherwise, Mailbox/Library Maintenance just reports the problems.
Reset User Disk Space Totals: Recalculates the total disk space a GroupWise user is using by
reading the selected user mailboxes and updating the poll record used for disk space
management. Because disk space is user-specific, the program calculates the amount of disk
386 GroupWise 7 Administration Guide
space in use by the user in the user databases, in any of the message databases, and in the
attachment directory. Disk space limitations do not take into account the disk space used in
document libraries. This option is usually run if the user totals are not being reflected correctly.
5 Using the tabs at the bottom of the Mailbox/Library Maintenance dialog box, set the following
options:
“Databases” on page 429
“Logging” on page 429
“Results” on page 430
“Misc” on page 430
“Exclude” on page 430
Selected options can be saved for repeated use. See “Saving Mailbox/Library Maintenance
Options” on page 431.
6 Click Run to perform the Analyze/Fix operation.
Analyze/Fix can also be run using the standalone GroupWise Check program. See Section 34.1,
“GroupWise Check,” on page 423. It can also be scheduled to run on a regular basis by properly
configuring the POA. See Section 36.4.1, “Scheduling Database Maintenance,” on page 507.
novdocx (en) 11 December 2007
27.2 Performing a Structural Rebuild of a User Database
The Structural Rebuild option of Mailbox/Library Maintenance rebuilds the structure of a user or
resource database (userxxx.db) and reclaims any free space. It does not re-create the contents of
the database. If you need to recover database contents as well as structure, see Section 27.3, “Re-
creating a User Database,” on page 388.
To rebuild a user database:
1 In ConsoleOne, browse to and select one or more User or Resource objects whose database
needs to be rebuilt.
2 Click Tools > GroupWise Utilities > Mailbox/Library Maintenance.
Maintaining User/Resource and Message Databases 387
3 From the Action drop-down list, select Structural Rebuild.
4 Using the tabs at the bottom of the Mailbox/Library Maintenance dialog box, set the following
options:
“Databases” on page 429
“Logging” on page 429
“Results” on page 430
“Misc” on page 430
Selected options can be saved for repeated use. See “Saving Mailbox/Library Maintenance
Options” on page 431.
5 Click Run to perform a structural rebuild of the user database.
27.3 Re-creating a User Database
The Re-create User Database option of Mailbox/Library Maintenance rebuilds a user or resource
database (userxxx.db) and recovers any information it can. Some information is lost, such as the
folder assignments.
novdocx (en) 11 December 2007
You should never need to select this option for regular database maintenance. It is designed for
severe problems, such as replacing a user database that has been accidentally deleted and for which
you have no backup copy. A substantial amount of information is lost in the re-creation process, as
listed in “User Databases” on page 465. Because folder assignments are lost, all items are placed
into the Cabinet folder. The user must then reorganize all the items in his or her mailbox. Using
filters and searching can facilitate this process, but it is not a desirable experience. It is, however,
preferable to losing everything.
To re-create a user database:
1 In ConsoleOne, browse to and select one or more User or Resource objects that need the user
database re-created.
2 Click Tools > GroupWise Utilities > Mailbox/Library Maintenance.
388 GroupWise 7 Administration Guide
3 From the Action drop-down list, select Re-create User Database.
4 Using the tabs at the bottom of the Mailbox/Library Maintenance dialog box, set the following
options:
“Databases” on page 429
“Logging” on page 429
“Results” on page 430
“Misc” on page 430
Selected options can be saved for repeated use. See “Saving Mailbox/Library Maintenance
Options” on page 431.
5 Click Run to re-create the user database.
novdocx (en) 11 December 2007
Maintaining User/Resource and Message Databases 389
novdocx (en) 11 December 2007
390 GroupWise 7 Administration Guide
28
Maintaining Library Databases and
novdocx (en) 11 December 2007
Documents
GroupWise® Document Management Services (DMS) uses libraries as repositories for documents.
For a review of library database structure, see Section 25.5, “Library Databases,” on page 374.
Section 28.1, “Analyzing and Fixing Databases for Libraries and Documents,” on page 391
Section 28.2, “Analyzing and Fixing Library and Document Information,” on page 392
NOTE: Unfortunately, damage to databases cannot be prevented. A power outage can occur in the
middle of a write to a database. A hard drive can fail. However, the GroupWise tools for repairing
damaged databases are very effective and should be able to resolve most damage to GroupWise
databases.
28.1 Analyzing and Fixing Databases for Libraries and Documents
For libraries, the Analyze/Fix Databases option of Mailbox/Library Maintenance looks for problems
and errors in library and document databases and then fixes them if you select the Fix Problems
option.
®
1 In ConsoleOne
2 Click Tools > GroupWise Utilities > Mailbox/Library Maintenance.
, browse to and select one or more Library objects.
28
3 From the Action drop-down menu, select Analyze/Fix Databases.
4 Select from the following options:
Maintaining Library Databases and Documents
391
Structure: When a user experiences a problem that is related to the library databases, you
should perform a structure check. The structure check verifies the integrity of the databases and
reports the amount of space that could be recovered. If there is a structural problem, the
databases are rebuilt with free space reclaimed.
Index Check: If you select Structure, you can also select Index Check. An index check can be
time-consuming.
Contents: The library database (located in the gwdms directory of the post office) does not
contain documents. Documents are stored in the lib0000-FF directories. A contents check
analyzes references from libraries to documents.
Collect Statistics: If you selected Contents, the Collect Statistics option is available to collect
and display statistics about the library, such as the number and size of documents.
Fix Problems: This option tells Mailbox/Library Maintenance to fix any problems it finds.
Otherwise, Mailbox/Library Maintenance just reports the problems.
5 Using the tabs at the bottom of the Mailbox/Library Maintenance dialog box, set the following
options:
“Databases” on page 429
“Logging” on page 429
“Results” on page 430
“Misc” on page 430
novdocx (en) 11 December 2007
Selected options can be saved for repeated use. See “Saving Mailbox/Library Maintenance
Options” on page 431.
6 Click Run to perform the Analyze/Fix Databases operation on the library.
Analyze/Fix Databases can also be run using the standalone GroupWise Check program. See
Section 34.1, “GroupWise Check,” on page 423. It can also be scheduled to run on a regular basis by
properly configuring the POA. See Section 36.4.1, “Scheduling Database Maintenance,” on
page 507.
28.2 Analyzing and Fixing Library and Document Information
The Analyze/Fix Library option of Mailbox/Library Maintenance performs more library-specific
functions than Analyze/Fix Databases. For all options except Verify Library, all documents in each
of the selected library databases are checked. This can be a time-consuming process. Therefore, if
you intend to select more than one of the Analyze/Fix Library options, you can save time by
selecting each of them before clicking Run. This causes all selected options to be run against each
document, which is faster than running each option individually against all documents.
To validate library databases:
1 In ConsoleOne, browse to and select one or more Post Office objects where you want to
validate libraries.
2 Click Tools > GroupWise Utilities > Mailbox/Library Maintenance.
392 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
3 From the Action drop-down menu, select Analyze/Fix Library.
4 Select from the following options:
Ver i fy Li bra r y: This is a post office-level check. It verifies that all libraries are on the libraries
list. It also checks the schema and guarantees its integrity. If there is a problem with the
schema, it resets to a default schema to reclaim any missing items. For example, if you deleted
the Document Type property, you could recover it using this option.
Fix Document/Version/Element: This performs an integrity check to verify the following:
Each document has one or more versions linked to it.
Each version has one or more elements linked to it.
All versions are linked to a document.
All elements are linked to a version.
If there are any missing links, the missing documents or versions are created from the
information contained in the existing version or element for which the link is missing. For
example, if a version is found that shows no link to a document, a document is created from the
information contained in the version and the link is reestablished. Of course, any information in
the lost document that might have been newer than the information contained in the old version
is lost.
Ver i fy Doc u me nt Fil e s: This determines if the BLOB exists for a document and the document
is accessible. If not, an error is logged for that document. The log message does not indicate
why a file is missing or inaccessible. You can recover a file by restoring it from backup.
Possible errors that would be logged include:
If the file system on the network becomes corrupted, this tells you which documents
cannot be opened or which BLOB files are missing.
If a file was marked by someone as Read Only or Hidden, this option logs an error
indicating that the file is inaccessible.
Validate All Document Security: This option validates document security for the Author,
Creator and Security (document sharing) fields. The validation replaces the results of selecting
Maintaining Library Databases and Documents 393
the Validate Author/Creator Security option, and is more thorough. Therefore, you only need to
select one option or the other.
Synchronize User Name: The Author and Creator fields display users’ full names, not unique
IDs. If a user’s name is changed, such as for marriage, this option verifies that the user’s name
on document and version records is the same as the user’s current display name. In other words,
the Author and Creator fields in documents and versions are updated to the user’s newer name.
Remove Deleted Storage Areas: When you delete a document storage area in the Storage
Areas page of a library’s details dialog box, the document storage area and the documents
stored there remain on the system. Deleting the storage area from the library only means that
new documents are not stored there. The documents there continue to be available to users.
If you want to also remove the document storage area from the system, you have two options:
delete the storage area and its documents, or first move the documents and then delete the
storage area. The first option is not advisable, but exists so that if you have moved all of the
documents that can be moved, but some corrupted documents are left behind, you can force the
document storage area to be deleted.
You should normally select Move Documents First so that users continue to have access to
those documents from a different document storage area. With this option, all BLOBs in the
library are checked to see which documents are in the area being deleted.
novdocx (en) 11 December 2007
Reassign Orphaned Documents: Documents can occasionally become orphaned (unattached
to a user). For example, this can happen when a user leaves your organization and the user
object is removed. All documents belonging to that user are no longer available in GroupWise
searches and cannot be accessed by anyone (document security is controlled by the user listed
in the Author and Creator fields). This option lets you reassign these documents to another
user. You must select a new author from the browser menu after checking this option. The new
author you designate has access to all orphaned documents in this library.
Reset Word Lists: Documents stored in a library are indexed and inserted into a generated
word list. This allows users to search for a document by keywords as well as any word
contained within a document. The document library word list might become outdated and if
this occurs, the word list must be regenerated. This option allows the program to regenerate the
document library word list the next time an index operation is performed.
5 Using the tabs at the bottom of the Mailbox/Library Maintenance dialog box, set the following
options:
“Databases” on page 429
“Logging” on page 429
“Results” on page 430
“Misc” on page 430
Selected options can be saved for repeated use. See “Saving Mailbox/Library Maintenance
Options” on page 431.
6 Click Run to perform the Analyze/Fix Library operation.
Analyze/Fix Library can also be run using the standalone GroupWise Check program. See
Section 34.1, “GroupWise Check,” on page 423. It can also be scheduled to run on a regular basis by
properly configuring the POA. See Section 36.4.1, “Scheduling Database Maintenance,” on
page 507.
394 GroupWise 7 Administration Guide
29
Synchronizing Database
novdocx (en) 11 December 2007
Information
In general, synchronization of object information throughout your GroupWise® system occurs
automatically. Whenever you add, delete, or modify a GroupWise object, the information is
automatically replicated to all appropriate databases. Ideally, each domain database (wpdomain.db)
in your system contains original records for all objects it owns and accurately replicated records for
all objects owned by other domains. However, because unavoidable events such as power outages
and hardware problems can disrupt network connectivity, information in various databases might get
out of sync.
If you think you have a synchronization problem, especially soon after adding, deleting, or
modifying objects, it is wise to check Pending Operations to make sure your changes have been
processed. See Section 4.5, “Pending Operations,” on page 60. When waiting for replication to take
place, patience is a virtue.
When information differs between the original record and a replicated record, the original record is
considered correct. If you perform synchronization from the owning domain, the owning domain
notifies the primary domain of the correct information, then the primary domain broadcasts the
correct information to all secondary domains. Therefore, the best place to perform synchronization
is from the domain that owns the object that is out of sync. The next best place to perform
synchronization is from the primary domain, because the primary domain sends a request to the
owning domain for the correct information, then broadcasts the correct information to all secondary
domains.
29
Any GroupWise object can be synchronized:
Section 29.1, “Synchronizing Individual Users or Resources,” on page 395
Section 29.2, “Synchronizing a Post Office,” on page 396
Section 29.3, “Synchronizing a Library,” on page 397
Section 29.4, “Synchronizing a Secondary Domain,” on page 397
Section 29.5, “Synchronizing the Primary Domain from a Secondary Domain,” on page 398
29.1 Synchronizing Individual Users or Resources
Most often, you will notice a synchronization problem when a user has trouble sending a message.
Symptoms include:
The sender receives a “user is undeliverable” message.
A new user or resource created in ConsoleOne
or all post offices.
User or resource information is incorrect in the Address Book but correct in ConsoleOne.
®
does not appear in the Address Book in some
Synchronizing Database Information
395
A user or resource is listed in the Address Book as belonging to one post office but actually
belongs to another.
To synchronize individual User and/or Resource objects:
1 In ConsoleOne, connect to the domain that owns the users and/or resources, as described in
Section 9.1, “Connecting to a Domain,” on page 127.
or
Connect to the primary domain.
2 Browse to and right-click one or more User or Resource objects to synchronize, then click
Properties.
3 Make sure the correct information appears on the object’s Identification page, then click
Cancel.
4 Repeat Step 2 and Step 3 for each user or resource you need to synchronize.
5 Select each User or Resource object, then click Tools > GroupWise Utilities > Synchronize.
6 When you are asked whether to proceed, click Yes.
Current, correct information is then replicated throughout your GroupWise system.
If many User or Resource objects are being synchronized, you can check progress by viewing
pending operations. See Section 4.5, “Pending Operations,” on page 60.
After synchronization is complete, you can verify that it was successful by checking the
synchronized objects in Address Books and several post offices in your GroupWise system.
novdocx (en) 11 December 2007
If there are indications that a large number of User or Resource objects need to be synchronized,
rebuilding the post office database (wphost.db) can be preferable to synchronizing individual
objects. However, this process requires exclusive access to the post office database. See
Section 26.3, “Rebuilding Domain or Post Office Databases,” on page 381.
®
Occasionally, GroupWise user information can get out of sync with Novell
information. This requires a different type of synchronization process. See Section 41.4.1, “Using
eDirectory User Synchronization,” on page 638.
eDirectoryTM user
29.2 Synchronizing a Post Office
If information for a particular post office does not display the same throughout your GroupWise
system, you can synchronize the post office.
1 In ConsoleOne, connect to the domain that owns the post office, as described in Section 9.1,
“Connecting to a Domain,” on page 127.
or
Connect to the primary domain.
2 Browse to and right-click the Post Office object to synchronize, then click Properties.
3 Make sure the correct information appears on the post office Identification page, then click
Cancel.
4 Select the Post Office object, then click Tools > GroupWise Utilities > Synchronize.
5 When you are asked whether to proceed, click Yes .
396 GroupWise 7 Administration Guide
Current, correct post office information is then replicated throughout your GroupWise system.
After synchronization is complete, you can verify that it was successful by checking the post
office information when connected to different domains in your GroupWise system.
See also Section 26.3, “Rebuilding Domain or Post Office Databases,” on page 381.
29.3 Synchronizing a Library
If information for a library does not display the same throughout your GroupWise system, you can
synchronize the library.
1 In ConsoleOne, connect to the domain that owns the library, as described in Section 9.1,
“Connecting to a Domain,” on page 127.
or
Connect to the primary domain.
2 Browse to and right-click the Library object to synchronize, then click Properties.
3 Make sure the correct information appears on the library Identification page, then click Cancel.
4 Select the Library object, then click Tools > GroupWise Utilities > Synchronize.
5 When you are asked whether to proceed, click Yes .
novdocx (en) 11 December 2007
Current, correct library information is then replicated throughout your GroupWise system.
After synchronization is complete, you can verify that it was successful by checking the library
information when connected to different domains in your GroupWise system.
See also Section 28.2, “Analyzing and Fixing Library and Document Information,” on page 392.
29.4 Synchronizing a Secondary Domain
If information for a particular secondary domain does not display the same throughout your
GroupWise system, you can synchronize the secondary domain.
1 In ConsoleOne, connect to the primary domain, as described in Section 9.1, “Connecting to a
Domain,” on page 127.
2 If there is any doubt about the correctness of that secondary domain’s information as stored in
the primary domain database, synchronize the primary domain with the secondary domain
before proceeding, as described in Section 29.5, “Synchronizing the Primary Domain from a
Secondary Domain,” on page 398.
3 Browse to and right-click the Domain object to synchronize, then click Properties.
4 Make sure the correct information appears on the domain Identification page, then click
Cancel.
5 Select the Domain object, then click Tools > GroupWise Utilities > Synchronize.
6 When you are asked whether to proceed, click Yes .
Current, correct domain information for the secondary domain is then replicated throughout
your GroupWise system.
After synchronization is complete, you can verify that it was successful by checking the
domain information when connected to different domains in your GroupWise system.
Synchronizing Database Information 397
Loading...