1 / 32

Move GW, NW -> Linux

Move GW, NW -> Linux. Václav Šamša TDP Ltd. Move GW, NW -> Linux. I'm from Prague, Czech Republic I'm working with GroupWise since WordPerfect Office 3.0 My primary objective is GroupWise and eDIR I'm founding member of GroupWiseR initiative I'm working for TDP Ltd. Move GW, NW -> Linux.

hop
Download Presentation

Move GW, NW -> Linux

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Move GW, NW -> Linux Václav Šamša TDP Ltd

  2. Move GW, NW -> Linux • I'm from Prague, Czech Republic • I'm working with GroupWise since WordPerfect Office 3.0 • My primary objective is GroupWise and eDIR • I'm founding member of GroupWiseR initiative • I'm working for TDP Ltd

  3. Move GW, NW -> Linux • Overview • Customer case • Preparation • Migration • Afterwards • Q&A

  4. Move GW, NW -> Linux • Simple example – single server GW System • Customer is running GW 6.5 on NetWare 6.5 and wants to upgrade to GroupWise 7 • Decision was made to migrate to NOWS on Linux kernel, especially because of better price • NOWS/NOES was SLES 9, now with NOES2 - SLES10 • Due to license limitations, everything must be moved to Linux • The whole operation should be done within one weekend

  5. Move GW, NW -> Linux • The only challenge is to migrate the Groupwise, file system can be moved by Novell Server Consolidation and Migration Toolkit • The migration will be done to new server HW • (if in place migration needed, than make temporary copy of NW server(mirror) and install Linux on original server HW)‏ • The configuration of client workstations should not be changed – customer wants to upgrade clients later, subsequently - possible?

  6. Move GW, NW -> Linux • Groupwise checklist • Version? - 6.5.4 • Domains? - One, primary • Post offices? - One, large (90 users, 200GB)‏ • Libraries? - three, with storage areas • Gateways? - GWIA, Webaccess • Others? - GWAVA – optional for discussion

  7. Move GW, NW -> Linux • It's recommended and with libraries very important – the Groupwise will be upgraded on the NetWare system BEFORE the migration • eDir will be checked – it's standard and Linux server has to be added in existing tree • NetWare will be upgraded to latest SP

  8. Move GW, NW -> Linux • IP addresses – VERY IMPORTANT • Netware server has just one IP address used for all GW services also - 192.168.0.3 • Need IP for Linux server - 192.168.0.7 • Need IP for GW POA and MTA – 192.168.0.8 and 192.168.0.9 • (Having dedicated address for whole groupwise or better foreach agent makes the further changes and optimalization much easier)‏

  9. Move GW, NW -> Linux

  10. Move GW, NW -> Linux CSU Internet Plzen Ustredi Hradec Brno ........

  11. Move GW, NW -> Linux CSU CSUPRI Internet Plzen Ustredi Hradec Brno ........

  12. Move GW, NW -> Linux INET CSU CSUPRI Internet Plzen Ustredi Hradec Brno ........

  13. Move GW, NW -> Linux INET CSU1 CSU2 PM CSU CSUPRI Internet Ustredi Brno Hradec ........

  14. Move GW, NW -> Linux • Tip - Check cfg files for override setting • Compare cfg file setting with C1 – remove as much as possible (.poa, .mta, gwia.cfg, .waa)‏ • Focus to IP address and port for MTP • Check the IP address and port for client connection for POA • On the other side – be ready to use cfg file to change address and port manually in case of having troubles

  15. Move GW, NW -> Linux • How to change the GW agent IP address? • Add secondary address on NW - 192.168.0.8 • Change the address of POA • Reload POA • Check MTP Link – open? • Change the address of MTA • Reload • Check MTP and PO links - open?

  16. Move GW, NW -> Linux • Changed IP/port - How to deal with clients? • use ngwnameserver • define new „void“ PO on the old IP address with task of routing clients to new PO • Use ZENworks to change the registry setting • Like tricky solutions - Use regedit /s regfile

  17. Move GW, NW -> Linux • Cookbook - Upgrade Netware • Novell Server Consolidation and Migration Toolkit needs NW 6.5sp5 & eDIR 8.6.2, but use NW 6.5sp6 & eDIR 8.7.3.9 • If migrating from NW 6.0.x – schema must be extended first from NW 6.5 CD ! • SLP • Check DA • Use named scope • Switch off IPX/SPX and test

  18. Move GW, NW -> Linux • Cookbook - Upgrade Netware - cont • eliminate print queues (unsupported on NOES)‏ • Switch to NTP, check time • check eDIR – local DB and tree incl. volumes • Check SDI – sdidiag • Check PKI and certificates - pkidiag • Check LDAP – is iManager working? • Not use PSA

  19. Move GW, NW -> Linux • Cookbook - Upgrade Groupwise • Be sure not to use 7.0, use 7.0.2 • Be sure to install new C1 – 1.36e or 1.36f • Make backup copy of all cfg files and wpdomain.db • Copy software, check .dc files! • MTA first, wait for db conversion, check ver • POA, wait for db conversion, check ver • Gateways – keep eye on restrictions and aliases • Use old gwia.cfg for setting gw 7 gwia

  20. Move GW, NW -> Linux • Cookbook – install Linux NOES • Install Novell NCP + ncpfs, Novell Linux User Management (LUM), Novell SMS (data migration), NSS • Use existing SLP DA on NW, install SLP DA on Linux • Add server to existing tree, create local replica • Create new CA and use local LDAP if new server will be the only one server afterwards

  21. Move GW, NW -> Linux • Cookbook – pure SLES • use ReiserFS, gettext, don't install POSTFIX • Install NICI • Install eDIR • Setup NTP • Install C1 • Described at cool solutions by John Hurst: http://www.novell.com/coolsolutions/feature/14539.html

  22. Move GW, NW -> Linux • Cookbook – getting Linux ready • comment – SLES can't replace NW • Check eDIR is working (possible from NW)‏ • Check iManager, LDAP, C1 /usr/ConsoleOne/bin/ConsoleOne • Create NSS volumes, move user data using migration toolkit – not related to GW

  23. Move GW, NW -> Linux • Cookbook – migrate GroupWise • install DBCopy http://www.novell.com/documentation/gw7/gw7_admin/index.html?page=/documentation/gw7/gw7_admin/data/bqpw8ct.html#bqpxea0 • install GWCheck http://www.novell.com/documentation/gw7/gw7_admin/index.html?page=/documentation/gw7/gw7_admin/data/a3n60l6.html#bqt18o4 • Mount netware volume with groupwise ncpmount -m -A server_address -S server_name -V volume -U full_user_ID -P password /mount_point

  24. Move GW, NW -> Linux • Cookbook – migrate GroupWise – PO • http://www.novell.com/documentation/gw7/gw7_install/index.html?page=/documentation/gw7/gw7_install/data/b2qsmz0.html • Due to size may take lot of time – 2 passes • ./dbcopy -m -f /po_directory /dest_directory • -f – first pass – don't copy queues (org PO is running)‏ • ./dbcopy -b /storage_area_dir /dest_dir • -b – migration of BLOB files • Be lazy - Install POA for new location • Check - ./gwpoa --show --home /po_directory --noconfig

  25. Move GW, NW -> Linux • Cookbook – migrate GroupWise – PO • Configure POA using C1 – location of PO, location of remote storage area, platform • ./dbcopy -m -i mm-dd-yyyy -s /po_dir /dest_dir • -i incremental since first pass (date not time!)‏ • -s second pass (+queues wpcsin, wpcsout)‏ • ./dbcopy -b -i mm-dd-yyyy /storage_area_dir /dest_dir

  26. Move GW, NW -> Linux • Cookbook – migrate GroupWise – PO • Use gwcheck storelowercase option to change all names to lowercase • Database Type - Post Office, select new(!) PO location, enter PO name, Object Type - Post Office, check Structure and Fix Problems, Do not check Contents/Fix Problems!, Misc tab, Support Options, specify storelowercase and RUN • Run POA, check links (MTA, GWIA, webaccess)‏

  27. Move GW, NW -> Linux • Cookbook – migrate GroupWise - domain • http://www.novell.com/documentation/gw7/gw7_install/index.html?page=/documentation/gw7/gw7_install/data/b2qsmz0.html • Small – very fast – one pass • ./dbcopy -m /domain_directory /dest_directory • Be lazy – install MTA for new location • Check - ./gwmta --show --home /domain_directory –noconfig • http://mta_server_ip_address:7180 (7181 for PO by default)‏

  28. Move GW, NW -> Linux • Cookbook – migrate GroupWise - domain • Configure domain using C1- location, platform • Gateway object - Properties - GroupWise > Identification - Subdirectory - reselect the gateway directory - must be taken for all gateways belongs to domain • Run MTA • Check links to PO, other domains, gateways

  29. Migrating GW to Linux • Cookbook – migrate GroupWise – LDAP • LDAP authentication not recommended if using webaccess unless you authenticate to eDIR using NMAS with smartcard ie • public root certificate file (like rootcert.der) from the LDAP server to the /opt/novell/groupwise/agents/bin

  30. Migrating GW to Linux • Cookbook – migrate GroupWise – SSL • LDAP authentication not recommended if using webaccess and not NMAS with smartcard ie • create a new certificate file (.crt) and a new key file (.key) for the Linux server • Store them to /opt/novell/groupwise/agents/bin which is the default location

  31. Migrating GW to Linux • Backup • /etc/opt/novell/sms/smdrd.conf • autoload: tsaf --EnableGW • autoload: tsafsgw --home /GWISE/domena --home /GWISE/postoffice • restart novell-smdrd module • Backup Exec and Backup Express tested

  32. Migrating GW to Linux Thank You! Questions?

More Related