Migrating Novell GroupWise to Linux

Migrating Novell ®

GroupWise to Linux ®

Robin Redgrave Tim Heywood
Collaboration Technical Specialist CTO, NDS8
rredgrave@novell.com tim.heywood@nds8.co.uk

Agenda

• Preparing to migrate
• Manual Migration vs. Wizard Migration
• Domain Migration
• Post Office Migration
• What’s going on behind the scenes
• Troubleshooting
• Question and Answer

2 © Novell, Inc. All rights reserved.

Planning the Migration

• Health Check first

• Contents check on all post Offices

– Resolve all problems and errors


Planning the Migration

• Planning

– Is hardware being replaced?

– New hosts virtualised?


Special Considerations

• Case sensitivity

– On Linux, Novell GroupWise , will expect all lowercase
® ®

filenames

• Management
– You need to decide how to access your GW domain
> ConsoleOne on the Linux server
®

> ConsoleOne on Windows workstation


Manual Migration vs. Wizard

• Manual Migration is “easy” - if you understand
Linux

• Wizard is more “hidden”
– More things to “go wrong”

– Much easier if you aren't that comfortable with Linux


Manual Migration

• Install the Agents on the Linux Server

• Copy Novell GroupWise data to Linux Server
® ®

• Configure the Agents

• Load the Agents

Sounds simple huh?


Wizard Migration

• Run the Wizard

Sounds even more simple


Manual Migration vs. Wizard

• If it's that simple why don't we just use the wizard?

– Path...
– There is no control over the destination
– Log File locations
– Clustering


Prerequisites

• A Linux Server
• NCPFS on Linux Server *
– This allows you to mount a drive to a NetWare Server
®

• SMBFS on Linux Server * (usually there by default)
– This allows you to mount a drive to a Windows Server

• Adequate Disk Space for Migration
• Novell GroupWise Linux software
® ®

• ConsoleOne and snapins on Linux server
®

* Depending on what you are migrating from

Which File System

• Recommended Choices
– NSS

– EXT3

– Reiser

– EXT3 with H-Tree?
> Currently avoid
– XFS

> Currently avoid


Which Linux?

• Open Enterprise Server
– Manageability
> Integrated with Novell eDirectory
®
™

> Novell client / NCP access to all file systems
™

> Linux User Management
> Novell Remote Manager

– Novell Cluster Services ™

• SUSE Linux Enterprise Server
®

– One free server license with Novell GroupWise purchase*
®

* - “Or as many as your Novell GroupWise system Requires”

Data Preparation

Belt, Braces and Binder Twine!

Run a change case utility to make all files
lower case before you start

http://www.febooti.com/


Server Configuration

• Install SUSE Linux Enterprise Server and
®

partition disk
– Partitioning scheme
> boot – ext3 – 5GB+
> swap 2GB
> /var – 10 GB
> /srv GroupWise data partition
®

» dbcopy, 3 times post office size
» tsafsgw, 2 times post office size
> /srv/backup or /srv/restore partition is an option
– Logical vs. primary
> Only four primary partition permitted (primary or extended)
» Multiple extended partitions?
» LVM or EVMS?

Accessing File Systems

• Use NCP to access domains on NetWare servers or
®

OES2 Linux servers

• Use SMB/CIFS to access domains on SUSE Linux ®

Enterprise Server or Windows servers

• Using NFS will result in File Lock (820E) errors
– (or is that OK?)


Moving Your Post Office

• Phase One
– Install agent software on your Linux server for all objects you plan
to migrate
> Agents
> GWIA
> WebAccess Agent
> WebAccess Application
– Make sure ngwguard.db is lower case before running
– Mount a drive to your NetWare server ®

> ncpmount -S server -A 123.123.123.123 -U userid -P password /mnt/netware/server

• NCPFS is slow


Moving Your Post Office

• Use DBCopy
– Run dbcopy to make first pass copy of the post office
> dbcopy –p –m –f –k <source> <destination>

