54
GroupWise 7 Multi-System Administration Guide
no
vd
ocx (
E
NU)
10
Au
gu
st
200
6
9.4 Planning the Location of the Domain
Database Backup Directories
Because the domain database is critical to the performance of GroupWise, you should always create
a backup copy of the domain databases you will be manipulating. This ensures that an original
version of each database is available should you make a mistake, or if any problems should arise
during the merge process. You can always return to the former configurations while you correct any
problems encountered.
9.5 Planning GroupWise System Connections
The merge cannot occur unless Site #1 is able to make a direct connection to the Site #2 domain
being merged. You should have direct system connections established between Site #1 and Site #2
so that you can open the databases. If you are able to connect to Site #2 and have appropriate rights,
you can create external domains, release secondary domains, and merge domains in the GroupWise
View.
If you cannot open the domain databases to be merged (you do not have the necessary rights and/or
the systems cannot be connected), you need to use copies of each Site #2 domain database for
making the direct connections.
So that the database copies will accurately mirror the live databases, you and the other GroupWise
administrator involved with the merge should avoid making any administrative changes in
GroupWise after you have made the copies of the Site #2 databases. GroupWise clients can function
in the two systems while you run the merge against the copy.
If you are the Site #1 administrator, you create directories for the Site #2 database copies (both the
original Site #2 primary domain and the newly-released Site #2 domain databases). During the
merge process, you target each of these directories to merge that domain to the Site #1 system.
When the merge process is completed, you copy the merged database copies over the live databases.
If you want to merge systems that are connected through a GroupWise gateway, you should treat the
systems as if they are not connected. This is because the merge requires use of external domains.
WORKSHEET
Under
Item 15: Paths to Site #1 wpdomain.dbs
, enter paths to the Site #1
wpdomain.db
files.
Under
Item 6: Paths to Site #2 wpdomain.dbs
, enter paths to the Site #2
wpdomain.db
files.
Under
Item 24: Paths to Site #1 Backup Directories
, enter the path to the backup directory you will create
to hold the backup copy of the Site #1 domain database.
Under
Item 25: Paths to Site #2 Backup Directories
, enter the path to each backup directory you will
create to hold the backup copy of a Site #2 domain database. Every domain database has the same
name, so plan to either temporarily rename the database copies or to create separate directories for
them.
Summary of Contents for GROUPWISE 7 - MULTI-SYSTEM ADMINISTRATION
Page 4: ......
Page 8: ...8 GroupWise 7 Multi System Administration Guide ...
Page 12: ...12 GroupWise 7 Multi System Administration Guide ...
Page 15: ...Understanding Connection Options 15 ...
Page 16: ...16 GroupWise 7 Multi System Administration Guide ...
Page 26: ...26 GroupWise 7 Multi System Administration Guide ...
Page 32: ...32 GroupWise 7 Multi System Administration Guide ...
Page 36: ...36 GroupWise 7 Multi System Administration Guide ...
Page 40: ...40 GroupWise 7 Multi System Administration Guide ...
Page 42: ...42 GroupWise 7 Multi System Administration Guide ...
Page 44: ...44 GroupWise 7 Multi System Administration Guide ...
Page 46: ...46 GroupWise 7 Multi System Administration Guide ...
Page 48: ...48 GroupWise 7 Multi System Administration Guide ...
Page 50: ...50 GroupWise 7 Multi System Administration Guide ...