Cl212
•Transferir como ODP, PDF•
1 gostou•1,894 visualizações
Novell Brainshare 2010 Amsterdam
![Lessons Learned: Novell ® Open Enterprise Server Upgrades Made Easy Martin Weiss Senior Technical Specialist [email_address] Dr. Frieder Schmidt Senior Technical Specialist [email_address]](https://image.slidesharecdn.com/cl212-101204115333-phpapp02/85/cl212-1-320.jpg)
![Agenda ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Cl212
Semelhante a Cl212 (20)
Último
Último (20)
Cl212
- 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]
- 3. Novell ® Open Enterprise Server Implementation Guidelines
- 5. The Novell ® Open Enterprise Server 2 Migration Toolkit
- 6. Before Starting the Migration
- 9. Domain Services for Windows
- 10. Virtualization
- 15. User comments
- 19. Wiki
- 21. Linkedin Groups
- 22. Facebook
- 27. Check that the OES2 services fulfill your requirements
- 29. 32 or 64 bit
- 31. GroupWise ®
- 32. ZENworks ®
- 33. Identity Manager
- 34. Prepare Your Existing Environment (1) C:serslenocumentsresentation-templatecon-bublelueardwareerver.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
- 36. SLP
- 38. Can the CA Private Key be exported?
- 40. Versions, patch level, and schema (at 8.8?)
- 41. Unique naming, ID, and Posix Attributes
- 42. Novell ® Open Enterprise Server Things to Think About
- 45. Local ext3 and LVM
- 48. know if it is cluster or stand-alone
- 49. Verify certification of storage infrastructure for SLES SAN Connectivity
- 51. Changes in SLP (move to OpenSLP)
- 55. Install user vs. LDAP proxy users
- 56. One proxy user per service / per location / per server
- 61. CPFL & DFS / DST Support
- 63. Use DNS for Print Manager name resolution
- 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
- 75. Disable Login and clear connections for final delta-sync
- 77. Copy/consolidate and change DNS
- 79. Use DNS (CNAME) where possible
- 80. Use login scripts Dependency Cleanup
- 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. Migration “Transfer-ID” Cluster Node Not needed!
- 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
- 86. No changes to login scripts required
- 87. No changes to eDirectory ™ attributes required
- 89. No easy rollback
- 90. No chance to test
- 91. No chance to increase the load
- 92. No chance to re-design
- 94. Find and remove your dependencies
- 95. Remove forgotten “old, inherited stuff”
- 98. The Novell ® Open Enterprise Server 2 Migration Toolkit
- 99. Screenshot of the GUI
- 101. 6.0 SP5a
- 102. 6.5SP6 or later
- 103. OES1 Linux
- 104. OES2 Linux
- 106. 8.7.X
- 108. Source Linux NSS, NCP ™ and POSIX
- 109. Target OES2 NSS, NCP and POSIX
- 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
- 119. Creates duplicate printer objects (NetWare ® to Linux)
- 120. Option to “migrate” objects to same container (rename _NW)
- 121. Is a non-risk procedure if choosing 'Consolidate'
- 123. Does not configure workstations to point to new print manager
- 128. Subnet Level: Migrates the selected NetWare subnets only
- 129. Tree Level: Migrates all the servers in the tree with the associated data
- 130. After the Migration to Novell ® Open Enterprise Server
- 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. Reference Customer Witzenmann GmbH
- 137. Novell GroupWise ® 7 on NetWare
- 139. Migrated Cluster to Open Enterprise Server 2
- 140. Server Consolidation into Cluster Nodes
- 141. Storage Migrated to new SAN Storage Hardware
- 142. Implemented SAN based Backup Solution
- 144. ZENWorks ® Desktop Management 7 on Linux Servers
- 145. Updated to GroupWise ® 8 and migrated to Linux Servers
- 147. Concept
- 148. Implementation
- 149. Pilot
- 150. Testing
- 155. Upgrading to Open Enterprise Server Guide - http://www.novell.com/documentation/oes2/upgrade_to_oes_lx/ page=/documentation/oes2/upgrade_to_oes_lx/data/front.html
- 156. iPrint Migration Best Practices – TID 7004455
- 157. Other iPrint Resources – TIDS 7004109 , 7005255 , 7004910
- 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.
- 160. Supporting Slides
Notas do Editor
- 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