Novell Doc: GroupWise 8 Multi-System Administration Guide

10.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 10-1 Merge Planning 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 10.1, Understanding the Merge Process.
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 10.2, Planning Administrator Rights.
3) GroupWise Objects to Delete:	None	List any eDirectory user objects, GroupWise user accounts, resources, or distribution lists that are no longer in use. Enter “none” if you have nothing to delete. For more information, see Section 10.3, Determining Which GroupWise Objects Are No Longer In Use.
4) Systems Connected? Yes No	No	If the GroupWise systems you are merging are not connected, select No; otherwise, select Yes. For more information, see Section 10.5, Planning GroupWise System Connections.
5) Site #2 Primary Domain:	Branch1	List the name of the primary domain for Site #2. For more information, see Section 10.1, Understanding the Merge Process.
6) Paths to Site #2 wpdomain.db Files:	\\gw\sys\branch1 \\gw\sys\distrib	To merge a domain from Site #2, you must supply the path to the wpdomain.db file for the domain being merged. If there are multiple domains in Site #2, list the paths for each wpdomain.db file. For more information, see Section 10.4, Planning the Location of the Domain Database Backup Directories.
7) Site #2 Name:	Lakewood	Identify the GroupWise system you want to merge into Site #1. The primary domain of this system will become a secondary domain in Site #1. Each secondary domain in Site #2 will be released so it can be merged as a primary domain. For more information, see Section 10.1, Understanding the Merge Process.
8) Site #2 External Domain Names:	Headquarters	There must be at least one direct link between a domain in Site #1 and each domain being merged from Site #2. Specify the exact name of the external domains you will create in Site #2. Each external domain you create in Site #2 must correspond to a domain of the same name in Site #1. If you selected Yes for worksheet item 12, you only need to create one external domain in Site #2 because indirect links are automatically created between the other domains in Site #1 and the domain being merged from Site #2. If you selected No for worksheet item 12, you need to create direct links from all primary and secondary domains in Site #1 to Site #2, and from all primary and secondary domains in Site #2 to Site #1. For more information, see External Domains.
9) Site #2 Time Zone:	Central	Enter the local time zone for Site #2. For more information, see Section 10.1, Understanding the Merge Process.
10) Site #2 Secondary Domains:	Distribution	List the names of all secondary domains in Site #2. One at a time, each secondary domain in Site #2 will be released to become an independent primary domain on its own to be merged into Site #1. For more information, see Section 10.1, Understanding the Merge Process.
11) Descriptions for Site #2 External Domains:	Headquarters - primary	Enter an informative description for each Site #2 external domain. For more information, see External Domains.
12) Allow Indirect Links to Site #1 Secondary Domains? Yes No	Yes	Select Yes and the merge utility automatically creates indirect links between the secondary domains in Site #1 and the domain being merged from Site #2. You can configure links later, if necessary. Select No if you want to configure all of your links before performing the merge. For more information, see Linking the Domains.
13) Site #1 External Domain Names:	Branch1 Distribution	You must have an external domain in Site #1 for each primary and secondary domain in Site #2. Specify the exact name of each external domain you will create in Site #1 that corresponds to a domain of the same name in Site #2. For more information, see External Domains.
14) Site #1 Primary Domain:	Headquarters	List the name of the primary domain for Site #1. For more information, see Section 10.1, Understanding the Merge Process.
15) Paths to Site #1 Files: wpdomain.db	\\gw\sys\headq	If you selected Yes for worksheet item 12, you will make a direct link only to the primary domain of Site #1. List the path to its wpdomain.db file. If you selected No for worksheet item 12, you will need to make direct links to all Site #1 secondary domains. List each of the paths to their wpdomain.db files. For more information, see Section 10.4, Planning the Location of the Domain Database Backup Directories.
16) Site #1 Name:	Manhattan	Identify the GroupWise system you want to be Site #1. This system will retain its primary domain status. For more information, see Section 10.1, Understanding the Merge Process.
17) Site #1 Time Zone:	Eastern	Enter the local time zone for Site #1. For more information, see Section 10.1, Understanding the Merge Process.
18) Site #1 Secondary Domains:	None	If you selected No for worksheet item 12, you will be creating direct links between the secondary domains in Site #1 and the domains being merged from Site #2. List the Site #1 secondary domains. If you selected Yes for worksheet item 12, enter “none” because indirect links are automatically made by the merge utility to secondary domains in Site #1. For more information, see Section 10.1, Understanding the Merge Process.
19) Descriptions for Site #1 External Domains:	Branch1 - primary Distribution - secondary	Enter an informative description for each Site #1 external domain. For more information, see External Domains.
20) Link Configuration Fields: Description: Link Type: Settings - Protocol: Settings: Path or UNC Path:	Headquarters Direct UNC \\gw\sys\headq (This example is only for a Headquarters link. You will need to list this information for each link.)	Fill in the fields once for each link being set up. For more information, see Linking the Domains.
21) Paths to Site #2 Temporary Holding Directories:	\\gw\sys\hold\branch1 \\gw\sys\hold\distrib	If the systems you are merging cannot be connected, and you are the administrator for Site #1, specify the paths for each temporary holding directory you will create to hold the domain databases of Site #2. Name the directories so that you can keep track of which domain the database file belongs to. For more information, see Section 10.5, Planning GroupWise System Connections.
22) Are Temporary Holding Directories for Site #2 on Another Tree? Yes No	No	If your temporary holding directories are located on a tree different than the one Site #1 is on, select Yes; otherwise, select No. If you select Yes, you will need to be logged in to the other tree during the merge. For more information, see Section 10.5, Planning GroupWise System Connections.
23) GroupWise MTAs for Sites #1 and #2:	MTA.Headquarters.Manhattan MTA.Research.Manhattan MTA.Accounting.Manhattan MTA.Branch1.Lakewood MTA.Distribution.Lakewood	The MTAs must be shut down during the merge to prevent changes from being made to the domain databases. The POAs can be left running so that users can use GroupWise during the merge. Enter the applicable MTAs for both systems. For more information, see Section 10.1, Understanding the Merge Process.
24) Paths to Site #1 Backup Directories:	\\gw\sys\bak\research \\gw\sys\bak\headq \\gw\sys\bak\account	To protect against losing information in case of error, you need a backup of each Site #1 domain database. You should place each wpdomain.db file in a separate backup directory. Enter the paths for each directory. For more information, see Section 10.4, Planning the Location of the Domain Database Backup Directories.
25) Paths to Site #2 Backup Directories:	\\gw\sys\bak\distrib \\gw\sys\bak\branch1	To protect against losing information in case of error, you need a backup of each Site #2 domain database. You should place each wpdomain.db file in a separate backup directory. Enter the paths for each directory. For more information, see Section 10.4, Planning the Location of the Domain Database Backup Directories.