Replication facility

Abstract: A replication facility provides for the replication of files or portions of files in a distributed environment. The replication facility is able to replicate any subtree within a distributed namespace of the distributed environment. The replication facility provides multi-mastered, weakly consistent replication. The replication facility supports both public replication and private replication.

Description: The present invention relates generally to data processing systems and, more particularly, to replication facilities used within distributed systems. Replication facilities have been provided in a number of different types of software products. For instance, replication facilities have been incorporated in database products, network directory service products, and groupware products. Many of the conventional replication facilities are limited in terms of what they can replicate. For instance, many conventional replicators can only replicate one type of logical structure (i.e., a file). Furthermore, the conventional replicators are limited in terms of the quantity of the logical structures that may be replicated at a time. In particular, many conventional replicators can only replicate one file at a time. Software-Practice and Experience, Dec. 1987, UK, vol. 17, no. 12, ISSN 0038-0644, pages 923-940, Purdin T.D.M. et al. 'A file replication facility for Berkeley Unix' discloses a file replication facility for supporting file replication in a network computer. File replication is supported by reproduction sets which are collections of two or more files that the system attempts to keep identical. Similarly, location transparency for a collection of files can be established using a metafile. A reproduction set is created by the mkrep command which has several file arguments. If the file indicated by the first argument exists when the command is executed, its contents are copied to the other named files. Proceedings of the Summer 1993 USENIX Conference, Cincinnati; OH, USA, 21-25 June 1993, 1993 Berkeley, CA, USA, USENIX Assoc, USA, pages 279-290, Fowler G. et al. 'A user-level replicated file system' discloses a user-level replicated file system and describes a replication mechanism. To avoid replicating temporary files, the replication mechanism introduces a new notion, a replicated tree, by which users are able to define one or more sub-trees of a file system that need to be replicated. Files under replicated trees can be replicated to a backup physical file system whenever their context/attributes are changed. The replication mechanism allows users to define one or more sub-trees of a file system as replicated trees. Replicated trees are described as allowing users to avoid replicating the temporary files. It is the object of the present invention to provide a more secure method of replicating files in a distributed system, and a corresponding distributed system. This object is solved by the invention as claimed in the independent claims. The invention is less limited in terms of what they can replicate and in terms of the quantity of the logical structures that may be replicated at time. Preferred embodiments are defined in the dependent claims. A method is provided that may be practiced in a distributed system having a replication facility and a number of computer systems that each include a storage device. In this method, a plurality of files are provided and organized into a tree. A single one of the files is replicated using the replication facility such that a copy of the file is stored in the storage device of a different computer system than the original copy of the file. A subtree of files of multiple levels is also replicated. The subtree is originally stored on the storage device of one of the computer systems. Replication is performed using the replication facility such that a copy of the subtree and its files are stored in the storage device in another of the computer systems. In accordance with another aspect, a first copy of a file is provided in one of the computer systems. A second copy of the file is provided in another of the computer systems. The first copy of the file is reconciled with the second copy of the file using a reconciler facility. The reconciliation ensures that the second copy of the file incorporates any changes made to the first copy of the file. A first copy of a group of files is provided in one of the computer systems, and a second copy of the group of files is provided in another of the computer systems. The reconciler facility is used to reconcile the first copy of the group of files with the second copy of the group of files so that the second copy of the group of files incorporates any changes made to the first copy of the group of files since last reconciled. In accordance with a further aspect, a first copy of a group of files is stored in the storage device of a first of the computer systems. A second copy of the group of files is stored in the storage device of a second of the computer systems. Changes are made to at least one of the files in the first copy of a group of files. The changes are propagated to the second group of files upon the occurrence of an event. Additional changes are made to at least one of the files in the first copy of a group of files, and these changes are also propagated to the second copy of a group of files upon the occurrence of another event. In accordance with yet another aspect, a first copy of a group of files is stored in the storage device of the first computer system. The second copy of the group of files is stored in the storage device of a second computer system. Any changes made to the first copy of the group of files are incrementally sent to the second computer system so that the changes may be made to the second copy of the group of files. In accordance with an additional aspect, a first set of files that are stored in one of the storage devices is specified to be replicated. A filter is specified for determining what files in the first set of files are to be replicated. The files specified by the filter are replicated using the replication facility to produce a second set of files. In accordance with a still further aspect, files having names are stored in the storage devices of the computer systems of the distributed system. A distributed namespace is provided. The distributed namespace comprises a logical organization of the names of the stored files. Selected portions of a group of files in the namespace are replicated to create new files holding the selected portions of the files. In accordance with a further aspect, a first copy of a set of files of a given class are stored in a first computer system. A second copy of the set of files are stored in a second computer system. The first copy of the set of files is reconciled with the second copy of the set of files using a class-specific reconciler that only reconciles files of the given class. The files may be stored as persistent objects, which are organized into classes. Objects and classes will be discussed below. In accordance with another aspect , an application program is run on one of the computer systems of a distributed system. A request is made within the application program to a private replication mechanism to replicate a set of files. Each of the files maintains a list of processes that are permitted to access the file. The set of files is replicated using the private replication mechanism to produce a new set of files without replicating the list of processes that are permitted to access the file. In accordance with a further aspect, a first copy of a group of files is provided in a first computer system and a second copy of the group of files is provided in a second computer system. Changes are made to the first copy of a group of files. An agent is provided for the first copy of group of files. Each agent has access rights to access and read the files in the first of the group of files. A reconciler is provided at the second computer system for reconciling the second copy of the group of files with the first copy of the group of files. A proxy is granted from the agent of the first copy of the group of files to the reconciler. The proxy grants the reconciler limited authority to access and read the files in the first copy of the group of files. The reconciler then reconciles the second copy of the group of files with the first copy of the group of files using the reconciler so that changes that were made to the first copy of group of files is also made to the second copy of group of files. In accordance with a final aspect, a method is practiced in a distributed system. In this method, heterogeneous file systems are provided in the distributed system. A storage manager is provided for each file system to manage access to the files held therein. In response to a request to reconcile a first set of files with a second set of files, access is granted to the first set of files by the storage manager for the file system that holds the first set of files and access is granted to the second set of files by the storage manager for the file system that holds the second set of files. The first object set is reconciled with the second object set under the control of the storage managers of the respective file systems that hold the first set of files and the second set of files. Brief Description of the Drawings Figure 1A is a block diagram of a distributed system suitable for practicing a preferred embodiment of the present invention. Figure 1B is a diagram of a distributed namespace for a distributed system in accordance with the preferred embodiment of the present invention. Figure 2 is a block diagram of a change log used in the preferred embodiment of the present invention. Figure 3 is a block diagram of a replication information block (RIB) used in the preferred embodiment of the present invention. Figure 4 is a block diagram illustrating the functional components of the replication facility used in the preferred embodiment of the present invention. Figure 5 is a diagram illustrating the interaction of elements that play a role in public replication in the preferred embodiment of the present invention. Figure 6 is a flowchart of the steps performed in replication in the preferred embodiment of the present invention. Figure 7 is a flowchart illustrating the steps performed to provide security during replication in the preferred embodiment of the present invention. Detailed Description of the Invention A preferred embodiment of the present invention provides a replication facility for use in a distributed environment. The replication facility supports weakly consistent replication of any subtree of persistent objects in the distributed namespace of the system. The replication facility may replicate single objects or may replicate logical structures that include multiple objects. The replication facility reconciles local copies of objects with remote copies of objects. Reconciliation occurs on a pair-wise basis such that each object in a local set of objects is reconciled with its corresponding object in the remote set of local objects. The reconciliation may occur over heterogeneous file systems. Figure 1A depicts a distributed system 10 that is suitable for practicing the preferred embodiment of the present invention. The distributed system 10 includes an interconnection mechanism 12, such as a local area network (LAN), wide area network (WAN), or other interconnection mechanism, that interconnects a number of different data processing resources. The data processing resources include workstations 14, 16, 18 and 20, printers 22 and 24, and secondary storage devices 26 and 28. Each of the workstations 14, 16, 18 and 20 includes a respective memory 30, 32, 34 and 36. Each of the memories 30, 32, 34 and 36 holds a copy of a distributed operating system 38. Each workstation 14, 16, 18 and 20 may implement a separate file system. Those skilled in the art will appreciate that the present invention may be practiced on configurations other than the configuration shown in Figure 1A. The distributed system 10 shown in Figure 1A is intended to be merely illustrative and not limiting of the present invention. For instance, the interconnection mechanism 12 may interconnect a number of networks together that are running separate network operating systems. The preferred embodiment of the present invention allows users and system administrators to replicate persistent "objects." An object, in this context, is a logical structure that holds at least one data field. Groups of objects with similar properties and common semantics are organized into object classes. A number of different object classes may be defined for the distributed system 10. Although the preferred embodiment of the present invention employs objects, those skilled in the art will appreciate that the present invention is not limited to an object-oriented environment; rather, the present invention may also be practiced in non-object-oriented environments. The present invention is not limited to replication of objects; rather, it is more generalized to support the replication of logical structures, such as files or file directories. The operating system 38 includes a file system for storing the objects that are used in the preferred embodiment of the present invention. The objects are organized into a distributed namespace 19 (Figure 1B). The distributed namespace 19 is a logical tree-like structure formed from the object names 21 stored in the file system of the operating system 38. The distributed namespace 19 illustrates the hierarchy among the named objects of the system 10 (Figure 1A). The replication facility of the preferred embodiment of the present invention provides not only for the duplication of objects so that objects may be distributed across the distributed system, but also provides for reconciliation of multiple copies of objects (i.e., multimaster replication). Reconciliation refers to reconciling an object with a changed object so that the object reflects the changes made to the changed object. For instance, suppose that a remote copy of an object has been changed and a local copy of the object has not yet been updated to reflect the changes. Each object not only has contents but also has a name and location within the distributed file system. Reconciliation involves reconciling the two copies of the object such that the local copy of the object is changed in a like fashion to how the remote copy of the object was changed. The term "replication," as used herein, refers to not only duplicating objects so that multiple copies of the objects are distributed across the distributed system 10, but also refers to reconciliation of the copies of the objects. Before discussing the preferred embodiment of the present invention in more detail below, it is helpful to introduce a few key concepts that will be referenced below. An "object set" is a collection of objects that are grouped together for replication. An object set may include a single object or a sub-tree of objects. The object set is specified by the user or administrator who requests replication. A "replica set," in contrast, is a collection of systems which each own a local copy of an object set, and a "replica" is a member of a replica set. To insulate the replication facility from the underlying physical storage system (e.g., the type of file system employed to store objects) and to provide extensibility, the preferred embodiment of the present invention adopts the abstraction of a replicated object store (ReplStore). The ReplStore abstraction allows the replication facility to be applied across heterogeneous file systems. The ReplStore presents a group of interfaces that must be supported for an underlying physical storage system to support replication facilities. In particular, only those objects that reside in object stores that support the ReplStore interfaces can be replicated. An interface is a named group of logically related functions. The interface specifies signatures (such as parameters) for the group of related functions provided by an interface. The interface does not provide code for implementing the functions; rather, the code for implementing the function is provided by objects or by other implementations. Objects that provide the code for an instance of an interface are said to "support" the interface. The code provided by an object that supports an interface must comply with the signature specified within the interface. Thus, in the example described above, the object store that stores the objects in the object set must support the ReplStore interfaces in order for the object set to be replicated. Implementations of the ReplStore interfaces are provided for each of the file systems within the distributed system 10 in order to support replication over each of the file systems. Each ReplStore provides a mechanism for identifying replicated objects on the local volume. This mechanism is the replicated object ID (ROBID). The ROBID is an abstraction that encapsulates the identity as well as other information about an object that is being replicated. The ReplStore supports routines for serializing and deserializing ROBIDs. The ROBID of an object provides a mechanism for performing numerous operations. For instance, an object can be retrieved from storage using information contained in the ROBID. Further, a component name of an object can be derived from its ROBID. Each ReplStore maintains a replicated storage change log 40 (Figure 2). The change log 40 includes a number of change items 42 that specify changes that have been made to objects in the object set. Each change item 42 includes a type field 44, a serialized ROBID field 46 for the object that is changed, a time field 48 indicating the time that the change occurred (local time) and a replication information block (RIB) field 50 holding a RIB that is associated with the change. In the embodiment described herein, there are five types of changes that may be specified within the type field 44. These changes are deletion, creation, modification, renaming, and moving. A deletion occurs when an object is deleted. Creation occurs when the object is created. A modification occurs when the contents of the object are modified in some way. A renaming occurs when the component name of the object is modified and moving occurs when the object is moved under a new parent in the distributed namespace of the system. A cursor 49 is maintained within the change log 40 that acts as an index into the list of change items 42. The cursor 49 acts as a marker in the list of change items 42. In addition, a change log may include multiple cursors. The cursor 49 may take the form of a tine stamp. The cursor 49 may, for example, identify the beginning of changes that have occurred after a point in time. Every object in an object set that is being replicated is stamped with an RIB 51 (Figure 3). The RIB 51 has three fields: an originator field 57, a change identifier field 55, and a propagator field 57. The originator field 53 specifies where the last change to the object occurred. The change identifier field 55, in contrast, identifies the last change to the object relative to the originator identified within the originator field 53. Lastly, the propagator field 57 specifies the identity of the party who sent the change to the local site. When an object is changed locally, the RIB 51 associated with the object is modified to reflect the local site as the originator and the propagator. The change identifier is stamped appropriately. Replication is useful for the distributed system 10 in that it provides load balancing and availability. Replication provides load balancing by having more than one copy of an object stored across the distributed system 10 to limit the load on any one copy of the object. Replication enhances availability by allowing multiple copies of important objects to be distributed across the system 10. The enhanced availability increases the fault resilience of the system. Specifically, by having copies of important objects distributed across the system 10, users are less affected by failures within the system that prevent or limit access to objects. The enhanced availability also enhances the performance of the system. The preferred embodiment of the present invention is embodied in a replication facility 54 (Figure 4) that is part of the operating system 38. Nevertheless, those skilled in the art will appreciate that the replication facility of the present invention may also be implemented in other environments, including graphical user interfaces. As shown in Figure 4, the replication facility 54 includes three primary functional components: a copying component 56, a reconciler component 58 and a control component 60. The replication facility 54 uses the copying component 56 for duplication. In addition, the replication facility 54 reconciles copies of object sets using the reconciler component 58 to ensure that they are consistent with each other. This reconciliation insures a consistent view of the objects across the distributed system 10. One level of control exerted by the control component 56 concerns how replication is invoked. Replication may be invoked manually or automatically. Manual invocation requires that an explicit request to replicate be made by a user or other party. The user or other party must specify the object set and the destination for replication. The destinations are not specified for each replication cycle; rather a replica connection is specified initially. The replica connection identifies the two replicas and the object set that are to be involved in replication. In contrast, automatic invocation occurs when replication is triggered by certain events 67 (see Figure 5) or by the passage of a certain amount of time (which may be construed as a type of event). Replication may be prescheduled to occur at fixed time intervals. Another aspect of control exerted by the control mechanism concerns who may invoke replication. Replication may be invoked by an appropriately privileged party. The preferred embodiment of the present invention provides two types of replication: public replication and private replication. Public replication refers to a process that may be performed only by appropriately privileged parties to produce a "public" copy of an object set. In public replication, each of the copies of the object set that are produced cooperates with the other copies to maintain consistency. The nodes in the namespace that store the public copies, in aggregate, form a public replica set, and the members of the set keep state information to maintain consistency among the copies. Access restrictions on the objects are preserved. Changes that occur in a public copy of an object set are reconciled with other public copies. Private replication refers to a process for producing private copies of an object set. A private copy may be created by any party, including a non-administrator. Not all members of the replicated sets keep state information to maintain consistency among copies. Private replication will be discussed in more detail below. A number of elements play a role in the replication process in the preferred embodiment of the present invention. Figure 5 is a diagram illustrating the elements that may play a major role in the public replication process. Object replication agents (ORAs) 62 and 64 are replicator objects that act as agents on behalf of nodes in which object sets are stored to provide automatic support for replication. Each machine in the distributed system has its own ORA. The ORAs 62 and 64 may act as remote procedure call (RPC) servers that service requests made on behalf of remote clients or may alternatively be other types of reliable communication mechanisms that serve a similar role. A separate ORA 64 is provided for a local object and another ORA 64 is provided for the corresponding remote object in the public replication process. Local ORA 62 is responsible for loading a ReplStore DLL 66 and a ReplStore Manager DLL 65. The ReplStore Manager 65 is responsible for regulating access to the ReplStore 66. Clients call the ReplStore Manager 65 to load the appropriate ReplStore 66 for a given physical storage system. The ORAs 62 and 64 have a level of privilege that allows them to read and write all objects that are being replicated from a local object store. The ORAs 62 and 64 are responsible for replying to requests to exchange changes with other ORAs which maintain public replicas. A reconciler 68 also plays a role in the public replication process. It acts as a counterpart to the local ORA 62 to reconcile the local object set with the remote object corresponding. The reconciler 68 is called by the local ORA 62 and is responsible for opening objects that are to be reconciled. Two types of reconciler objects may be called by the reconciler 68. Specifically, a class-specific reconciler 70 may be called or a default (i.e., class-independent) reconciler 72 may be called. The class-specific reconciler 70 reconciles objects that have class specific requirements on replication. The class specific reconciler 70 is applied to only a class of objects. The class-independent reconciler 72 reconciles objects regardless of their class. Multiple class-independent reconcilers may be available in the system 10. For instance, each object set may have its own class-independent reconciler. Every replica set may be associated with its own class independent reconciler which is invoked whenever a class-specific reconciler is unavailable. Lastly, as mentioned above, events 67 may play a role in triggering replication. Figure 6 is a flowchart of the steps performed for replication in the preferred embodiment of the present invention. Initially, access is gained to a change log 40 (Figure 2) for a remote object set (step 74 in Figure 6). In particular, when a local object set is to be reconciled with a remote object set, the local ORA 62 (Figure 5) contacts the remote ORA 64 via a remote procedure call mechanism. The local ORA 62 contacts the remote ORA 64 to gain access to the change log 40. A cursor 49 (Figure 2) is then created in the change log (step 76 in Figure 6). Specifically, the local ORA 62 stores a time stamp indicating the time of the last reconciliation between the object sets and then passes this time stamp to the remote ORA 64 to be used as a cursor 49. The remote ORA 64 then passes this time stamp as a cursor into the remote change log 40. The cursor identifies items in the change log that have time stamps after the last reconciliation and, thus, are of interest for this replication cycle. A list of change items are then obtained from the remote change log utilizing the cursor, to identify the change items that are for changes that have occurred after the last reconciliation. The remote ORA 64 screens the RIBs 51 of each of the change items 42 to insure that the remote ORA does not pass back to the local ORA 62 changes that originated at the local ORA (i.e., the remote ORA examines the originator field 53 of the RIBs) and examines the RIBs to insure that change items for changes that were propagated from the local ORA (i.e., the remote ORA examines the propagator field 57 of the RIBs) are not sent. The resulting change items are passed back to the local ORA 62 where they are stored persistently. The local ORA 62 then uses the reconciler 68 to perform namespace reconciliation (step 80) and content reconciliation (step 82) on the objects identified by the ROBIDs in the change items. In particular, the reconciler 56 reconciles each object that has changed in the remote object set with corresponding objects of the local object set. Any changes that have been made to the remote object are made to the corresponding local object. Whether the class-specific reconciler 70 or the class-independent reconciler 72 is used depends upon the source (i.e., remote copy of an object). A class specific reconciler 70 is used only if the remote copy of the object requires such a reconciler. Namespace reconciliation is performed (see step 80 in Figure 6) for any change recorded in a change item that is not strictly a content modification or that is not associated with a system property. Such changes include creations, deletions, moves, and renames. Namespace reconciliation occurs by comparing information obtainable by ROBIDs of local objects relative to information stored for corresponding remote objects. Many different ways for resolving name resolution conflicts may be used within the present invention. The preferred embodiment of the present invention, however, adopts rules. A first rule used by the preferred embodiment of the present invention to resolve namespace conflicts is to select a last modification over a previous modification. When an object is moved/renamed at one site to have a first name, and the same object is moved or renamed to another site to have a different name, the last occurring change is chosen so that the object assumes the name associated with the last change. A second rule is used to resolve namespace collisions. A namespace collision occurs when two different objects are created, moved, or renamed to have the same name. The second rule specifies that whichever object was created, moved, or renamed first is the name that is selected for the object at the local site. Content reconciliation (see step 82 in Figure 6) involves reconciling contents of a local object with a remote object so that the local object includes the modifications made to the remote object. By examining the changes in the change log, the local objects may be changed to have the same contents as the remote objects. During replication, changes are propagated from one replica to another. Replication is "one way" in that the changes made to an initial copy of an object set are made to a second copy of the object set. There is no immediate reciprocal action to copy the changes made to the second copy of the object set to the first copy of the object set. Nevertheless, such propagation to the first copy of the object set may be performed. Given this one way nature of replication, each replica monitors how up to date a local copy of an object set is for a replica, cursors are maintained into partner change logs. At the completion of each exchange during reconciliation, the two replicas exchange cursor information. Public replication poses a number of security issues. In general, reconcilers must be able to update objects in order to perform replication. The class-independent reconciler is a trusted system process, and, thus, does not pose a security risk. Class-specific reconcilers, however, are not trusted system processes, and thus pose a security threat. To help alleviate this security dilemma, the preferred embodiment of the present invention utilizes "proxies". A proxy is a delegation ticket that allows worker processes or remote processes that perform well-defined operations without having extraordinary privileges. The proxy packages credentials of the granting party and lends them to the parties seeking access to remote objects. The party seeking access may then step in the shoes of the granting party and access the necessary objects. These credentials may be encrypted. Figure 7 is a flowchart of the steps performed to utilize a proxy in the preferred embodiment of the present invention. During the replication process, the remote ORA 64 (Figure 5) gives a local reconciler 68 a proxy (step 84 in Figure 7). As mentioned above, this proxy includes the appropriate credentials and access rights that are to be granted by the remote ORA to the local reconciler. The reconciler 68 then sends the credentials to the remote site (step 86 in Figure 7). In other words, the reconciler 68 presents the proxy to the remote site. The remote site then validates the credentials, and if the credentials are valid, grants limited access to the objects within the remote copy of the object set in question (step 88). The reconciler 68 then gains access to the remote objects in the object set (step 80). The local reconciler's range of access, however, is limited to only that which is necessary to perform proper reconciliation. It should be appreciated that the present invention is not limited to exclusively using proxies. Any technique that grants secure access, such as making each ORA a member of a common access group that grants access rights, is permissible. Most of the above discussion has focused on public replication. Private replication is similar to public replication but includes a number of differences. In private replication, the source of changes does not maintain a record of what objects were duplicated or changed. There is no state information maintained at the source. The source is not responsible for advising that changes have occurred. Accordingly, the resources that are required for public replication are not required. These characteristics make private replication especially appropriate for instances where manual control of replication is desired, or instances wherein the cost of maintaining a public copy of an object set is not warranted. While the present invention has been described with reference to a preferred embodiment thereof, those skilled in the art will appreciate that the various changes in form and detail may be made without departing from the scope of the present invention as defined in the appended claims. For example, the present invention need not be implemented in an object-oriented environment and need not be practiced solely in a distributed system configuration like that shown in Figure 1A. Furthermore, communication mechanisms other than RPC mechanisms may be used for remote interactions, and security mechanisms other than proxies may be employed.

