Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo
Lessons Learned: Novell ®  Open Enterprise Server Upgrades Made Easy Martin Weiss Senior Technical Specialist [email_address] Dr. Frieder Schmidt Senior Technical Specialist [email_address]
Agenda Before Starting the Migration
Novell ®  Open Enterprise Server Implementation Guidelines
Migration Processes
The Novell ®  Open Enterprise Server  2 Migration Toolkit
Before Starting the Migration
Reasons for Migrating End of NetWare ®  General Support 3 rd  party support has waned
March 7, 2010 – Start extended support New Features Dynamic Storage Technology
Domain Services for Windows
Virtualization
Enhanced scalability – 64-bit support Linux and Open Source New possibilities
Linux certifications
Building Your Knowledge  Novell ®  Open Enterprise Server 2 Upgrade Resources Training Courses Migration and upgrade
Free Training Best Practices Guide Live document
User comments
Quick response time
Real migration scenarios Novell Community Upgrade/migration articles
Novell CoolSolutions
Wiki
Migration forums Social Media Twitter:  twitter.com/novelloes
Linkedin Groups
Facebook
YouTube Learning Resources
Pre-Upgrade/Migration - Analyze and Review the Environment Know your Environment Analyze using Novell ®  Support Advisor
Verify and document the source environment Review, Fix and Stabilize Solve existing issues
Apply latest patches before upgrading Analyze the Services File, print, DNS, DHCP, access protocols
Check that the OES2 services fulfill your requirements
Plan the New Environment New Environment Create a written concept Design your target platform OES2 SP2  Services
32 or 64 bit
RAM replacement Other Applications Anti-Virus and Backup
GroupWise ®
ZENworks ®
Identity Manager
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
Prepare Your Existing Environment (2) Name Resolution DNS
SLP
HOSTS (Old, new and temp  servers) Timesync Migrate from Timesync to NTP eDirectory ™  Security Verify SDI + PKI
Can the CA Private Key be exported?
Use SDIDIAG and iManager PKI Plugin eDirectory ™  Core Review structure, partitioning, replication
Versions, patch level, and schema  (at 8.8?)
Unique naming, ID, and Posix Attributes
Novell ®  Open Enterprise Server Things to Think About
Novell ®  Open Enterprise Server Things to Think About Define and Follow your “new” standards Standards Linux is case sensitive (User, Groups and other objects)
Uniqueness Naming system device
Local ext3 and LVM
/boot / (root) /tmp /var /home File System Layout Install only what is really required and used
1. Install, 2. Patch, 3. Configure Packet / Pattern Detection Use Bonding for fault tolerance (active-backup) LAN Connectivity Use DM-MPIO if possible

More Related Content

Cl212

Editor's Notes

  1. Do we need to mention iManager for DNS Migration??
  2. f
  3. 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.
  4. 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