If a server holding the Master Read/Write replica of a partition is EBA-enabled, the partition is considered EBA–enabled. eDirectory does not allow any operation that makes a partition non–EBA enabled. On an EBA-enabled server, eDirectory imposes the following restrictions on the partition and replica operations:
If the server hosting EBA CA holds the master replica of the tree root partition, eDirectory does not allow you to change its replica type.
If EBA CA is hosted on a server that holds the Read/Write replica of the tree root partition, ensure that you do not change the replica type to anything other than the master. Changing the replica type to Read-Only/Filtered Read-Only might break the EBA functionality in the entire tree. eDirectory enforces this restriction if the eDirectory server holding the master replica of the tree root partition is EBA-enabled.
NOTE:In a mixed environment where you have older and eDirectory 9.2 servers, you might be successful in changing the replica types; however, doing this can break the EBA functionality.
If the master replica of a partition is present on an EBA-enabled server, the following operations will fail:
Transferring the role of master to a non EBA-enabled server.
Transferring the role of master to any other server, if the server is acting as EBA CA.
Do not merge two partitions when the parent partition is not EBA–enabled and the child partition is EBA–enabled. Doing this might break the EBA functionality.
When eDirectory is configured on a server in EBA-enabled mode, this setting is saved in the n4u.server.eba_enabled parameter in the nds.conf file. When eDirectory is deconfigured on this server and the server configured again, EBA is turned on by default. To configure the server in a non-EBA mode, remove this parameter from the nds.conf file before configuring eDirectory on the server.