Migrating Novell ®   GroupWise ®  to Linux Paul van der Cruyssen The Network Factory [email_address] Diethmar Rimser Brain...
Agenda <ul><li>Preparing to migrate
Manual Migration vs. Wizard Migration
Domain Migration
Post Office Migration
What’s going on behind the scenes
Troubleshooting
Question and Answer </li></ul>
Planning the Migration <ul><li>Health Check first
Contents check on all post Offices </li><ul><li>Resolve all problems and errors </li></ul></ul>
Planning the Migration <ul><li>Planning </li><ul><li>Is hardware being replaced?
New hosts virtualised? </li></ul></ul>
Special Considerations <ul><li>Case sensitivity </li><ul><li>On Linux, Novell ®  GroupWise ® , will expect all lowercase f...
ConsoleOne on Windows workstation </li></ul></ul></ul>
The Migration
Manual Migration vs. Wizard <ul><li>Manual Migration is “easy” - if you understand Linux
Wizard is more “hidden” </li><ul><li>More things to “go wrong”
Much easier if you aren't that comfortable with Linux </li></ul></ul>
Manual Migration <ul><li>Install the Agents on the Linux Server
Copy Novell ®  GroupWise ®  data to Linux Server
Configure the Agents
Load the Agents </li></ul>Sounds simple huh?
Wizard Migration <ul><li>Run the Wizard </li></ul>Sounds even more simple
Manual Migration vs. Wizard <ul><li>If it's that simple why don't we just use the wizard? </li><ul><li>Path...
There is no control over the destination
Log File locations
Clustering </li></ul></ul>
Manual Migration
Prerequisites <ul><li>A Linux Server
NCPFS on Linux Server * </li><ul><li>This allows you to mount a drive to a NetWare ®  Server </li></ul><li>SMBFS on Linux ...
Novell ®  GroupWise ®  Linux software
ConsoleOne ®  and snapins on Linux server </li></ul>* Depending on what you are migrating from
Which File System <ul><li>Recommended Choices </li><ul><li>NSS
EXT3
Reiser
EXT3 with H-Tree? </li><ul><li>Currently avoid </li></ul><li>XFS </li><ul><li>Currently avoid </li></ul></ul></ul>
Which Linux? <ul><li>Open Enterprise Server </li><ul><li>Manageability </li><ul><li>Integrated with Novell ®  eDirectory ™
Novell Client ™  / NCP ™  access to all file systems
Linux User Management
Novell Remote Manager </li></ul><li>Novell Cluster Services ™ </li></ul><li>SUSE ®  Linux Enterprise Server  </li><ul><li>...
Data Preparation Belt, Braces and Binder Twine! Run a change case utility to make all files  lower case before you start  ...
Server Configuration <ul><li>Install SUSE ®  Linux Enterprise Server and  partition disk </li><ul><li>Partitioning scheme ...
swap 2GB
/var – 10 GB
/srv GroupWise ®  data partition </li><ul><li>dbcopy,  3 times post office size
tsafsgw, 2 times post office size </li></ul><li>/srv/backup or /srv/restore partition is an option </li></ul><li>Logical v...
LVM or EVMS? </li></ul></ul></ul></ul>
Accessing File Systems <ul><li>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 </li><ul><li>(or is that OK?) </li></ul></ul>
Moving Your Post Office <ul><li>Phase One </li><ul><li>Install agent software on your Linux server for all objects you pla...
GWIA
WebAccess Agent
WebAccess Application </li></ul><li>Make sure ngwguard.db is lower case before running
Mount a drive to your NetWare ®  server </li><ul><li>ncpmount -S server -A 123.123.123.123 -U userid -P password /mnt/netw...
Moving Your Post Office <ul><li>Use DBCopy </li><ul><li>Run dbcopy to make first pass copy of the post office </li><ul><li...
– 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. </li></ul><li>The first pass copy can be run days prior to the final copy, or  imm...
Configuring Post Office <ul><li>Configuring Agent </li><ul><li>Creates POA startup file
Configures gwha.conf  </li></ul><li>Start POA on Linux server for testing </li><ul><li>/opt/novell/groupwise/agents/bin/gw...
Connect to test – specify the IP address
Shut down this POA </li></ul>
Post Office Migration – Phase Two <ul><li>Stop the source Post Office Agent
Edit Post Office configuration </li><ul><li>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 </li></ul></ul>
Post Office Configuration– Phase Two <ul><li>Rebuild the PO </li><ul><li>Rebuild to  c:temp
Rename the old wphost.db
Copy the new wphost.db </li></ul></ul>
Migrating Post Office – Phase Two <ul><li>Use DBCopy </li><ul><li>Run dbcopy to make the second pass copy of the post offi...
Upcoming SlideShare
Loading in …5
×

