Synchronizing Database Information
29
411
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
29
Synchronizing Database
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 65
. 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.
Any GroupWise object can be synchronized:
Section 29.1, “Synchronizing Individual Users or Resources,” on page 411
Section 29.2, “Synchronizing a Post Office,” on page 412
Section 29.3, “Synchronizing a Library,” on page 413
Section 29.4, “Synchronizing a Secondary Domain,” on page 413
Section 29.5, “Synchronizing the Primary Domain from a Secondary Domain,” on page 414
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
®
does not appear in the Address Book in some
or all post offices.
User or resource information is incorrect in the Address Book but correct in ConsoleOne.
A user or resource is listed in the Address Book as belonging to one post office but actually
belongs to another.
Summary of Contents for GROUPWISE 8 - DATABASES
Page 2: ...388 GroupWise 8 Administration Guide novdocx en 22 June 2009...
Page 6: ...392 GroupWise 8 Administration Guide novdocx en 22 June 2009...
Page 20: ...406 GroupWise 8 Administration Guide novdocx en 22 June 2009...
Page 40: ...426 GroupWise 8 Administration Guide novdocx en 22 June 2009...
Page 48: ...434 GroupWise 8 Administration Guide novdocx en 22 June 2009...