Benefit from the hard-won experience gained by Novell Consulting in dozens of Novell Open Enterprise Server 2 upgrades. In this session, we will discuss the methodologies successfully used with both large and small customers. We'll also discuss prerequisites, environmental preparation, migration strategies and post-migration cleanup. Handouts containing a pre-migration discovery survey and a migration checklist will be provided.

1. Upgrading from NetWare to Novell ® ®
Open Enterprise Server on Linux:
The Novell Consulting Way
Ryan Kensrud Michael Saunders
Senior Technical Specialist Senior Technical Specialist
rkensrud@novell.com msaunders@novell.com

2. What Is the Novell Consulting Way? ®
• Develop a methodology to migrate your
NetWare environment ®
– Not just servers, but services and in which order
• Develop a repeatable process for your servers
• Lab test the process until success is assured
– Lab must mirror production as close as possible
– Use images of production servers in lab (Xen, Portlock, VMware, etc.)
– Isolate lab from production network physically and logically
• Develop user communication and change control
• Develop back-out procedures that return NetWare to
production if required
2 © Novell, Inc. All rights reserved.

3. Why Migrate from NetWare to ®
Novell Open Enterprise Server 2?
®
• Support for NetWare is going away
– Novell support®
> 3/7/2010 - End of standard support
> 3/7/2012 - End of extended support
> 3/7/2015 - End of self support
> All current and future development is for Linux
> We will not leave migrating customers hanging
– Hardware support
> Server vendors are no longer certifying NetWare for new hardware
> LAN / HBA vendors are no longer writing drivers
3 © Novell, Inc. All rights reserved.

4. Why Migrate from NetWare to ®
Novell Open Enterprise Server 2?
®
• Support for NetWare is going away (continued)
– Utility software support
> Anti-Virus vendors will shortly stop providing DAT file updates
> Tape-backup vendors will shortly stop certifying solutions for new
tape hardware
• Other reasons
– Qualified staff
> Education and training for Linux is easier to find than for NetWare
> Entry level IT professionals are more likely to know Linux than NetWare
4 © Novell, Inc. All rights reserved.

5. Why Migrate from NetWare to ®
Novell Open Enterprise Server 2?
®
• Other reasons (continued)
– Innovation has been on the Linux platform
> Dynamic storage technology
> Novell iFolder 3.x
> Domain services for windows
> Xen services
– Take advantage of modern hardware
> OES2 is a 64 bit OS
> Able to use more CPU cores
> Able to use virtualization features of CPU
5 © Novell, Inc. All rights reserved.

6. Tenets of a Migration
• Source environment must be clean, ready, and stable
• Novell Open Enterprise Server 2 configuration must
®
be complete and accurate
– OES2 is less tolerant of misconfiguration than NetWare was
®
• Most migration operations run directly on the target
server as a “pull” operation
• Most migration operations are a non-destructive copy
• Use DNS for everything
• Use a checklist during migrations
• Bulk load most of the effort before the migration
• Keep the outage window as short as possible (<1 hour)
6 © Novell, Inc. All rights reserved.

7. Overview of Migration Steps

8. Step 1: Prepare Your Environment
• All servers should be running a supported OS
– NetWare 5.1 sp8, or NetWare 6.5 sp7/8
®
– Novell Open Enterprise Server 1 sp1
®
• Novell eDirectory should be 8.7.3.9+ or 8.8+
™
on ALL servers
– 8.6 seems to work but it is unsupported
• Verify all software in use is compatible with eDirectory 8.8
– Novell ZENworks 2.x, Identity Manager 3.x, no IPX, etc.
• Perform a complete eDirectory health check
• Clean up stale login scripts
• Delete stale data
8 © Novell, Inc. All rights reserved.

9. Step 2: Plan Your Migrations
• Map out a server consolidation plan
– 1:1 at small sites unless WAN will carry consolidation
– 4:1 average at data centers
– Consolidate SLP, LDAP, and replica servers
• Map out a sequence for servers and services
– Certificate authority and LDAP should be first to move
– SLP DA services should be last to move
– Start with utility servers that have redundancy (replica, ldap, etc.)
– Move smaller work group server next as a pilot
– Finish with critical file and print servers
9 © Novell, Inc. All rights reserved.

