428
GroupWise 8 Administration Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
3
If you do not use GWTSA or TSAFSGW to restore the post office, time-stamp the restored user
databases so that old items are not automatically purged during nightly maintenance.
3a
In ConsoleOne, browse to and select the Post Office object, then click
Tools > GroupWise
Utilities > Backup/Restore Mailbox
.
3b
On the
Backup
tab, select
Restore
, then click
Yes
.
4
Restart the POA for the post office.
5
To update the restored post office database (
wphost.db
) with the most current information
stored in the domain database, rebuild the post office database, as described in
Section 26.3,
“Rebuilding Domain or Post Office Databases,” on page 397
.
6
To update other restored databases such as user databases (
user
xxx
.db
) and message
databases (
msg
nnn
.db
) with the most current information stored in other post offices, run
Analyze/Fix Databases with
Contents
selected, as described in
Section 27.1, “Analyzing and
Fixing User and Message Databases,” on page 401
.
32.3 Restoring a Library
Typically, damage to library databases (
dmsh.db
and others) can be repaired using the database
maintenance tools provided in ConsoleOne or using GroupWise Check (GWCheck). See
Chapter 28, “Maintaining Library Databases and Documents,” on page 407
and
Section 34.1,
“GroupWise Check,” on page 439
.
If damage to the library is so severe that rebuilding databases is not possible:
1
Stop the POA that services the library.
2
Use the backup software for your platform, as listed in
Section 31.3, “Backing Up a Library
and Its Documents,” on page 424
, to restore the library.
3
Restart the POA.
4
To update the restored library databases with the most current information stored in other post
offices:
4a
In ConsoleOne, run Analyze/Fix Databases with
Contents
selected.
4b
Run Analyze/Fix Library.
For more information, see
Section 28.2, “Analyzing and Fixing Library and Document
Information,” on page 408
.
32.4 Restoring an Individual Database
Typically, damage to user and resource databases (
user
xxx
.db
) and message databases
(
msg
nnn
.db
) can be repaired using the database maintenance tools provided in ConsoleOne or using
GroupWise Check (GWCheck). See
Chapter 27, “Maintaining User/Resource and Message
Databases,” on page 401
and
Section 34.1, “GroupWise Check,” on page 439
.
If damage to an individual database is so severe that repair is not possible:
1
Make sure the user to whom the affected database belongs is not running the GroupWise client.
2
Use your backup software of choice to restore the database into the proper location in the post
office directory.
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...
