Directory server replication

• US 9,143,559 B2
• Filed: 12/05/2007
• Issued: 09/22/2015
• Est. Priority Date: 12/05/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Raut, Sachin Ramesh
• Primary Examiner(s): Alam, Hosain
• Assistant Examiner(s): HARPER, ELIYAH STONE
• Application Number:
  US11/950,565
• Publication Number:
  US 20090150398A1
• Time in Patent Office: 2,848 Days
• Field of Search: 707/610, 707/644, 707/603, 707/633
• US Class Current: 1/1
• CPC Class Codes: G06F 16/184 implemented as replicated file system
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: H04L 61/4505 using standardised directories; using standardised directory access protocols
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Information regarding requests made to a directory server by clients is collected. The requests including read, compare, search, write, and update requests. It is determined the number of the read, compare and search requests is greater than a threshold and/or whether the number of the write and update requests is greater than the threshold. In response to determining that either or both numbers are greater than the threshold, the following is performed. The process by which the directory server should be replicated is determined based on the information collected. The type of replication as to which the directory server should be replicated is also determined based on the information collected. A new directory server is then replicated from the directory server using the determined process. The new directory server has the determined type of replication.

Claims

1. A method for replicating a directory server comprising:

collecting information regarding requests made to the directory server by clients;

determining a process by which the directory server should be replicated based on the information collected, where the process is determined based on the requests made to the directory server by the clients, as opposed to the requests made just by one of the clients;

determining a type of replication as to which the directory server should be replicated based on the information collected, where the type of replication is determined based on the requests made to the directory server by the clients, as opposed to the requests made just by one of the clients; and

,

replicating a new directory server from the directory server using the process that has been determined, the new directory server having the type of replication that has been determined, such that replicating the new directory server having the type of replication that has been determined and using the process that has been determined results in the new directory server being accessible by the clients, and not just by one of the clients.

2. The method of claim 1, wherein the requests made to the directory server by the clients include read, compare, search, write, and update requests,

the method further comprising determining whether a number of the read, compare and search requests is greater than a threshold and/or whether a number of the write and update requests is greater than the threshold,

such that, in response to determining that the number of the read, compare, and search requests is greater than the threshold and/or that the number of the write and update requests is greater than the threshold,

the process by which the directory server should be replicated and the type of replication as to which the directory server should be replicated are determined, and the new directory server is replicated from the directory server.

3. The method of claim 1, wherein collecting the information regarding the requests made to the directory server by the clients comprises:

collecting information regarding read, compare, search, write and update requests made to the directory server by the clients; and

,

collecting networking information regarding the clients making the requests.

4. The method of claim 3, wherein collecting the information regarding read, compare, search, write and update requests made to the directory server by the clients comprises:

collecting base, scope, filter, and attribute information for read, compare, and search requests made to the directory server by the clients; and

,

collecting base distinguished name (base DN) information for write and update requests made to the directory server by the clients.

5. The method of claim 1, wherein collecting the information regarding the requests made to the directory server by the clients comprises, for each specific request made to the directory server:

where the specific request is not contained in a composite request encompassing all previously made requests to the directory server by the clients, performing a logical OR operation on the composite request with the specific request to update the composite request; and

,

where the specific request is already contained in the composite request, ignoring the specific request.

6. The method of claim 1, wherein determining the process by which the directory server should be replicated comprises:

where a composite request encompassing all previously made requests to the directory server by the clients includes base information encompassing all directory suffixes of the directory server, the composite request includes scope information encompassing sub-levels of all the directory suffixes, the composite request includes filter information encompassing object classes of all the directory suffixes, and the composite request includes attribute information encompassing all attributes of a directory schema of the directory server,

selecting the process by which the directory server should be replicated as a first process in which an entire directory of the directory server is replicated.

7. The method of claim 6, wherein determining the process by which the directory server should be replicated further comprises:

where the composite request includes base information encompassing some but not all of the directory suffixes of the directory server, the composite request includes scope information encompassing the sub-levels of some but not all the directory suffixes, the composite request includes filter information encompassing the object classes of some but not all the directory suffixes, and the composite request includes attribute information encompassing all the attributes of the directory schema,

