Abstract: Systems and methods for orchestrating synchronizations between different targets in a synchronization community. The order and nature of synchronizations may depend on multiple factors, including the initiator of the synchronization, the data being synchronized, and other characteristics of the synchronization participants and synchronization community.

Abstract: A disaster recovery system and a method therefor, having: a function for receiving write requests from a host computer to write log information indicating the contents of a database process executed for a database buffer on a main site, database data updated on the database buffer and status information indicating the position of log information used for disaster recovery; a function for transferring the received write request for log information to a recovery site by a synchronous remote copy process; and a function for transferring the received write request for database data to the recovery site by an asynchronous remote copy process. While remote copy can be executed at a long distance without data loss, the deterioration of the performance of a database process on a main site can be suppressed.

Abstract: A system for managing changes to identity data is described. A first spoke managing system is described which includes a first database, a first application in communication with the first database, and a first spoke manager in communication with the first application. A first message is generated including a plurality of common data attributes. The first message is sent to a hub managing system. The hub managing system includes a hub manager. The first message including the plurality of common data attributes is received from the first spoke managing system. A plurality of common data attributes are updated. A determination is made if a unique data attribute that uniquely identifies a reference object is being updated. A second message is generated based on the determination. A third message is generated based on the updates of the plurality of common data attributes. The second message and third message are sent.

Abstract: Performing a synchronization operation is disclosed. A first processing thread is used to copy a first file from a first data storage to a second data storage using a first connection. A second processing thread is used to copy a second file from the first data storage to the second data storage using a second connection. The first file is copied substantially concurrently with the copying of the second file. The synchronization operation results in first copied file and a second copied file in the second data storage. A real-time replication operation is performed. The first copied file and the second copied file are updated in an order determined at least in part by an order in which changes were made to the first file and the second file, respectively, as stored in the first data storage.

Abstract: The various disclosed techniques and equipment relate to synchronizing a subscriber's address books located in a portal and in the subscriber's mobile station, determining the subscription status of a directory number of another party with whom the subscriber intends to communicate, and/or for enabling the subscriber to make a referral to another party who might not be a qualified subscriber.

Abstract: A data migration method is provided which can provide a user at a low cost with a function of migrating data from an existing storage when an additional storage is installed. A business application is operated by using a business server and a first storage. When the capacity and performance of data used by a business application become insufficient, a second storage is installed to compensate for insufficiency. In this case, the management server collectively copies data and configuration information of the first storage to the second storage, the data and configuration information are deleted at a later time in accordance with migration command information selected from a GUI screen. It is therefore possible to migrate necessary data and configuration information of the first storage to the second storage, without making a user be conscious of the details of the configuration information of logical devices of a storage.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for synchronizing a server and an on-demand database service. These mechanisms and methods for synchronizing a server and an on-demand database service can enable embodiments to synchronize a larger amount of data. The ability of embodiments to provide such feature can enable more effective synchronization of a user-level sharing entity database with a multi-user on-demand database service.

Abstract: Systems and methods that track changes in a database via a change tracking layer that enables separation of change tracking and change enumeration. Such an arrangement enables multiple change enumeration and sync technologies over a single change tracking layer, while reducing amount of tracking information that are maintained.

Abstract: The present invention comprises a method of data synchronization between multiple devices by, in one embodiment, classifying one device to be a primary device and other devices to be subsidiary devices. Synchronization is performed, in one embodiment, by updating the primary device with data from the subsidiary devices, and then updating each subsidiary device using data from the updated primary device. The exemplary data synchronization according to the present invention can accommodate for absent devices, avoid redundant synchronization operations, accommodate for data truncation or translation and preserve synchronization of relationships. The devices may be any one of computers, handheld devices (e.g. a Palm device), personal digital assistants, music devices, and mobile telephones. The data to be synchronized may include any data, and even applications can be synchronized.

Abstract: Synchronization architectures, methods, systems, and computer readable media are described. One exemplary embodiment includes a first software component which is configured to cause retrieval and storage of structured data for a first data class from a first store of the structured data on a device, such as a first data processing system, and is configured to synchronize structured data for the first data class in the first store with structured data of the first data class in a second store on a host, such as a second data processing system. The first software component is separate from an application software which provides a user interface to allow a user to access and edit the structured data. The first software component synchronizes the structured data through a second software component which interfaces with the host and the device and which controls an order of synchronizing and a plurality of data classes including the first data class.