> –p Post Office Migration
> –m This is a migration – storelowercase and case conversion
> -f First pass of a migration
> -k do not calculate database sizes etc.

– The first pass copy can be run days prior to the final copy, or
immediately preceding


Configuring Post Office

• Configuring Agent

– Creates POA startup file
– Configures gwha.conf

• Start POA on Linux server for testing
– /opt/novell/groupwise/agents/bin/gwpoa @startup.poa –show

• Watch via the “-show” window
• Connect to test – specify the IP address

• Shut down this POA

Post Office Migration – Phase Two

• Stop the source Post Office Agent

• Edit Post Office configuration
– Post Office UNC path (do this first)

– POA IP address

– POA Platform

– Ports (if needed)

– Log file path

– SSL cert/key file paths

– Remote Library Storage area path

– LDAP server Trusted Root certificate for LDAP authentication

Post Office Configuration– Phase Two

• Rebuild the PO

– Rebuild to c:temp
– Rename the old wphost.db
– Copy the new wphost.db


Migrating Post Office – Phase Two

• Use DBCopy
– Run dbcopy to make the second pass copy of the post office
> dbcopy –p –m –s –k <source> <destination>

> –p Post Office Migration
> –m This is a migration – storelowercase and case conversion
> –s Second pass of a migration
> –k Still do not calculate database sizes etc.

• DO NOT USE –l or -o switches!


Remote Library Storage Area

• May need to manually copy remote library storage
area to Linux server

• Modify storage path in ConsoleOne ®

• Do this before starting the POA


Post Office Migration

• Start the POA on the Linux server, verify that you
can log in and send mail in and out of the GWIA
– and to another post office on another server


Migrating Domains and Gateways

Domain Migration

• Gateways – Kill or Keep?
– If you have other Gateways running GWIA etc

> Kill – Cleaner in the new environment
– No other Gateways
> Kill – Create temporary gateways
– If you really insist – yes it will work

YMMV


Domain Migration

• The Domain does not require a two step migration
process, because it is typically a “fast” process
– Clean out queues from “old” and invalid information

– Clean out “problem” and “log” directories

– Stop the GWIA

– Stop the GWINTER

– Stop any other gateways

– Delete the Gateways (save the gwac.db first)

– Stop the MTA

Migrating the Domain

• Mount your source server

• Run dbcopy –d –m <source> <destination>

–d domain copy
–m migration


Domain Migration

• In ConsoleOne , change the IP ®

addresses and paths for all migrated
objects (including gateways)

• Verify the link configuration for the
migrated domain


Domain Migration

• Edit domain configuration
– Domain UNC path
– MTA IP address
– MTA Platform
– Log file path
– Message log path (if enabled)
– Run the Agent Configuration module from the Linux
Install application


Gateways – GWIA

• Edit GWIA settings in ConsoleOne ®

– Change Platform to Linux
– Modify NetWork Address settings
> Bind Exclusively to TCP/IP Address
» Allows coexistence with Postfix (Watch out for SLES10 SP3)

– Modify /dhome path (if not in current gwia.cfg)
– Modify Log path
– Modify SSL path
> May need to create new certificates for new server

• Change MX record to point to new DNS name
• Run the GWIA configuration module in the Linux
installation program

Gateways – WebAccess

• If running remote, edit starup file to point to new UNC
for the new domain location

• Configure the WebAccess Agent with the
Installation software

• Install and Configure WebAccess application on
Linux Server
– If application is on another server, copy commgr.cfg to
application directory to use new agent IP address


Domain Migration

Start the MTA

Start the Internet Agent

Start the WebAccess Agent


Verify Your Migration

Verify that all portions of your migration have
been successful


The Novell Migration Wizard
®

Prerequisites – NetWare ®


Prerequisites – Windows


Source Server


Destination Server


Software Location


Select Component to Migrate


Auto Detect /Add Post Office

– Looks in SYS:SYSTEM for GRPWISE.NCF and agent
startup files
– Add Post Office to configure manually

– Destination path is cosmetic


Post Office Migration – Phase One


Behind the Scenes – Phase One