selecting the process by which the directory server should be replicated as a second process in which just particular suffixes of the entire directory of the directory server are replicated; and

,

where the composite request includes base information encompassing some but not all directory sub-trees of the directory server, the composite request includes scope information encompassing sub-levels of some but not all the directory sub-trees, the composite request includes filter information encompassing object classes of some but not all the directory sub-trees, and the composite request includes attribute information encompassing all the attributes of the directory schema,

selecting the process by which the directory server should be replicated as a third process in which just particular directory sub-trees of the entire directory of the directory server are replicated.

8. The method of claim 7, wherein determining the process by which the directory server should be replicated further comprises:

where the composite request includes base information encompassing some but not all the directory sub-trees, the composite request includes scope information encompassing the sub-levels, base levels, and/or one-levels of some but not all the directory sub-trees, the composite request includes filter information for some but not all the directory sub-trees, and the composite information includes attribute information encompassing all the attributes of the directory schema,

selecting the process by which the directory server should be replicated as a fourth process in which just particular directory sub-trees of the entire directory of the directory server are replicated with filter criteria corresponding to the filter information of the composite request; and

,

where the composite request includes base information encompassing some but not all the directory sub-trees, the composite request includes scope information encompassing the sub-levels, base levels, and/or one-levels of some but not all the directory sub-trees, the composite request includes filter information for some but not all the directory sub-trees, and the composite information includes attribute information for some but not all the attributes of the directory schema,

selecting the process by which the directory server should be replicated as a fifth process in which just particular directory sub-trees of the entire directory of the directory server are replicated with filter criteria corresponding to the filter information of the composite request and with attribute criteria corresponding to the attribute information of the composite request.

9. The method of claim 1, wherein determining the type of replication as to which the directory server should be replicated comprises, where a composite request encompasses all previously made requests to the directory server by the clients, and where the previously made requests include at least read requests, search requests, and compare requests:

where a number of the read requests, search requests, and/or compare requests encompassed by the composite request for any directory suffix or directory sub-tree of the directory server is greater than or equal to a first threshold,

where networking information regarding the clients making the requests indicate that a second threshold has been reached in relation to any sub-net,

selecting the type of replication as a first type of replication in which the new directory server is a replica of the directory server; and

,

where the networking information indicates that the second threshold has not been reached in relation to any sub-net,

selecting the type of replication as a second type of replication in which the new directory server is a forwarder and a replica of the directory server.

10. The method of claim 9, wherein determining the type of replication as to which the directory server should be replicated further comprises, where the composite request encompasses all the previously made requests to the directory server by the clients, and where the previously made requests also include at least update requests and write requests:

where a number of the update requests and/or write requests encompassed by the composite request for any directory suffix or directory sub-tree of the directory server is greater than or equal to a third threshold,

where the networking information regarding the clients making the request indicates that the second threshold has been reached in relation to any sub-net,

selecting the type of replication as a third type of replication in which the new directory server is a master of the directory server; and

,

where the networking information indicates that the second threshold has not been reached in relation to any sub-net,

selecting the type of replication as a fourth type of replication in which the new directory server is a gateway for the directory server.

19. The method of claim 1, wherein the information collected is stored in a composite request comprising:

scope information encompassing sub-levels, base-levels, and/or one-levels of at least some of directory sub-trees of the directory server; and

attribute information encompassing attributes of a directory schema of the directory server.

20. The method of claim 1, wherein the type of replication as to which the directory server should be replicated is determined based on the information collected from a plurality of types comprising:

a first type of replication in which the new directory server is a replica of the directory server;

a second type of replication in which the new directory server is a forwarder and a replica of the directory server;

a third type of replication in which the new directory server is a master of the directory server;

a fourth type of replication in which the new directory server is a gateway for the directory server.

11. A system comprising:

a learning engine to collect information regarding requests made to a directory server by clients;

a determination engine to determine a process by which the directory server should be replicated based on the information collected and to determine a type of replication as to which the directory server should be replicated based on the information collected, where both the process and the type of replication are determined based on the requests made to the directory server by the clients, as opposed to the requests made just by one of the clients; and

,