Claims: Method of replicating files in a distributed system (10), the system having a replication facility (38, 54) and a number of computer systems (14-20) that each include a storage device (32, 66) wherein each storage device contains a plurality of files organized into a tree (19) of files, the files to be replicated being stored in the storage device of a first of the computer systems using the replication facility so that a copy of the file is stored in the storage device of a second of the computer systems, the method comprising the steps of: replicating a single file that is stored in the storage device of the first computer system into the storage device of the second computer system using the replication facility; and replicating a sub-tree of files of multiple levels, from the tree of files, that is stored in the storage device of the first computer system using the replication facility; providing an agent (62, 64) for the first copy of the sub-tree of files, wherein each agent has access rights to access and read the files in the first copy of the sub-tree of files; providing a reconciler (68) at the second computer system for reconciling the second copy of the sub-tree of files with the first copy of the sub-tree of files; granting (84) a proxy to the reconciler from the agent of the first copy of the sub-tree of files, said proxy granting the reconciler limited authority to access and read the files in the first copy of the sub-tree of files; and reconciling the second copy of the sub-tree of files with the first copy of the sub-tree of files using the reconciler. The method of claim 1, further comprising the step of replicating the single file that is stored in the storage device of the first computer system into the storage device of a third computer system using the replication facility. The method of claim 1, further comprising the step of replicating the sub-tree that is stored in the storage device of the first computer system into the storage device of a third computer system using the replication facility. The method of claim 3, wherein the sub-tree being replicated includes at least three levels of files. The method of one of claims 1 to 4, further comprising the steps of: reconciling the first copy of the single file which is stored in the storage device of the first computer system with the second copy of the single file which is stored in the storage device of the second computer system using the reconciler facility by incorporating any changes made to the first copy of the single file since last reconciled into the second copy of the single file; and reconciling the first copy of the sub-tree of files which is stored in the storage device of the first computer system with the second copy of the sub-tree of files which is stored in the storage device of the second computer system using the reconciler facility by incorporating any changes made to the first copy of the sub-tree of files since last reconciled into the second copy of the sub-tree of files. The method of claim 6 wherein the step of reconciling the first copy of the subtree of files with the second copy of the sub-tree of files further comprises the step of reconciling on a pair by pair basis each file in the first copy of the subtree of files with a corresponding file in the second copy of the sub-tree of files. The method of one of claims 1 to 6, further comprising the steps of: making changes to at least one of the files in the first copy of the sub-tree of files which is stored in the storage device of the first computer system; propagating the changes to the second copy of the sub-tree of files which are stored in the storage device of the second computer system upon the occurrence of an event; making additional changes to at least one of the files in the first copy of the sub-tree of files; and propagating the additional changes to the second copy of the sub-tree of files upon the occurrence of another event. The method of claim 7 wherein the event is the elapsing of a predetermined time period. The method of claim 8 where the other event is also the elapsing of a predetermined time period. The method of claim 7 wherein the event is a request by the second computer system to receive the changes. The method of claim 10 wherein the other event is a request by the second computer system to receive the additional change. The method of one of claims 7 to 11, further comprising the step of reconciling the second copy of the sub-tree of files with the first copy of the sub-tree of flies by incorporating the changes made to the first copy of the sub-tree of files into the second copy of the sub-tree of files. The method of claim 12, further comprising the step of reconciling the second copy of the sub-tree of files with the first copy of the sub-tree of files by incorporating the additional changes made to the first copy of the sub-tree of files with the second copy of the sub-tree of files. The method of one of claims 1 to 13, wherein each of the plurality of files has an associated name, the method further comprising the steps of: providing a distributed namespace (19) comprising a logical organization of the names of the first copy and second copy of the sub-tree of files; and replicating selected portions of the first copy of the sub-tree of files stored in the storage devices of the first computer system and whose names form a part of the distributed namespace using the replication facility to create new files holding the selected portions of the first copy. The method of claim 14, further comprising the step of: distributing the new files across at least a portion of the computer systems of the distributed system. The method of one of claims 1 to 15, wherein the files of the first and second sub-trees of files are of a given class, and wherein the step of replicating further comprising the step of: reconciling the first copy of the sub-tree of files which are stored in the storage device of the first computer system with the second copy of the sub-tree of files which are stored in the storage device of the second computer system using a class-specific reconciler (70), said class-specific reconciler being a reconciler that only reconciles files of the given class. The method of claim 16, further comprising the steps of making changes to the first copy of the sub-tree of files; reconciling the first copy of the sub-tree of files with the second copy of the sub-tree of files using a class-independent reconciler (72), said class-independent reconciler being a reconciler that reconciles files regardless of class. The method of one of claims 1 to 17, further comprising the steps of: within an application program, making a request to a private replication mechanism to replicate a set of files, each of the files maintaining a list of processes that are permitted to access the file; and replicating the set of files using the private replication mechanism to produce a new set of files without replicating, for each file, the list of processes that are permitted to access the file. The method of one of claims 1 to 18, further comprising the steps of: providing a collection of files at the first computer system; in response to a request to replicate the collection of files to the second computer system, determining whether all or none of the files in the collection should be replicated; where it is determined that all of the files in the collection should be replicated, replicating all of the files in the collection so that a replica of the collection is provided at the second computer system; and where it is determined that none of the files in the collection should be replicated, replicating none of the files in the collection. The method of one of claims 1 to 19, further comprising the steps of: providing heterogeneous file systems in the distributed system; providing a storage manager (65) for each file system to manage access to files in the file system; in response to a request to reconcile a first set of files with a second set of files, granting access to the first set of files by the storage manager for the file system that holds the first set of files and granting access to the second set of files by the storage manager for the file system that holds the second set of files; and reconciling the first set of files with the second set of files under control of the storage managers of the respective file systems holding the first set of files and the second set of files. The method of claim 20 wherein each copy of a file stored in the file systems is provided a storage-specific identifier by the storage manager. The method of claim 20 or 21 wherein each storage manager reports changes to the files in its file system. The method of claim 22 wherein the changes include deletions of files. The method of claim 22 or 23 wherein the changes include renaming of files. The method of one of claims 22 to 23 wherein the changes include moving of files in the distributed system. The method of one of claims 22 to 25 wherein the changes are reported to a change log and wherein the step of reconciling is performed using the change log. The method of one of claims 20 to 26 wherein each copy of a file is assigned to a unique identifier and wherein the step of reconciling includes comparing identifiers to determine which files are to be reconciled. A distributed system comprising a plurality of computer systems, adapted to perform the method of claims 1 to 27.

Inventors: COOK PETER J, MILLER ARNOLD S, NEEMAN YUVAL, RAMAN BALAN S, COOK, PETER J., MILLER, ARNOLD S., NEEMAN, YUVAL, RAMAN, BALAN S.
Applicants: MICROSOFT CORP, MICROSOFT CORPORATION
Application year: 1995
Main classification: G06F17
IPC codes: G06F17, G06F12