• Creates directory structure on Linux server
• Copies and installs RPM’s to Linux server
• Mounts source server
– NCP mount to Netware ®

– Samba mount to Windows
• Runs dbcopy –a 127.0.0.1 –p –m –f –k –u 5001
– -a sends status update to update utility
– -p designates a post office copy
– -m to migrate to lower case
– -f first pass (phase one copy)
– -k don’t compute size before copy
– -u port for –a parameter

Behind the Scenes – Phase One

• Creates POA startup file

• Configures gwha.conf

• Starts POA on Linux server for testing

• Removes RPM files (if selected)

• Shuts down POA


Post Office Migration – Phase One


Post Office Configuration


Post Migration Configuration

• Edit Post Office configuration
– Post Office UNC path (do this first)
– POA IP address
– POA Platform
– Log file path
– Remote Library Storage area path
– LDAP server Trusted Root certificate for LDAP authentication


Post Office Migration – Phase Two


Behind the Scenes – Phase Two

• dbcopy –a 127.0.0.1 –m –s –i <date> –u 5001
– -a sends status update to update utility
– -s second pass (phase two copy)
> -i incremental copy based on date

• dbcopy executes gwcheck call for /storelowercase
option
– When –s option is used


Behind the Scenes – Phase Two

• Migration utility ships with own version of dbcopy

– Optimized for performance

• Removes temp files

• Dismounts source server


Remote Library Storage Area

• May need to manually copy remote library storage
area to Linux server

• Modify storage path in ConsoleOne ®


Post Office Migration


Domain Migration


Add Domain


Add Agent – GWIA


Behind the Scenes – Domain

• One pass only
• Creates directory structure on Linux server
• Copies and installs RPM’s to Linux server
– Includes GWIA and GWINTER, but not
WebAccess application
• Runs dbcopy –a 127.0.0.1 –d –m –k –u 5001
– -a sends status update to utility
– -d designates a domain copy
– -k don’t compute size before copy

Domain Migration


Domain Migration

• Edit domain configuration
– Domain UNC path
– MTA IP address
– MTA Platform
– Log file path
– Message log path (if enabled)


Gateways – GWIA

• Edit GWIA settings in ConsoleOne ®

– Change Platform to Linux
– Modify NetWork Address settings
> Bind Exclusively to TCP/IP Address
» Allows coexistence with Postfix

– Modify /dhome path (if not in current gwia.cfg)
– Modify Log path
– Modify SSL path
> May need to create new certificates for new server

• Change MX record to point to new DNS name


Domain Migration


Post Migration Tips

• Verify outbound MTP IP address for Post Offices after
domain migration (use HTTP Console)
• Start/Stop agents without UI
– /etc/init.d/grpwise start <agentname>
> Or rcgrpwise start <agentname>
– /etc/init.d/grpwise stop <agent>
– /etc/init.d/grpwise status
• Start agents with UI
– /opt/novell/groupwise/agents/bin/gwpoa –show @startup.poa


Troubleshooting

• Utility log file
– gwsvrmig_MM-DD-YYYY.log
> In gwsvrmig directory or temp directory
– Check log for errors
• dbcopy log file
> <po>/<date>gwbk.001

• ssh
– Firewall issues – enable ssh port 22
• nfsmount/Samba mounts
– Verify reads/writes to mounted file systems


Migrating Novell GroupWise to Linux

Unpublished Work of Novell, Inc. All Rights Reserved.
This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc.
Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope
of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified,
translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc.
Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General Disclaimer
This document is not to be construed as a promise by any participating company to develop, deliver, or market a
product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in
making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents
of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any
particular purpose. The development, release, and timing of features or functionality described for Novell products
remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to
make changes to its content, at any time, without obligation to notify any person or entity of such revisions or
changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc.
in the United States and other countries. All third-party trademarks are the property of their respective owners.

Migrating Novell GroupWise to Linux

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Migrating Novell GroupWise to Linux (20)

More from Novell (20)

Migrating Novell GroupWise to Linux