Published on

Novell Brainshare 2010 Amsterdam

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Do we need to mention iManager for DNS Migration??
  • f
  • Prior to performing a migration, review TID 7004455. This TID lists recommended pre-check tests to perform to increase the likelihood of a successful iPrint migration. It also contains useful troubleshooting information in the event of a problem. The iPrint Migration tool copies an NLM (psminfo.nlm) from the OES 2 SP1 server to the NetWare server. The NLM is loaded on the NetWare server. The NLM reads the NetWare Print Manager database ([vol]:/ndps/xxxxxxxx.psm/psmdb.dat) and creates a text output of the database attributes and values (psmimport.xml). The printer drivers associated to the NetWare printer agents are copied to the Linux server and uploaded to the Driver Store repository using an iPrint Linux command line tool (iprntman). The /opt/novell/iprint/bin/psmimport.xml is executed using iprntman. iprntman creates the printer agents and their attributes defined in the XML file. As the iPrint migration tool heavily relies on iprntman, it is recommended to test iprntman's ability to authenticate prior to the migration. See TID 7004455 for important iPrint Migration Pre-check steps to increase the probability of a successful migration. Whether the iPrint migration succeeds or fails, users will continue to print to the source server. To test the success or failure of an iPrint migration, go to the /ipp page on the destination server (http://[IPorDNSofDestinationServer]/ipp and install printers.
  • See TID 7004109 to understand why the Consolidate migration is preferred over the Transfer-ID method when iPrint is involved. The TID also shows how to safely perform a Transfer-ID migration after the iPrint service has been migrated using the Consolidate method. Create target printer objects in the Source Printer Context An option within the iPrint Migration is to “Create target printer objects in the Source Printer Context”. Creating a new object (iPrint Linux Printer Agent Object) in the same context as the NetWare Printer Agent Object with the same name is not possible. Because of this, this option will rename the NetWare Printer Agent Object to have an _NW extension to the eDir name. By renaming the NetWare Printer Agent object, workstations pointing to that NetWare object will still be able to print. The iPrint client is not aware of the eDir name, instead, it prints to the printer object in the MOD. The name in the MOD does not change when using this feature. If the iPrint Migration does not succeed, but the migration went far enough to create the /opt/novell/iprint/bin/psmimport.xml file, you can run this command while in the /opt/novell/iprint/bin directory to complete the migration: iprntman psm –xml-import ./psmimport.xml
  • Cl212

    1. 1. Lessons Learned: Novell ® Open Enterprise Server Upgrades Made Easy Martin Weiss Senior Technical Specialist [email_address] Dr. Frieder Schmidt Senior Technical Specialist [email_address]
    2. 2. Agenda <ul><li>Before Starting the Migration
    3. 3. Novell ® Open Enterprise Server Implementation Guidelines
    4. 4. Migration Processes
    5. 5. The Novell ® Open Enterprise Server 2 Migration Toolkit </li></ul>
    6. 6. Before Starting the Migration
    7. 7. Reasons for Migrating <ul><li>End of NetWare ® General Support </li><ul><li>3 rd party support has waned
    8. 8. March 7, 2010 – Start extended support </li></ul></ul><ul><li>New Features </li><ul><li>Dynamic Storage Technology
    9. 9. Domain Services for Windows
    10. 10. Virtualization
    11. 11. Enhanced scalability – 64-bit support </li></ul></ul><ul><li>Linux and Open Source </li><ul><li>New possibilities
    12. 12. Linux certifications </li></ul></ul>
    13. 13. Building Your Knowledge Novell ® Open Enterprise Server 2 Upgrade Resources <ul><li>Training Courses </li></ul><ul><ul><li>Migration and upgrade
    14. 14. Free Training </li></ul></ul><ul><li>Best Practices Guide </li></ul><ul><ul><li>Live document
    15. 15. User comments
    16. 16. Quick response time
    17. 17. Real migration scenarios </li></ul></ul><ul><li>Novell Community </li></ul><ul><ul><li>Upgrade/migration articles
    18. 18. Novell CoolSolutions
    19. 19. Wiki
    20. 20. Migration forums </li></ul></ul><ul><li>Social Media </li></ul><ul><ul><li>Twitter:
    21. 21. Linkedin Groups
    22. 22. Facebook
    23. 23. YouTube </li></ul></ul>Learning Resources
    24. 24. Pre-Upgrade/Migration - Analyze and Review the Environment Know your Environment <ul><ul><li>Analyze using Novell ® Support Advisor
    25. 25. Verify and document the source environment </li></ul></ul>Review, Fix and Stabilize <ul><ul><li>Solve existing issues
    26. 26. Apply latest patches before upgrading </li></ul></ul>Analyze the Services <ul><ul><li>File, print, DNS, DHCP, access protocols
    27. 27. Check that the OES2 services fulfill your requirements </li></ul></ul>
    28. 28. Plan the New Environment New Environment Create a written concept Design your target platform <ul><ul><li>OES2 SP2 Services
    29. 29. 32 or 64 bit
    30. 30. RAM replacement </li></ul></ul>Other Applications <ul><ul><li>Anti-Virus and Backup
    31. 31. GroupWise ®
    32. 32. ZENworks ®
    33. 33. Identity Manager </li></ul></ul>
    34. 34. Prepare Your Existing Environment (1) C:UsersGlenDocumentspresentation-templateicon-bubleBlueHardwareserver.png AutoYaST + ZENworks Linux Management Server Source for Install and Update Easy Post-installation Frozen Patch Levels Faster than CD/DV D Based on Templates eDirectory ™ Server Cluster Node Remote / Special Purpose
    35. 35. Prepare Your Existing Environment (2) Name Resolution <ul><ul><li>DNS
    36. 36. SLP
    37. 37. HOSTS </li></ul></ul><ul><ul><li>(Old, new and temp  servers) </li></ul></ul>Timesync <ul><ul><li>Migrate from Timesync to NTP </li></ul></ul>eDirectory ™ Security <ul><ul><li>Verify SDI + PKI
    38. 38. Can the CA Private Key be exported?
    39. 39. Use SDIDIAG and iManager PKI Plugin </li></ul></ul>eDirectory ™ Core <ul><ul><li>Review structure, partitioning, replication
    40. 40. Versions, patch level, and schema (at 8.8?)
    41. 41. Unique naming, ID, and Posix Attributes </li></ul></ul>
    42. 42. Novell ® Open Enterprise Server Things to Think About
    43. 43. Novell ® Open Enterprise Server Things to Think About <ul><ul><li>Define and Follow your “new” standards </li></ul></ul>Standards <ul><ul><li>Linux is case sensitive (User, Groups and other objects)
    44. 44. Uniqueness </li></ul></ul>Naming <ul><ul><li>system device
    45. 45. Local ext3 and LVM
    46. 46. /boot / (root) /tmp /var /home </li></ul></ul>File System Layout <ul><ul><li>Install only what is really required and used
    47. 47. 1. Install, 2. Patch, 3. Configure </li></ul></ul>Packet / Pattern Detection <ul><ul><li>Use Bonding for fault tolerance (active-backup) </li></ul></ul>LAN Connectivity <ul><ul><li>Use DM-MPIO if possible
    48. 48. know if it is cluster or stand-alone
    49. 49. Verify certification of storage infrastructure for SLES </li></ul></ul>SAN Connectivity
    50. 50. Novell ® Open Enterprise Server Things to Think About <ul><ul><li>DNS (same as on NetWare ® )
    51. 51. Changes in SLP (move to OpenSLP)
    52. 52. HOSTS </li></ul></ul>Name Resolution <ul><ul><li>Move from Timesync to NTPD </li></ul></ul>Timesync <ul><ul><li>NMAS ™ + Universal Password + Password Policies
    53. 53. Implement Universal Password for AFP and CIFS? </li></ul></ul>eDirectory ™ <ul><ul><li>For what do we need LUM?
    54. 54. Convert lower, persistent search, cache only, alternate servers </li></ul></ul>Linux User Mgmt <ul><ul><li>Where to put them in eDirectory ™ ?
    55. 55. Install user vs. LDAP proxy users
    56. 56. One proxy user per service / per location / per server
    57. 57. Security </li></ul></ul>LDAP Proxy Users <ul><ul><li>LDAP integrated “Linux” DHCP </li></ul></ul>DHCP
    58. 58. Novell ® Open Enterprise Server Things to Think About <ul><ul><li>Same as on NetWare ® </li></ul></ul>DNS <ul><ul><li>Novell Storage Services ™
    59. 59. Distributed File System
    60. 60. Dynamic Storage Technology </li></ul></ul>File Services <ul><ul><li>NCP ™ / CIFS / AFP / NFS / NetStorage
    61. 61. CPFL & DFS / DST Support
    62. 62. Pure-FTP + Gateway </li></ul></ul>File Access Protocols <ul><ul><li>One driver store only
    63. 63. Use DNS for Print Manager name resolution
    64. 64. Use DSServer2/DSServer3 for LDAP fault tolerance </li></ul></ul>iPrint <ul><ul><li>Install only where required
    65. 65. Keep plugins current </li></ul></ul>iManager <ul><ul><li>See Novell Cluster Services ™ Session </li></ul></ul>Cluster Services
    66. 66. Migration Processes: Step-by-Step
    67. 67. Migration Step-by-Step eDirectory ™ Server To Rollback – just reverse the process Install New Server Add Replicas Change Replica Type Move CA and Verify SDI Move IDM Driversets Change Login Process Verify and Monitor Uninstall Old Server
    68. 68. Migration Step-by-Step Cluster (Rolling Upgrade) Remove NetWare ® Node Re-add Server as a Linux Node Migrate Resources to Linux Node Repeat steps 1-3 for all Nodes Do Final Conversion after all nodes are Linux Advantages <ul><li>No new hardware
    69. 69. Less effort </li></ul>Disadvantage <ul><li>High risk </li></ul>
    70. 70. Migration Step-by-Step Cluster (Build a New Cluster) Build New Linux Cluster Move Data using Migration Toolkit or SAN Replication Change Login Script, DNS Entries, UNC paths Remove old Servers from the tree and clean up eDirectory ™ Congratulate yourself on a successful Migration! Advantages <ul><li>Lowest Risk
    71. 71. Chance for re-design, consolidation & Test </li></ul>Disadvantage <ul><li>More Effort </li></ul>
    72. 72. Migration Step-by-Step Remote Server / Special Purpose Install New Server Move / Migrate each service Uninstall Old Server <ul><ul><li>Assign the zones to the new DNS server
    73. 73. Reconfigure clients and servers </li></ul></ul>DNS Migration <ul><ul><li>Use Migration Toolkit
    74. 74. Clean up before migrating </li></ul></ul>DHCP Migration <ul><ul><li>Use Migration Toolkit
    75. 75. Disable Login and clear connections for final delta-sync
    76. 76. Modify Login Scripts </li></ul></ul>File Migration <ul><ul><li>Use Migration Toolkit
    77. 77. Copy/consolidate and change DNS
    78. 78. Remove old queues and gateways </li></ul></ul>iPrint Migration <ul><ul><li>Move users per user / department </li></ul></ul>User Migration <ul><ul><li>Find and remove existing dependencies
    79. 79. Use DNS (CNAME) where possible
    80. 80. Use login scripts </li></ul></ul>Dependency Cleanup
    81. 81. Migration Processes: Transfer-ID
    82. 82. Migration “Transfer-ID” eDirectory ™ Server Post-Migration and Cleanup Clean Up eDirectory Check eDirectory Use Migration Tools Transfer eDirectory and Identity Verify Log Files Install New Server Install Pre-Migration pattern Install into the same context as the source server
    83. 83. Migration “Transfer-ID” Cluster Node Not needed!
    84. 84. Migration “Transfer-ID” Remote Server / Special Purpose Post-Migration and Cleanup Clean up eDirectory Configure and Check Services Install New Server Install Services that will Migrate (NSS, iPrint) Install Pre-Migration pattern Install into same context as source server Use Migration Tools Transfer eDirectory ™ and Identitity Transfer Services File, Print, iFolder, DHCP Verify Log Files
    85. 85. Transfer-ID vs. Step-by-Step Transfer-ID Comparison Advantages <ul><ul><li>No new name or IP address required
    86. 86. No changes to login scripts required
    87. 87. No changes to eDirectory ™ attributes required
    88. 88. Fast </li></ul></ul>Disadvantages <ul><ul><li>High risk
    89. 89. No easy rollback
    90. 90. No chance to test
    91. 91. No chance to increase the load
    92. 92. No chance to re-design </li></ul></ul>
    93. 93. Transfer-ID vs. Step-by-Step Recommendation and Best Practice <ul><li>Review your environment and re-design
    94. 94. Find and remove your dependencies
    95. 95. Remove forgotten “old, inherited stuff”
    96. 96. Separate services logically from server names </li><ul><li>Use DNS name resolution where possible
    97. 97. Use secondary IP addresses </li></ul><li>Start with Step-by-Step and use Transfer-ID later </li></ul>Note : Transfer-ID only migrates some applications
    98. 98. The Novell ® Open Enterprise Server 2 Migration Toolkit
    99. 99. Screenshot of the GUI
    100. 100. Supported Platforms Note – Only OES2 is supported as a destination OS, for NetWare destinations, use the older SCMT. Migration Tools Support Matrix Source OS Support <ul><ul><li>5.1 SP8
    101. 101. 6.0 SP5a
    102. 102. 6.5SP6 or later
    103. 103. OES1 Linux
    104. 104. OES2 Linux
    105. 105. Windows NT/2K/2k2 </li></ul></ul>eDirectory ™ <ul><ul><li>8.6.2 or later
    106. 106. 8.7.X
    107. 107. 8.8.X </li></ul></ul>File Systems <ul><ul><li>Source NetWare ® NSS and Traditional
    108. 108. Source Linux NSS, NCP ™ and POSIX
    109. 109. Target OES2 NSS, NCP and POSIX </li></ul></ul>
    110. 110. Migration Tools Features Service Migrations Non-destructive migration and consolidation File System iPrint CIFS AFP DHCP FTP iFolder NTP Archive and Versioning Migration Tools Migrates Several OES Services Transfer-ID Migration Scheduling E-mail Notification CLI Tools
    111. 111. File System: Migration Procedure <ul><li>Many Command Line parameters (see migfiles)
    112. 112. The GUI uses a SCMT like approach </li><ul><li>Drag/drop directories or volumes to the target
    113. 113. Select date/time or pattern based filters </li></ul><li>Uses SMS and nbackup to move data </li><ul><li>System meta data preservation = SMS Backup </li></ul></ul>
    114. 114. File System: Tips and Tricks <ul><li>Load TSAFS with /cluster and /showclustervolumesonnode on the source server </li></ul><ul><li>Use NSS /NOQUOTACHECKING on the target server </li></ul>
    115. 115. iPrint: Migration Procedure iPrint data migrated <ul><ul><li>Printer objects, printer drivers, driver profiles, print managers, ACL's, banners and printer pools </li></ul></ul>Using the GUI <ul><ul><li>Select the active print managers on both the source and the target
    116. 116. Select all or required printers to migrate </li></ul></ul>Printer Migration Naming <ul><ul><li>Printers can keep the same name and context in eDirectory ™ . The original eDirectory print objects are renamed </li></ul></ul>
    117. 117. iPrint: Migration Key Points <ul><li>TID 7004455 is the official iPrint migration best practices guide
    118. 118. The Migration tool for iPrint </li><ul><li>Requires successful iprintman authentication
    119. 119. Creates duplicate printer objects (NetWare ® to Linux)
    120. 120. Option to “migrate” objects to same container (rename _NW)
    121. 121. Is a non-risk procedure if choosing 'Consolidate'
    122. 122. Creates /opt/novell/iprint/bin/psmimport.xml
    123. 123. Does not configure workstations to point to new print manager </li></ul></ul>
    124. 124. iPrint: Workstation Migration iPrint printers installed to workstation consist of the following: <ul><ul><li>Printer agent name (without eDirectory ™ context)
    125. 125. Address to which Print Manager is bound </li></ul></ul>Two strategies to point installed printers to a new server: <ul><li>Address binding ( TID 7005255 ) </li></ul><ul><ul><li>PSMHostAddress value within etc/opt/novell/iprint/conf/ipsmd.conf </li></ul></ul><ul><li>iPrint printer agent redirection ( TID 3006726 ) </li></ul>
    126. 126. DHCP: Migration Procedure <ul><li>NetWare ® DHCP configuration is mapped to Linux DHCP </li><ul><li>The NetWare schema and Linux schema in eDirectory ™ are different
    127. 127. All the subnets get migrated inside a single DHCP service (dhcpService object) including leases </li></ul><li>The GUI and the CLI support three levels of migration </li><ul><li>Server Level: Migrates NetWare server with all the associated subnets
    128. 128. Subnet Level: Migrates the selected NetWare subnets only
    129. 129. Tree Level: Migrates all the servers in the tree with the associated data </li></ul></ul>
    130. 130. After the Migration to Novell ® Open Enterprise Server
    131. 131. Activation / Implementation of NEW Features Wait some time before new features are activated Make sure the migration was successful Monitor the system Fix any problems Implement any additional features (DST, DFS, DSfW, iFolder)
    132. 132. Reference Customer Witzenmann GmbH
    133. 133. Who is Witzenmann? <ul>...for flexible metal elements </ul><ul>Competent solver of engineering problems </ul><ul>The Pioneer Company </ul><ul>Leader in Technology </ul><ul>Germany  1900 employees Europe  950 employees America  175 employees Asia  175 employees </ul><ul>Witzenmann-Group  </ul><ul>HQ Pforzheim Germany </ul><ul>Business Objectives </ul><ul>Profitable Growth Global Supplier Technology and Innovation Leadership Quality Leader </ul><ul> </ul><ul>Product Range From miniature hose to power station expansion joint HYDRA® metal hoses, expansion joints, metal bellows, motor vehicle components and pipe supports are employed worldwide in numerous branches of industry. With more than 120 years' market experience, Witzenmann has the most extensive range of products in the branch and offers its customers tailored system solutions to meet a very wide range of demands. Witzenmann is certified in accordance with internationally recognised standards in the automotive industry and other industries. </ul>
    134. 134. The Source Environment <ul><li>~3000 Employees / ~1400 IT-User
    135. 135. 23 Locations in 17 countries worldwide, Headquarter in Germany </li></ul>Products being used <ul><li>NetWare ® 6.5 </li><ul><li>Novell Cluster Services ™ </li></ul></ul><ul><ul><li>Novell Storage Services ™ </li></ul></ul><ul><ul><li>iPrint
    136. 136. NetStorage, FTP, DNS, DHCP, SLP </li></ul></ul><ul><li>Novell ® ZENWorks ® Desktop Management 7 on NetWare
    137. 137. Novell GroupWise ® 7 on NetWare </li></ul>
    138. 138. The Target Environment <ul><li>Novell ® Open Enterprise Server 2
    139. 139. Migrated Cluster to Open Enterprise Server 2
    140. 140. Server Consolidation into Cluster Nodes
    141. 141. Storage Migrated to new SAN Storage Hardware
    142. 142. Implemented SAN based Backup Solution
    143. 143. New Antivirusprotection
    144. 144. ZENWorks ® Desktop Management 7 on Linux Servers
    145. 145. Updated to GroupWise ® 8 and migrated to Linux Servers </li></ul>
    146. 146. The Migration Project <ul><li>Analysis
    147. 147. Concept
    148. 148. Implementation
    149. 149. Pilot
    150. 150. Testing
    151. 151. Migration central office
    152. 152. Migration remote offices </li></ul><ul><li>Partners: Dell, EMC, Quantum, Commvault, McAfee </li></ul>
    153. 153. Questions and Answers
    154. 154. References <ul><li>Upgrade Community -
    155. 155. Upgrading to Open Enterprise Server Guide - page=/documentation/oes2/upgrade_to_oes_lx/data/front.html
    156. 156. iPrint Migration Best Practices – TID 7004455
    157. 157. Other iPrint Resources – TIDS 7004109 , 7005255 , 7004910 </li></ul>
    158. 159. 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.
    159. 160. Supporting Slides
    160. 161. Migration Tools Features (Continued) <ul><li>Disable login during data migration </li><ul><li>User logins are disabled during data migration for better data integrity and to minimize open file errors </li></ul><li>Sync enhancements </li><ul><li>Files skipped due to open file errors are migrated during sync, meta data changes like trustee addition etc. </li></ul><li>Multiple path selection </li><ul><li>Drag and Drop multiple paths during consolidation </li></ul><li>Non-English character directories </li><ul><li>Non-English character support using Novell Client ™ </li></ul><li>Support for cluster data migration </li></ul>