Abstract: A data synchronizing method between a server and a client is provided. The server and the client manage database changed after a previous synchronization of data shared by them. The database includes a sync anchor field for each data item. When a sync session is initiated upon request of the client, a last anchor is detected from the database stored in the client and a last anchor from the database stored in the server. The last anchor of the client is compared with the last anchor of the server. A client change log and a server change log are generated according to a comparison result based on a database change that occurred after the last anchor of client or server when the last anchor of the client is identical to the last anchor of the server. The databases are updated according to the client change log and the server change log.

Abstract: Transactional database replication techniques are disclosed. The techniques can be realized in many ways, such as in a replicator module that can be instantiated at each site in a distributed system. The techniques support a variety of data storage technologies such as traditional durable transactional databases as well as in-memory data storage systems, and a variety of data types such as relational, flat file, XML, and object-oriented data. Guaranteed levels of distributed transactional data consistency for both reads and writes are enabled for database applications. The techniques also support the ability of applications distributed across a network to perform updates concurrently, and the ability to replicate many standard database systems without needing to modify their intrinsic behavior or needing them to be aware of the replicator, and the ability to tolerate network and process failures without any change to the data consistency guarantees provided to the applications.

Abstract: Various technologies and techniques are disclosed that improve synchronization of data between varying types of devices and/or services. A full participant receives a request from another participant to perform a synchronization operation. The synchronization engine determines whether the device or service is a full, partial, or simple participant. The device or service is a simple participant if it has a data store for synchronized data and no knowledge store. The device or service is a partial participant if it has a data store for synchronized data and a knowledge store, but does not understand the knowledge. The device or service is a full participant type if it has a data store for synchronized data and a knowledge store and understands the knowledge. The synchronization engine performs the synchronization operation with the device or service using a set of logic that is appropriate for the type of device or service.

Abstract: Various embodiments introduce the notion of a replication entity which implements a highly scalable file replication system. In one embodiment, the replication entity resides in the form of a scalable replication service. In at least some embodiments, the replication service provides a “drive in the sky” facility that can be used by individuals, such as subscribers, to synchronize their individual machines, such that their files are automatically replicated to a safe and always-on location. Alternatively or additionally, individuals such as subscribers can also access their files via a web-based interface when they are away from their machines.

Abstract: Disclosed is a data synchronization service for use in a peer-to-peer computing environment. Selected data objects are copied onto selected computing devices. A service running on each device monitors data objects for changes. When a change is detected, the service sends a change notification to the other devices so that they can update their copies of the data object. A user can access a data object from any device, knowing that he will retrieve the latest version of the data object. Instead of incurring the costs of storing a large file on every device, a user “ghosts” the file on some devices. A ghosting device stores only metadata about the file rather than the entire file. The user accesses the file through the ghost: access requests are sent to a device that holds the actual contents, and those contents are presented to the user as if they were stored locally.

Abstract: Data associated with a plurality of transactions in a data replication system including first and second nodes connected via communication media in a topology is replicated. Each node includes a database and a replication engine which performs data replication functions between the first and second nodes. Each transaction is one or more transaction steps or transaction operations. One or more initial transaction steps or operations of a transaction are sent from an input device to a first node. The one or more initial transaction steps or operations of the transaction are sent to the second node via the replication engine at the first node. If a communication failure is detected between the input device and the first node, the input device sends the remaining transaction steps or operations to the second node.

Abstract: A method, apparatus, and article of manufacture for a transformation lineage model. Data stored on a data storage device connected to a computer is navigated. In response to receiving user input, a target object in an information catalog is selected. Then, information about a source from which the target object was derived is provided.

Abstract: Aspects of the invention described herein provide a method and apparatus for the synchronization of metadata across various metadata repositories. According to the invention, upon synchronization of a local metadata repository and at least one remote metadata repository, metadata values are stored in a local collection or mediator database. The mediator database facilitates conflict resolution across metadata repositories. The invention further provides a repository-specific metadata memory to enable the storage of repository-specific metadata histories to further enhance management and synchronization of the metadata.

Abstract: Data processing architecture where submitters can write data and/or metadata changes to a destination through an asynchronous interface. The architecture includes a ticketing system that issues a ticket (a unique identifier) to the submitter in response to receiving a changelist from the submitter. When the changes are successfully completed at the destination, the cached destination data can be re-downloaded to the submitter, and the changes cached in the submitter, discarded. Absent this capability, a user has to manually manage the cached changes and cached data. The architecture can be distributed in that multiple submitters can submit changelists. The destination provides data integrity by managing submissions to assist in ensuring data integrity across multiple submissions. Automatic changelist cleanup is provided on the submitter so that changelists do not impact performance, memory, and storage.

Abstract: One embodiment is a method that reads audit from an audit trail of a source database distributed across multiple storage systems with independent audit trails and then replicates the audit trail to a target database distributed across multiple storage systems with independent audit trails without manual coordination by a database administrator.