Presentation on theme: "Migrate GroupWise Post Office to Linux from NetWare"— Presentation transcript:
1 Migrate GroupWise Post Office to Linux from NetWare Morris BlackhamNovell, Inc.Danita ZanreCaledonia
2 Who am I?16 yrs working with WP Office, GroupWiseOriginal WordPerfect Office “Swat” teamConsultant with teltrust.com/dotOne5 yrs as GWIA QA engineerCurrently development manager for GW CPR maintenance team
3 Agenda Why run GroupWise on Linux Preparing to migrate Domain MigrationPost Office MigrationWhat’s going on behind the scenesTroubleshootingDemoQ & A
4 Better application fault handling and recovery Why GroupWise on LinuxImproved stabilityFewer operating system faultsReduced impact from other application faultsBetter application fault handling and recoveryGroupWise agents restart within secondsCore files are generated within secondsLower overall impactNo database corruptions with agent crashesMinimal database corruption on hardware/power failures
5 Major Differences in Linux OS Extremely stable OSVery few system failuresLong periods between server restartsApplication crashes do not affect server or other applicationsApplications run in protected memory space by design
6 Planning the Migration Choose Linux operating system, OES or SLESOESManageabilityIntegrated with eDirectoryNovell client / NCP access to all filesystemsLinux User ManagementNovell Remote ManagerNovell Clustering ServicesSLES1 free server license with GroupWise purchase
7 Preparing Linux Server Install and configure serverGroupWise data partitionReiserfs is recommended file systemPartition size depends on post office backup methoddbcopy, 3 times post office sizetsafsgw, 2 times post office size
8 Prerequisites – NetWare NOTE: ncpfs does not appear to be included as a package with OES SP2. You must download and install it manually.
16 Behind the scenes – Phase One Creates directory structure on Linux serverCopies and installs RPM’s to Linux serverMounts source serverNCP mount to NetwareSamba mount to WindowsRuns dbcopy –a –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
17 Behind the scenes – Phase One Creates POA startup fileConfigures gwha.confStarts POA on Linux server for testingRemoves RPM files (if selected)Shuts down POA
20 Post Migration Configuration Edit Post Office configurationPost Office UNC path (do this first)POA IP addressPOA Platformports (if needed)Log file pathSSL cert/key file pathsRemote Library Storage area pathLDAP server Trusted Root certificate for LDAP authentication
22 Behind the scenes – Phase Two Mounts source serverdbcopy –a –m –s –i <date> –u 5001-a sends status update to update utility-m to migrate to lower case-s second pass (phase two copy)-i incremental copy based on date-u port for –a parameterdbcopy executes gwcheck call for /storelowercase optionWhen –s option is used
23 Behind the scenes – Phase Two Migration utility ships with own version of dbcopyOptimized for performanceRemoves temp filesDismounts source server
30 Behind the scenes – Domain One pass onlyCreates directory structure on Linux serverCopies and installs RPM’s to Linux serverIncludes GWIA and GWINTER, but not WebAccess applicationMounts source serverRuns dbcopy –a –d –m –k –u 5001-a sends status update to utility-d designates a domain copy-m to migrate to lower case-k don’t compute size before copy-u port for –a parameter
33 Edit GWIA settings in ConsoleOne Gateways - GWIAEdit GWIA settings in ConsoleOneChange Platform to LinuxModify NetWork Address settingsBind Exclusively to TCP/IP AddressAllows coexistence with PostfixModify /dhome path (if not in current gwia.cfg)Modify Log pathModify SSL pathMay need to create new certificates for new serverChange MX record to point to new DNS name
34 Install and Configure WebAccess application on Linux Server Gateways – WebAccessIf running remote, edit starup file to point to new UNC for the new domain locationInstall and Configure WebAccess application on Linux ServerIf application is on another server, copy commgr.cfg to application directory to use new agent IP address
41 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 DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. 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. 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.
Your consent to our cookies if you continue to use this website.