10. Step 2: Plan Your Migrations (continued)
• Plan user facing changes
– How to deal with login scripts
> Server names likely changed if consolidating
> Volume names and paths likely changed if consolidating
> Copy and paste in text files. Easy to back-out changes
> Consider using Directory Map Objects (DMO) instead of UNC
– Client 32 upgrades and changes
> Should be at least version 4.91 sp4
> Now is the time for the scripted install with auto-update for future
> Is login server still correct or required? (requires NCP name, not DNS)
> Change SLP and LDAP to DNS entries pointing to existing servers
– iPrint agent and printer deployments if necessary (using DNS)
10 © Novell, Inc. All rights reserved.

11. Step 3: Create a Server Build Process
• Recommend using a network source for files
– It's faster than DVD and will ensure all servers are the same
– Build an SMT patch source to cache updates locally
• Create a proxy user account for server builds
– Password never expires, account never gets deleted
• Use a build process document or scripted install
• Prepare a Linux User Management (LUM) design
• Pre-populate DNS with entries for servers and services
– iPrint managers, LDAP servers, SLP DA, time source, etc.
11 © Novell, Inc. All rights reserved.

12. Step 4: Build Your First Server
• Configure Linux User Management (LUM)
• Patch the server via online updates or internal SMT
• Use it for your LDAP server during subsequent server
installs (using DNS for LDAP service)
• Move your Certificate Authority to this server
– Follow TID 3618399
– Be aware of the following links if you loose your CA
> http://www.novell.com/coolsolutions/appnote/18424.html
> http://www.novell.com/communities/node/5704/certificate-recreation-script-oes1-and-oes2
12 © Novell, Inc. All rights reserved.

13. Step 5: Build Subsequent Servers
• Follow the build documentation
• Use Pre-migration option if doing Transfer-ID method
• Cluster the servers if able
• Configure Linux User Management (LUM)
• Patch the server via online updates or internal SMT
– Especially migration tools
• Install all desired services including tape backup,
anti-virus, monitoring, etc
• Test all services before users are moved and affected
13 © Novell, Inc. All rights reserved.

14. Step 6: Execute Migrations
• Use your checklist for every action
• Be familiar with your back-out plan and prepared
to execute it each time
– You did perform a backup right?
• Have a subset of users from the business available
post migration to test and sign-off
• Have a plan to retire old server (don't allow
changes to migrated data)
14 © Novell, Inc. All rights reserved.

15. Migration Resources Available
• Novell Open Enterprise Server 2
®
Product Documentation
> http://www.novell.com/documentation/oes2/
• OES2 Migration Tools Documentation
> http://www.novell.com/documentation/oes2/upgrade_to_oes_lx/data/front.html
• OES2 Cool Solutions
> http://www.novell.com/communities/coolsolutions/upgradetooes
• OES2 Migration Best Practices Guide
> TBD (being updated and moved as of this week)
• OES2 On-Demand Training
> http://www.novell.com/training/ondemand
15 © Novell, Inc. All rights reserved.

16. Migration Resources Available (continued)
• Novell Open Enterprise Server 2
®
Knowledge Base Articles for Top Support Issues
– TID 7002862 - Troubleshooting data migration issues with miggui
– TID 7000901 - Troubleshooting OES2 Novell iPrint Migration Tool
– TID 7004455 - iPrint Migration Best Practices
– TID 3150078 - Updates Catalog Missing after Registration of OES2
– TID 3503915 - LUM Enabling Pure-ftpd
– TID 7004574 - OpenSLP vs. NetWare SLP®
– TID 7001449 - eDirectory™ not registering with SLP
– TID 7001767 - Troubleshooting data migrations with migfiles from
NetWare 6.5 to OES 2 Linux
• Novell Consulting Fast Track
– http://www.novell.com/consulting/offerings/nw_oes_migration.html
16 © Novell, Inc. All rights reserved.

17. Demos

19. 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.