Is there anything I should be aware of with regard to having a single server be responsible for all replicas?
Articles and Tips: qna
01 Jan 1999
Q.
Dear Ab-end: Is there anything I should be aware of with regard to having a single server be responsible for all replicas? I'm thinking performance issues would be a concern, as would management issues, and maybe configuration issues. What do you think?
—Single in Saskatchewan
A.
Dear Single: Here are the advantages of having one server be responsible for all replicas: it certainly makes backing up NDS easier, with no WAN traffic to locate objects in other replicas. Also, tree walking on the central server is faster on external or subordinate references.
Now for the disadvantages: The single server will have to communicate with all servers in the tree holding any type of replica. This server will have to receive all updates made in the tree (such as object creations, deletions, modifications, login time-stamps). If you ever need to run DSRepair on the server holding all these replicas, you're looking at several hours of quality time when you could be playing Doom.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.