May 4, 2009
The GroupWise® Server Migration Utility is a tool to help you move GroupWise components (post offices, domains, and agents) from NetWare® or Windows* servers to Linux* servers. The utility prompts you for information so that it can set up the connection between the source NetWare or Windows server where a GroupWise component is located and the destination Linux server where you want to migrate that GroupWise component. It then creates the connection, transfers the GroupWise data, and installs and starts the Linux GroupWise agent for the component.
From the Novell Downloads Web site , download the GroupWise Server Migration Utility (gwsvrmig1.1.0.exe) into a temporary directory.
Run gwsvrmig1.1.0.exe to extract the software into a convenient directory on a Windows machine that meets the system requirements for the Server Migration Utility.
This directory becomes the Server Migration Utility installation directory.
Run gwsvrmig.exe to start the GroupWise Server Migration utility.
Click Help on any page where you need assistance filling in the fields or where you want to know what the utility is doing.
The Server Migration Utility is compatible with GroupWise 7 and GroupWise 8. For detailed system requirements and migration instructions, see the GroupWise Server Migration Utility 1.1 Installation and Migration Guide on the GroupWise Utilities Documentation Web site.
The Auto-Detect feature that finds post offices and domains by examining agent startup files is not available on Windows servers. You must manually provide the locations of post offices and domains.
The Server Migration Utility does not migrate document storage areas that are located outside of the post office directory structure. Instructions for manually migrating them are available in Help and in the GroupWise Server Migration Utility Installation and Migration Guide.
The Server Migration Utility does not currently handle LDAP authentication for users in the post office. This can affect the mailbox access test that you perform after the first stage of the post office migration has been completed. If you are using LDAP authentication, be aware of the following limitations:
The LDAP server that the POA communicates with must have a valid IP address or DNS hostname configured in ConsoleOne® (). Do not use a relative address such as localhost.
If you are using SSL along with LDAP, you must manually copy the trusted root certificate (often named rootcert.der) to the Linux server if the LDAP server accepts only LDAP authentication.
If the Linux POA uses a different LDAP server after the post office has been migrated, you must reconfigure the LDAP information manually in ConsoleOne (Post Office object > ).
If the Server Migration Utility fails to establish a Samba mount to a Windows server, it tries a CIFS mount. If the cifs-mount package is not installed, you receive the following error in the utility log file:
bash: /sbin/mount.cifs: No such file or directory
The utility log file is named gwsvrmig_mmddyyyy_nnnn.log and is found in the utility installation directory if the utility can write to that location. Otherwise, it is found in the /temp directory.
To resolve this error and achieve a successful mount to the Windows server, use the option of YaST to install the cifs-mount package from your Linux installation media.
If you run test migrations, manual cleanup afterward is not necessary. However, if you want to remove the GroupWise software from the destination Linux server before performing the real migration, you must use the Linux rpm -e command to remove the software.
Use the following command to see what GroupWise RPMs have been installed:
rpm -qa | grep groupwise
Use the following command to remove each RPM:
rpm -e novell-groupwise-component-version-date
If you manually deleted the GroupWise software files without using the rpm -e command, using rpm -e for each component resolves the discrepancy between the files on disk and the files that the rpm command thinks should be installed on the server. This enables the Server Migration Utility to proceed normally the next time it runs.
The following GroupWise components cannot be migrated with the Server Migration Utility:
Monitor Agent and Monitor Application
GroupWise gateways (Exchange, Notes, Async, API, etc.)
GroupWise Messenger
Manual migration instructions for the WebAccess Application and the Monitor Agent are provided in the GroupWise 7 Installation Guide and the GroupWise Server Migration Utility 1.1 Installation and Migration Guide. Manual migration instructions for Messenger are provided in the Messenger 2 Installation Guide. GroupWise gateways are not available for Linux and therefore cannot be migrated.
The Server Migration Utility hangs when trying to connect to the Linux server if the utility is using an outdated SSH host key. To resolve the problem, delete the SSH host key from the registry. By default, PuTTY stores the host keys in the Windows registry at \HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys.
During the server migration, all uppercase subdirectoy names are converted to lowercase. If a GWIA or WebAccess directory was converted from uppercase to lowercase during the migration, an error message appears when accessing a GWIA or WebAccess object in ConsoleOne.
To resolve this problem, select the new lowercase subdirectory after the migration.
Open ConsoleOne.
Right-click a GWIA or WebAccess object and select .
Click the tab.
In the field, use the drop-down menu to select the new lowercase subdirectory.
Click to save the changes
The following sources provide information about the GroupWise Server Migration Utility:
Installation: GroupWise Server Migration Utility 1.1 Installation and Migration Guide available on the Web
Product documentation included with the software: Online Help in the utility
Online product documentation: GroupWise Utilities Documentation Web site
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page for more information on exporting Novell software.
Copyright © 2006-2009 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page and one or more additional patents or pending patent applications in the U.S. and in other countries.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.