Cl210

724 views

Published on

Novell Brainshare 2010 Amsterdam

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Cl210

  1. 1. Migrating Novell ® GroupWise ® to Linux Paul van der Cruyssen The Network Factory [email_address] Diethmar Rimser BrainAgents [email_address]
  2. 2. Agenda <ul><li>Preparing to migrate
  3. 3. Manual Migration vs. Wizard Migration
  4. 4. Domain Migration
  5. 5. Post Office Migration
  6. 6. What’s going on behind the scenes
  7. 7. Troubleshooting
  8. 8. Question and Answer </li></ul>
  9. 9. Planning the Migration <ul><li>Health Check first
  10. 10. Contents check on all post Offices </li><ul><li>Resolve all problems and errors </li></ul></ul>
  11. 11. Planning the Migration <ul><li>Planning </li><ul><li>Is hardware being replaced?
  12. 12. New hosts virtualised? </li></ul></ul>
  13. 13. Special Considerations <ul><li>Case sensitivity </li><ul><li>On Linux, Novell ® GroupWise ® , will expect all lowercase filenames </li></ul><li>Management </li><ul><li>You need to decide how to access your GW domain </li><ul><li>ConsoleOne ® on the Linux server
  14. 14. ConsoleOne on Windows workstation </li></ul></ul></ul>
  15. 15. The Migration
  16. 16. Manual Migration vs. Wizard <ul><li>Manual Migration is “easy” - if you understand Linux
  17. 17. Wizard is more “hidden” </li><ul><li>More things to “go wrong”
  18. 18. Much easier if you aren't that comfortable with Linux </li></ul></ul>
  19. 19. Manual Migration <ul><li>Install the Agents on the Linux Server
  20. 20. Copy Novell ® GroupWise ® data to Linux Server
  21. 21. Configure the Agents
  22. 22. Load the Agents </li></ul>Sounds simple huh?
  23. 23. Wizard Migration <ul><li>Run the Wizard </li></ul>Sounds even more simple
  24. 24. Manual Migration vs. Wizard <ul><li>If it's that simple why don't we just use the wizard? </li><ul><li>Path...
  25. 25. There is no control over the destination
  26. 26. Log File locations
  27. 27. Clustering </li></ul></ul>
  28. 28. Manual Migration
  29. 29. Prerequisites <ul><li>A Linux Server
  30. 30. NCPFS on Linux Server * </li><ul><li>This allows you to mount a drive to a NetWare ® Server </li></ul><li>SMBFS on Linux Server * (usually there by default) </li><ul><li>This allows you to mount a drive to a Windows Server </li></ul><li>Adequate Disk Space for Migration
  31. 31. Novell ® GroupWise ® Linux software
  32. 32. ConsoleOne ® and snapins on Linux server </li></ul>* Depending on what you are migrating from
  33. 33. Which File System <ul><li>Recommended Choices </li><ul><li>NSS
  34. 34. EXT3
  35. 35. Reiser
  36. 36. EXT3 with H-Tree? </li><ul><li>Currently avoid </li></ul><li>XFS </li><ul><li>Currently avoid </li></ul></ul></ul>
  37. 37. Which Linux? <ul><li>Open Enterprise Server </li><ul><li>Manageability </li><ul><li>Integrated with Novell ® eDirectory ™
  38. 38. Novell Client ™ / NCP ™ access to all file systems
  39. 39. Linux User Management
  40. 40. Novell Remote Manager </li></ul><li>Novell Cluster Services ™ </li></ul><li>SUSE ® Linux Enterprise Server </li><ul><li>One free server license with Novell GroupWise ® purchase* </li></ul></ul>* - “Or as many as your Novell GroupWise system Requires”
  41. 41. 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/
  42. 42. Server Configuration <ul><li>Install SUSE ® Linux Enterprise Server and partition disk </li><ul><li>Partitioning scheme </li><ul><li>boot – ext3 – 5GB+
  43. 43. swap 2GB
  44. 44. /var – 10 GB
  45. 45. /srv GroupWise ® data partition </li><ul><li>dbcopy, 3 times post office size
  46. 46. tsafsgw, 2 times post office size </li></ul><li>/srv/backup or /srv/restore partition is an option </li></ul><li>Logical vs. primary </li><ul><li>Only four primary partition permitted (primary or extended) </li><ul><li>Multiple extended partitions?
  47. 47. LVM or EVMS? </li></ul></ul></ul></ul>
  48. 48. Accessing File Systems <ul><li>Use NCP ™ to access domains on NetWare ® servers or OES2 Linux servers
  49. 49. Use SMB/CIFS to access domains on SUSE ® Linux Enterprise Server or Windows servers
  50. 50. Using NFS will result in File Lock (820E) errors </li><ul><li>(or is that OK?) </li></ul></ul>
  51. 51. Moving Your Post Office <ul><li>Phase One </li><ul><li>Install agent software on your Linux server for all objects you plan to migrate </li><ul><li>Agents
  52. 52. GWIA
  53. 53. WebAccess Agent
  54. 54. WebAccess Application </li></ul><li>Make sure ngwguard.db is lower case before running
  55. 55. Mount a drive to your NetWare ® server </li><ul><li>ncpmount -S server -A 123.123.123.123 -U userid -P password /mnt/netware/server </li></ul></ul></ul><ul><li>NCPFS is slow </li></ul>
  56. 56. Moving Your Post Office <ul><li>Use DBCopy </li><ul><li>Run dbcopy to make first pass copy of the post office </li><ul><li>dbcopy –p –m –f –k <source> <destination>
  57. 57. – p Post Office Migration
  58. 58. – m This is a migration – storelowercase and case conversion
  59. 59. -f First pass of a migration
  60. 60. -k do not calculate database sizes etc. </li></ul><li>The first pass copy can be run days prior to the final copy, or immediately preceding </li></ul></ul>
  61. 61. Configuring Post Office <ul><li>Configuring Agent </li><ul><li>Creates POA startup file
  62. 62. Configures gwha.conf </li></ul><li>Start POA on Linux server for testing </li><ul><li>/opt/novell/groupwise/agents/bin/gwpoa @startup.poa –show </li></ul></ul><ul><li>Watch via the “-show” window
  63. 63. Connect to test – specify the IP address
  64. 64. Shut down this POA </li></ul>
  65. 65. Post Office Migration – Phase Two <ul><li>Stop the source Post Office Agent
  66. 66. Edit Post Office configuration </li><ul><li>Post Office UNC path (do this first)
  67. 67. POA IP address
  68. 68. POA Platform
  69. 69. Ports (if needed)
  70. 70. Log file path
  71. 71. SSL cert/key file paths
  72. 72. Remote Library Storage area path
  73. 73. LDAP server Trusted Root certificate for LDAP authentication </li></ul></ul>
  74. 74. Post Office Configuration– Phase Two <ul><li>Rebuild the PO </li><ul><li>Rebuild to c:temp
  75. 75. Rename the old wphost.db
  76. 76. Copy the new wphost.db </li></ul></ul>
  77. 77. Migrating Post Office – Phase Two <ul><li>Use DBCopy </li><ul><li>Run dbcopy to make the second pass copy of the post office </li><ul><li>dbcopy –p –m –s –k <source> <destination>
  78. 78. – p Post Office Migration
  79. 79. – m This is a migration – storelowercase and case conversion
  80. 80. – s Second pass of a migration
  81. 81. – k Still do not calculate database sizes etc. </li></ul></ul><li>DO NOT USE –l or -o switches! </li></ul>
  82. 82. Remote Library Storage Area <ul><li>May need to manually copy remote library storage area to Linux server
  83. 83. Modify storage path in ConsoleOne ®
  84. 84. Do this before starting the POA </li></ul>
  85. 85. Post Office Migration <ul><li>Start the POA on the Linux server, verify that you can log in and send mail in and out of the GWIA </li><ul><li>and to another post office on another server </li></ul></ul>
  86. 86. Migrating Domains and Gateways
  87. 87. Domain Migration <ul><li>Gateways – Kill or Keep? </li><ul><li>If you have other Gateways running GWIA etc </li><ul><li>Kill – Cleaner in the new environment </li></ul><li>No other Gateways </li><ul><li>Kill – Create temporary gateways </li></ul><li>If you really insist – yes it will work </li></ul></ul>YMMV
  88. 88. Domain Migration <ul><li>The Domain does not require a two step migration process, because it is typically a “fast” process </li><ul><li>Clean out queues from “old” and invalid information
  89. 89. Clean out “problem” and “log” directories
  90. 90. Stop the GWIA
  91. 91. Stop the GWINTER
  92. 92. Stop any other gateways
  93. 93. Delete the Gateways (save the gwac.db first)
  94. 94. Stop the MTA </li></ul></ul>
  95. 95. Migrating the Domain <ul><li>Mount your source server
  96. 96. Run dbcopy –d –m <source> <destination> </li><ul><li>– d domain copy
  97. 97. – m migration </li></ul></ul>
  98. 98. Domain Migration <ul><li>In ConsoleOne ® , change the IP addresses and paths for all migrated objects (including gateways)
  99. 99. Verify the link configuration for the migrated domain </li></ul>
  100. 100. Domain Migration <ul><li>Edit domain configuration </li><ul><li>Domain UNC path
  101. 101. MTA IP address
  102. 102. MTA Platform
  103. 103. Ports (if needed)
  104. 104. Log file path
  105. 105. Message log path (if enabled)
  106. 106. SSL cert/key file paths
  107. 107. Run the Agent Configuration module from the Linux Install application </li></ul></ul>
  108. 108. If You MUST Migrate Gateways
  109. 109. Gateways – GWIA <ul><li>Edit GWIA settings in ConsoleOne ® </li><ul><li>Change Platform to Linux
  110. 110. Modify Network Address settings </li><ul><li>Bind Exclusively to TCP/IP Address </li><ul><li>Allows coexistence with Postfix (Watch out for SLES10 SP3) </li></ul></ul><li>Modify /dhome path (if not in current gwia.cfg)
  111. 111. Modify Log path
  112. 112. Modify SSL path </li><ul><li>May need to create new certificates for new server </li></ul></ul><li>Change MX record to point to new DNS name
  113. 113. Run the GWIA configuration module in the Linux installation program </li></ul>
  114. 114. Gateways – WebAccess <ul><li>If running remote, edit starup file to point to new UNC for the new domain location
  115. 115. Configure the WebAccess Agent with the Installation software
  116. 116. Install and Configure WebAccess application on Linux Server </li><ul><li>If application is on another server, copy commgr.cfg to application directory to use new agent IP address </li></ul></ul>
  117. 117. Domain Migration Start the MTA Start the Internet Agent Start the WebAccess Agent
  118. 118. Verify Your Migration Verify that all portions of your migration have been successful
  119. 119. The Novell ® Migration Wizard
  120. 120. Prerequisites – NetWare ®
  121. 121. Prerequisites – Windows
  122. 122. Source Server
  123. 123. Destination Server
  124. 124. Software Location
  125. 125. Select Component to Migrate
  126. 126. Auto Detect /Add Post Office <ul><ul><li>Looks in SYS:SYSTEM for GRPWISE.NCF and agent startup files
  127. 127. Add Post Office to configure manually
  128. 128. Destination path is cosmetic </li></ul></ul>
  129. 129. Post Office Migration – Phase One
  130. 130. Behind the Scenes – Phase One <ul><li>Creates directory structure on Linux server
  131. 131. Copies and installs RPM’s to Linux server
  132. 132. Mounts source server </li><ul><li>NCP ™ mount to Netware ®
  133. 133. Samba mount to Windows </li></ul><li>Runs dbcopy –a 127.0.0.1 –p –m –f –k –u 5001 </li><ul><li>-a sends status update to update utility
  134. 134. -p designates a post office copy
  135. 135. -m to migrate to lower case
  136. 136. -f first pass (phase one copy)
  137. 137. -k don’t compute size before copy
  138. 138. -u port for –a parameter </li></ul></ul>
  139. 139. Behind the Scenes – Phase One <ul><li>Creates POA startup file
  140. 140. Configures gwha.conf
  141. 141. Starts POA on Linux server for testing
  142. 142. Removes RPM files (if selected)
  143. 143. Shuts down POA </li></ul>
  144. 144. Post Office Migration – Phase One
  145. 145. Post Office Configuration
  146. 146. Post Migration Configuration <ul><li>Edit Post Office configuration </li><ul><li>Post Office UNC path (do this first)
  147. 147. POA IP address
  148. 148. POA Platform
  149. 149. Ports (if needed)
  150. 150. Log file path
  151. 151. SSL cert/key file paths
  152. 152. Remote Library Storage area path
  153. 153. LDAP server Trusted Root certificate for LDAP authentication </li></ul></ul>
  154. 154. Post Office Migration – Phase Two
  155. 155. Behind the Scenes – Phase Two <ul><li>Mounts source server
  156. 156. dbcopy –a 127.0.0.1 –m –s –i <date> –u 5001 </li><ul><li>-a sends status update to update utility
  157. 157. -m to migrate to lower case
  158. 158. -s second pass (phase two copy) </li><ul><li>-i incremental copy based on date </li></ul><li>-u port for –a parameter </li></ul><li>dbcopy executes gwcheck call for /storelowercase option </li><ul><li>When –s option is used </li></ul></ul>
  159. 159. Behind the Scenes – Phase Two <ul><li>Migration utility ships with own version of dbcopy </li><ul><li>Optimized for performance </li></ul><li>Removes temp files
  160. 160. Dismounts source server </li></ul>
  161. 161. Remote Library Storage Area <ul><li>May need to manually copy remote library storage area to Linux server
  162. 162. Modify storage path in ConsoleOne ® </li></ul>
  163. 163. Post Office Migration
  164. 164. Domain Migration
  165. 165. Add Domain
  166. 166. Add Agent – GWIA
  167. 167. Add Agent – GWIA
  168. 168. Behind the Scenes – Domain <ul><li>One pass only
  169. 169. Creates directory structure on Linux server
  170. 170. Copies and installs RPM’s to Linux server </li><ul><li>Includes GWIA and GWINTER, but not WebAccess application </li></ul><li>Mounts source server
  171. 171. Runs dbcopy –a 127.0.0.1 –d –m –k –u 5001 </li><ul><li>-a sends status update to utility
  172. 172. -d designates a domain copy
  173. 173. -m to migrate to lower case
  174. 174. -k don’t compute size before copy
  175. 175. -u port for –a parameter </li></ul></ul>
  176. 176. Domain Migration
  177. 177. Domain Migration <ul><li>Edit domain configuration </li><ul><li>Domain UNC path
  178. 178. MTA IP address
  179. 179. MTA Platform
  180. 180. Ports (if needed)
  181. 181. Log file path
  182. 182. Message log path (if enabled)
  183. 183. SSL cert/key file paths </li></ul></ul>
  184. 184. Gateways – GWIA <ul><li>Edit GWIA settings in ConsoleOne ® </li><ul><li>Change Platform to Linux
  185. 185. Modify Network Address settings </li><ul><li>Bind Exclusively to TCP/IP Address </li><ul><li>Allows coexistence with Postfix </li></ul></ul><li>Modify /dhome path (if not in current gwia.cfg)
  186. 186. Modify Log path
  187. 187. Modify SSL path </li><ul><li>May need to create new certificates for new server </li></ul></ul><li>Change MX record to point to new DNS name </li></ul>
  188. 188. Domain Migration
  189. 189. Post Migration Tips <ul><li>Verify outbound MTP IP address for Post Offices after domain migration (use HTTP Console)
  190. 190. Start/Stop agents without UI </li><ul><li>/etc/init.d/grpwise start <agentname> </li><ul><li>Or rcgrpwise start <agentname> </li></ul><li>/etc/init.d/grpwise stop <agent>
  191. 191. /etc/init.d/grpwise status </li></ul><li>Start agents with UI </li><ul><li>/opt/novell/groupwise/agents/bin/gwpoa –show @startup.poa </li></ul></ul>
  192. 192. Troubleshooting <ul><li>Utility log file </li><ul><li>gwsvrmig_MM-DD-YYYY.log </li><ul><li>In gwsvrmig directory or temp directory </li></ul><li>Check log for errors </li></ul><li>dbcopy log file </li><ul><ul><li><po>/<date>gwbk.001 </li></ul></ul><li>ssh </li><ul><li>Firewall issues – enable ssh port 22 </li></ul><li>nfsmount/Samba mounts </li><ul><li>Verify reads/writes to mounted file systems </li></ul></ul>
  193. 193. Linux Mount Point
  194. 194. L inux Path in C1
  195. 195. Mount Point for Linux <ul><li>C1, Tools, GroupWise ® System Operations, System Preferences … , Linux Settings
  196. 196. /mnt
  197. 197. Within mnt create a link which leads to your GroupWise system
  198. 198. Will be the central anchor of your administration </li></ul>
  199. 199. Mount point for Linux (example) „ w ithin mnt create a link which leads to your GroupWise ® system ” <ul><li>A domain database is located in /mail/gwsys/do1/do
  200. 200. Windows will see: SERVER/Volume:gwsys/do1/do or servervolumegwsysdo1do
  201. 201. Therefore a redirection will lead from oes-linuxmail into /mail
  202. 202. Within /mnt directory a symbolic link: ln –s /mail „server+volume“ </li></ul>
  203. 203. Special Case - NSS-Volumes <ul>NSS volumes will be found at /media/nss (capital letters; i.e. /media/nss/MAIL) Therefore change SERVERMAILgroupwisedomain into /media/nss/MAIL/groupwise/domain ln –s /media/nss SERVER </ul>
  204. 204. Special Case - NSS-Volumes (2) <ul>ln –s /media/nss SERVER How to assemble a path: <li>/mnt
  205. 205. /SERVER (= /media/nss)
  206. 206. /MAIL (= /media/nss/MAIL)
  207. 207. /gwsys/do1/do (= /media/nss/MAIL/gwsys/ ...) </li></ul>
  208. 208. Accessing GroupWise ® on NetWare ® <ul>i.e.: server: nwserver, 172.17.2.1 ncpmount –S nwserver –A 172.17.2.1 –U .admin.users.company –P novell /mnt/nwserver </ul>
  209. 209. Accessing Other Linux Locations <ul>i.e.: server: lxserver, share: mail mount –t smbfs –o username root password novell //lxserver/mail /mnt/lxserver/mail </ul>
  210. 210. Accessing Windows-Based Domain <ul>i.e.: server: msserver, share: mail mount –t smbfs –o username root password novell //msserver/mail /mnt/lxserver/mail </ul>
  211. 212. 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.

×