Novell GROUPWISE 7 - DATABASES Manual page 25

Synchronizing Database
2 9
Information
In general, synchronization of object information throughout your GroupWise
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
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.
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.
60. When waiting for replication to take
®
does not appear in the Address Book in some
Synchronizing Database Information
®
system occurs
29
395