1 / 28

Upgrading to Notes/Domino ND7

Upgrading to Notes/Domino ND7. Abbreviated from… Andrea Waugh-Metzger Senior Solution Architect IBM Certified Specialist. Title slide. Agenda. Notes/Domino 7 Upgrade Information Recommended Path Key Success Factors Technical Considerations Other Considerations

ursala
Download Presentation

Upgrading to Notes/Domino ND7

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. Upgrading to Notes/Domino ND7 Abbreviated from… Andrea Waugh-Metzger Senior Solution ArchitectIBM Certified Specialist Title slide

  2. Agenda • Notes/Domino 7 Upgrade Information • Recommended Path • Key Success Factors • Technical Considerations • Other Considerations • Where to find upgrade information

  3. ND7 Upgrade Information Title slide

  4. Domino Directory Upgrade Path Servers Clients Mail Templates Applications Notes/ Domino 7 Release 6

  5. Upgrading the Domino Directory and Servers • Upgrade Admin clients at the same time • Start on the Adminp or main Directory server • Upgrade the Directory first, then server code. Start on non-user based servers, then move to mail servers, etc. • Use a tool such as TeamStudio tool to analyze Directory design structure to determine customization differences if you do not already have them documented

  6. Upgrading the Domino Directory and Servers • Use tools such as DYS Control! Suite to assist in network and server capacity analysis if considering consolidation or realignment • Test the new Directory in a development environment along with your customizations and against existing applications!

  7. Upgrading Clients • Use a Standard, repeatable, process for every user migrated • Take advantage of Business Partner tools such as Wolcott’s ADT product to assist: • Client Discovery • Deployment Tracking • Client Deployment • Management of deployment process • If you plan on doing server consolidations, move clients to the new servers as the upgrade occurs • Take advantage of the Smart Upgrade capability ???

  8. Upgrade Flow

  9. Key Success Factors(Best Practices) Title slide

  10. Key Success Factors Plan Design Pilot Production Communication & Transformation Management

  11. Phase One • Read the Release Notes – There are a number of planning issues, limitations and workarounds: for migration, version capability, DB2, Directory, clients, C&S…. • Read the documentation available in Upgrade Central • Planning is key – first step should always be determining what you will do during the upgrade. • Identify opportunities for improvement • Server consolidation • Domino Directory Cleanup • Platform change • Evaluate new features • Which ones provide immediate benefit • Which are easier to apply during a major upgrade • Which can be applied during “Phase Two”

  12. Phase One (cont’d) • Identify resources and win Management support • Human (Admins, Help Desks, Early Adopters, IBM) • Time • Funding • Determine education requirements • Build your project framework • Dates / locations • Goals / milestones • Baselines

  13. Planning

  14. Phase Two • An upgrade is only as good as the environment it goes into. • Cleanup your Mail environment • Directory customizations • Template modifications • Notes.ini parameters, configurations, etc. • Cleanup your Application environment • Remove old applications • Review design/development practices • Create a Test/Development Environment • Indicative of production • Include 3rd party applications • Create a Detailed Upgrade Plan • Use Cases • Used to validate timeframe, requirements • Provides an estimation of realistic timeframes

  15. Planning

  16. Design • Incorporate the new features in your architecture (create your server and client build models) • Resource Reservations changes • Policies – many have changed • Server Monitoring/Administration Updates • Domino Domain Monitor • Security • Setup SmartUpgrade if going to use it

  17. Pilot • Set up a pilot environment • Involve complete scenario candidates • Include different types of servers – hubs, 3rd party, mail, applications • Healthy load of users (...remember the Early Adopters?) • Support structure • Don't forget your applications • Know your environment and test early for it • Globalization, Time Zones • Clustering • Mobility • Applications • Involve many people - we all work differently

  18. Production • Use standardized, repeatable processes to deploy • Know the new features and how they work in your environment • Communicate and train the new/changed features to the users community and support communities • Announcement • Training • Cheat sheets

  19. Technical and Other Considerations Title slide

  20. Technical Considerations for Upgrading • Increased mail template size - 12.7 MB (Domino 6) vs. 15.2 MB (Domino 7) • Rooms and Resource Reservations have changed – special considerations for coexistence when replicating the ND7 RR to pre-ND7 • Pre-ND7 server cannot run Router task • RR database must be on an ND7 server • In cluster mates, pre-ND7 server cannot be first alphabetically • There are differences in the $users view in the directory • Unlike ND6.5, Extended Products can have mixed versions • Sametime 6.5, QuickPlace 7.0

  21. Technical Considerations…cont’d • Review notes.ini files for obsolete variables – like ND6, many have changed • Don’t forget about 3rd party applications like virus scan, backup, Blackberry – many vendors are still finalizing their ND7 supported code • Unlike going from R5 to ND6, ND6 to ND7 does not have an ODS change • When group calendars or managed calendars exist, make sure that client and template versions across users are compatible:

  22. Technical Considerations (cont’d) • Compact -a and -A will not work on DB2 enabled servers • This feature is not enabled for DB2 enabled servers • Remote server Setup from UNIX to W32 cannot be silent • remotesetup <serverhost> -silent <path to Setup Profile> =<path to notes.ini on serverhost> -pb • Use - remotesetup <serverhost> -pl • Spaces in directory names on UNIX causes nsd.sh to fail • spaces in directory names are not supported for Domino 7 on Linux • "System" databases cannot be compacted • events4.nsf and names.nsf system databases cannot be compacted

  23. Technical Considerations (cont’d) • Adding Domino 6 server to 7.0 domain replaces events4.nsf design • Delete EVENTS4.NTF from the Domino 6 server's data directory prior to launching the new Domino 6 server • ND 7 Upgrade removes installed language packs • Do not upgrade Domino Server until new Language Packs are available. • Running NSD manually on Unix can cause Domino to crash • Add the variable AMQ_NO_SIGWAIT_SIGTRAP=1

  24. Other Considerations • Biggest “bang” in ND7 is the TCO • 15% reduction in Direct Costs • 15% reduction in user productivity costs • 8.5% reduction in overall TCO • 22% reduction in TCO when upgrading from R5 • Good time to review overall Domino architecture • Consolidations (Domain and Server) • Platform Changes • User to Server ratio • Use of Notes/Domino 7 New Features • Review how the new features can apply to your environment after you have upgraded all servers and users. Implement only the “low hanging fruit” initially.

  25. What about using DB2? • In ND7.0, introduced as a Limited Availability feature, not General Availability feature • Must qualify for the Limited Availability Program • Must be existing DB2 customers • Available as a Feature Trial for all customers • Not supported by Lotus support • Web-based forum available for sharing information/issues • In general, customers will see the most benefit in applications, not mail servers, and only in sites that use DB2 extensively.

  26. What About Upgrading Applications? • Applications are typically left behind during an upgrade, but just as important. Upgrades should occur after the Notes client has been updated. • Tools available to determine if apps will work in new versions (R4-R5-ND6-ND7) • TeamStudio • Atlantic Decisions • IBM Software Services for Lotus • Tip: Use the 80/20 rule – review your most complex applications first

  27. Don’t Forget Education and Communications! • Education Opportunities: • User impact assessment • Development and implementation of communications strategy • Education assessment and planning • Targeted Education Curriculum • Implementation of training plan • Develop content for website support • Implement post-migration support • Get Executive Involvement • Market the plan

  28. ND 7 Upgrade Resources • Lotus Support Upgrade Central http://www.ibm.com/software/lotus/support/upgradecentral/index.html • Developer Works:Lotushttp://www-130.ibm.com/developerworks/lotus/products/notesdomino/ • Lotus Knowledge Basehttp://www-306.ibm.com/software/lotus/support/domino/support.html • Upcoming book by an ISSL member Upgrading to Notes R7 (by Tim Speed)

More Related