Maintaining Novell eDirectory 555novdocx (en) 11 July 200818.4.3 Deploying ARCARC is usually deployed on a server-to-server basis. Those servers that are ARC - enabled can knowthe new costing information.You should patch all the servers to 8.7.3.9 ftf3 and eDirectory 8.8 servers to 8.8.2 version and thenenable ARC on each server in the environment.Deployment ConsiderationsIt is not useful to enable ARC on all servers. Figure 18-4 shows a situation that could impact theefficiency of LDAP servers. In the figure, S4 holds a copy of the green partition, but not of the bluepartition. Any chaining LDAP request that requires information from the blue partition needs towalk to the S1, S2, or S3 servers to be fulfilled. This works in most cases, and ARC is designed forjust such situations.Figure 18-4 ARC Deployment ConsiderationsHowever, performing specific LDAP operations could be difficult. Although it is possible to add auser, for example, Bob.Blue.Novell, the operation might fail when you try to immediately return tomodify Bob. The figure shows Bob added on S2, but modifying Bob on S3 has failed because S3 hasnot yet synchronized with S2, so S3 has not yet received Bob. ARC has the capability to direct youto a different server, because ARC is more dynamic than the original costing method.This configuration works well in scenarios where the server costs don't vary much and they don'thave problems synchronizing. Disabling ARC on S4 resolves this issue.
