Checking Edirectory Health - Novell OPEN ENTERPRISE SERVER 2.0 SP2 - UPGRADING TO OES-PLANNING AND IMPLEMENTATION GUIDE 12-2009 Implementation Manual

User accessibility needs: Which applications and services are needed by which users? Do
users need to read data or modify it? which rights need to flow from the root? How many users
need remote access? Where will remote users access data from?
Application needs: Which offices use the same applications? How many users are there per
application? Are applications installed locally or centrally?
Administrative strategies: Do you intend to manage eDirectory centrally or from many
dispersed locations?
Naming standards for eDirectory objects: What naming standards are in force? Do any of
them need to be changed or updated?
Scalability and interoperability: How important are these on your network? Are you willing
to compromise scalability and/or performance for other worthwhile goals?
Speed and efficiency: How important are these on your network? Are you willing to
compromise speed and efficiency for other worthwhile goals?
Fault tolerance: What steps have you taken to provide fault tolerance? Do additional options
need to be implemented?
Deciding Whether to Move Services
If you decide to redesign your system, you need to determine whether to keep services in their
original tree or move them to a new tree. As part of this process, you probably also want to remove
any objects that are no longer being used.
For File and Print, Design around Your WAN
It is important that the WAN configuration is the first and foremost consideration for designing any
eDirectory tree that caters primarily to file and print, particularly if your organization includes
several remote facilities. In most cases, you should provide a partition for each remote location, even
when it is a single-server site.
For example, if you plan to have five OES 2 SP2 servers in place that are primarily dedicated to
providing eDirectory replica services, all of the Master replicas could be contained on one of these
servers along with multiple replicas of the higher levels of the tree. Each remote server should
include an R/W replica of its local partition. Make sure you have three writable replicas in place to
provide adequate redundancy.
Verify Your Redesign in a Lab First
If you decide to re-engineer your tree, it's a good idea to create the new tree in a lab to make sure
you can work with its structure and that it's actually going to work the way you want before you put
it into production.

3.2.2 Checking eDirectory Health

Problems with eDirectory can derail a rollout very quickly. Make sure there are no significant health
issues before you begin the upgrade. Determine whether the prerequisites have been met for
introducing OES 2 SP2 and eDirectory 8.8 into an existing tree or for transferring eDirectory from
NetWare to OES.
"What to Check For" on page 42
"Health Check Tools To Use" on page 43
Upgrading eDirectory to OES 41