a replication engine to replicate a new directory server from the directory server using the process that has been determined, the new directory server having the type of replication that has been determined, such that replicating the new directory server having the type of replication that has been determined and using the process that has been determined results in the new directory server being accessible by the clients, and not just by one of the clients.

12. The system of claim 11, wherein the directory server comprises a plug-in to implement the learning engine.

13. The system of claim 11, further comprising a topology router comprising a plug-in to receive information regarding the new directory server replicated.

14. The system of claim 11, wherein the learning engine comprises:

an information gathering component to collect the information regarding the requests made to the directory server by the clients, the requests including read, compare, search, write, and update requests made to the directory server by the clients; and

,

an information processing component to update a composite request encompassing all the requests made to the directory server by the clients.

15. The system of claim 11, wherein the determination engine comprises:

a first component to determine the process by which the directory server should be replicated based on the information collected, the process selected from a plurality of processes comprising;

a first process in which an entire directory of the directory server is replicated;

a second process in which just particular suffixes of the entire directory of the directory server are replicated;

a third process in which just particular directory sub-trees of the entire directory of the directory server are replicated;

a fourth process in which just particular directory sub-trees of the entire directory of the directory server are replicated with filter criteria corresponding to filter information of the composite request;

a fifth process in which just particular directory sub-trees of the entire directory of the directory server are replicated with filter criteria corresponding to the filter information of the composite request and with attribute criteria corresponding to attribute information of the composite request; and

,

a second component to determine the type of replication as to which the directory server should be replicated based on the information collected, the type selected from a plurality of types comprising;

a first type of replication in which the new directory server is a replica of the directory server;

a second type of replication in which the new directory server is a forwarder and a replica of the directory server;

a third type of replication in which the new directory server is a master of the directory server;

a fourth type of replication in which the new directory server is a gateway for the directory server.

16. The system of claim 11, wherein the determination engine is to determine the process by which the directory server should be replicated and is to determine the type of replication as to which the directory server should be replicated upon determining that a number of read, compare, and search requests of the requests made to the directory server is greater than a threshold and/or that a number of write and update requests of the requests made to the directory server is greater than the threshold.

17. A non-transitory computer-readable medium having one or more computer programs stored thereon to perform a method comprising:

collecting information regarding requests made to a directory server by clients, the requests including read, compare, search, write, and update requests;

determining whether a number of the read, compare and search requests is greater than a threshold and/or whether a number of the write and update requests is greater than the threshold;

in response to determining that the number of the read, compare, and search requests is greater than the threshold and/or that the number of the write and update requests is greater than the threshold,

determining a process by which the directory server should be replicated based on the information collected, where the process is determined based on the requests made to the directory server by all the clients, as opposed to the requests made just by one of the clients;

determining a type of replication as to which the directory server should be replicated based on the information collected, where the type of replication is determined based on the requests made to the directory server by the clients, as opposed to the requests made just by one of the clients; and

,

replicating a new directory server from the directory server using the process that has been determined, the new directory server having the type of replication that has been determined, such that replicating the new directory server having the type of replication that has been determined and using the process that has been determined results in the new directory server being accessible by the clients, and not just by one of the clients.

18. The non-transitory computer-readable medium of claim 17, wherein determining the process by which the directory server should be replicated comprises selecting the process from a plurality of processes comprising:

a first process in which an entire directory of the directory server is replicated;

a second process in which just particular suffixes of the entire directory of the directory server are replicated;

a third process in which just particular directory sub-trees of the entire directory of the directory server are replicated;

a fourth process in which just particular directory sub-trees of the entire directory of the directory server are replicated with filter criteria corresponding to filter information of the composite request;

a fifth process in which just particular directory sub-trees of the entire directory of the directory server are replicated with filter criteria corresponding to the filter information of the composite request and with attribute criteria corresponding to attribute information of the composite request; and

,

wherein determining the type of replication as to which the directory server should be replicated comprises selecting the type from a plurality of types comprising;

a first type of replication in which the new directory server is a replica of the directory server;

a second type of replication in which the new directory server is a forwarder and a replica of the directory server;

a third type of replication in which the new directory server is a master of the directory server;

a fourth type of replication in which the new directory server is a gateway for the directory server.