Novell GROUPWISE 7 - MULTI-SYSTEM ADMINISTRATION, Руководство пользователя, Страница: 59 / 75

Planning the Merge 59
no
vd
ocx (
E
NU)
10
Au
gu
st
200
6
9.6.2 Merging at Different Times
You might not want to merge several systems in one session. The amount of time required depends
on how many secondary domains exist in each additional system. This is because you must release
and merge each secondary domain one at a time.
If you plan to merge your GroupWise systems at different times, you can fill in each additional
worksheet when you are ready to plan the merge for its system using this section.
9.7 Merge Planning Worksheet
The GroupWise Merge Domain Advisor helps you merge GroupWise systems. You need to prepare
for the merge by planning the location and structure of your domain databases.
Table 9-1
Merge Planning Worksheet
WORKSHEET
Do the following on each additional worksheet:
Under Item 16: Site #1 Name , enter the name of the GroupWise system to designate as Site #1.
Under Item 7: Site #2 Name , enter the name of the GroupWise system to designate as Site #2. If you are
merging three or more GroupWise systems, you will select a different system as Site #2 each time you
reuse this planning section and rerun the merge process.
Under Item 23: GroupWise MTAs for Sites #1 and #2, list the GroupWise MTAs that you need to shut
down during the merge. Because you should be including all domains in the previously combined
systems, your list should be longer for each subsequent worksheet.
Item Example Explanation
1) Merging Three or
More GroupWise
Systems?
Š
Yes
Š
No
No If you will be merging three or more
GroupWise systems, whether in one
session or at different times, select
Yes ;
otherwise, select No .
For more information, see Section 9.1,
“Understanding the Merge Process,” on
page 51
.
2) Does Administrator
Performing the Merge
Have Admin-Equivalent
Rights to Both Systems?
Š
Yes
Š
No
Yes If the administrator does not have the
necessary rights to perform the merge,
select
No ; otherwise, select Yes . The
merge utility depends on the rights of the
person logged in for access to the
applicable databases.
For more information, see Section 9.2,
“Planning Administrator Rights,” on
page 53
.