Abstract: A fault-tolerant node for synchronous heterogeneous database replication and a method for performing a synchronous heterogenous database replication at such a node are provided. A processor executes a computer program to generate a series of database transactions to be carried out at the fault-tolerant node. The fault-tolerant node comprises at least two relational database management systems, each of which are different relational database management system products, each implementing snapshot isolation between concurrent transactions. Each system comprises a database and a database management component. For each database transaction, operation instructions are provided concurrently to each of the systems to carry out operations on their respective databases and to provide respective responses. The responses generated by the systems either comprise an operation result or an exception.

Abstract: In-band commands may be associated with a particular consistency interval and may indicate requested actions to be performed for that consistency interval. An application may desire to perform actions, such as additional backup, snapshots, etc. on stored data, when that data is in a consistent state from the application's point of view. In order to ensure that the data is in a consistent state, a consistency interval may be created on demand. A node may request a consistency interval by sending a consistency request message to a consistency interval coordinator, which in turn, establishes the consistency interval with all nodes in the distributed environment. After sending all write requests for the consistency interval, the node may then send the command message. Command messages may be stored in consistency logs along with write requests and a replication target, or other device, may read both the write requests and the command message.

Abstract: Methods and systems are disclosed that relate to single instance storage of asset parts utilizing a back reference count associated with each asset part. Entries in a journal associated with the asset parts reflect the intention to increment or decrement an asset part's back reference count. The journal may be used to maintain an accurate and reliable reference count for asset parts replicated across multiple disk drives in a distributed storage system, where the replication is structured to reduce the risk of data loss in the event of a disk drive failure. The journal entries may comprise generation numbers used to maintain a back reference count associated with an asset part and to verify a back reference count associated with an asset part.

Abstract: Providing synchronization to a local system. Embodiments may include downloading a batch of changes in a heterogeneous batch. The batch of changes is correlated to an anchor affiliated with a synchronization service. The anchor is a reference point indicating time or relative order. The batch of changes and the anchor are serialized to a non-volatile storage medium as a heterogeneous set. After serializing the batch of changes to a non-volatile storage medium as a heterogeneous set, entities in the batch of changes are parsed out into entities in in-memory representations. Similarly, embodiments may receive user input modifying a plurality of data entities, store on a non-volatile storage medium a serialized heterogeneous representation of the modified data entities, and upload the serialized heterogeneous representation to a synchronization service.

Abstract: Described are techniques for configuring resources of a data storage system. A definition for each of one or more tiers is provided. Each of the tiers corresponds to a different class of consumer of data storage system resources and has a different corresponding definition including a set of one or more clauses and a priority of each clause in said set relative to other clauses in said set. Each of the clauses in the set is one of a plurality of predefined types of clauses. One or more data storage consumers are associated with each tier. A first set of data storage system resources is associated with a first of said one or more tiers in accordance with a corresponding first definition for said first tier. The first set is used when processing storage provisioning requests and I/O requests for data storage consumers associated with the first tier.

Abstract: A system and method for transferring data between different types of systems, and in particular uses log-based replication to transfer data between, e.g. a MySQL database or system, and another type of database or system. In accordance with an embodiment, the system can be used to perform a one-time or initial copy of the MySQL data from a source database system to a target database system, and/or to replicate the on-going transactions captured from a MySQL database's binary log into one or additional non-MySQL database(s) on a continuous basis, such that the two systems are synchronized for transactions of interest. In accordance with an embodiment, full or partial data changes can be extracted from the MySQL binary log, optionally transformed, skipped or augmented, output or written to a file (which in accordance with an embodiment can be implemented as a trail file, or an Oracle GoldenGate trail file), and then applied at any of one or more target systems (e.g.

Abstract: Systems and methods for replicating data communicated over a network. According to one embodiment, among several embodiment, a data replication system includes a first interface table and a first application associated with a first computing system. The first application is configured to transfer data into the first interface table. The data replication system further includes a first replication module, which is also associated with the first computing system. The first replication module is configured to replicate data from the first interface table into a second interface table associated with a second computing system via a network. The data replication system also includes a second application and a second replication module associated with the second computing system. The second application is configured to transfer data into the second interface table. The second replication module is configured to replicate data from the second interface table into the first interface table via the network.

Abstract: A data processing apparatus, comprising a metadata store storing information about files that are stored in a distributed data storage system, and comprising a class database; one or more processing units; logic configured for receiving and storing in the class database a definition of a class of data storage servers comprising one or more subclasses each comprising one or more server selection criteria; associating the class with one or more directories of the data storage system; in response to a data client storing a data file in a directory, binding the class to the data file, determining and storing a set of identifiers of one or more data storage servers in the system that match the server selection criteria, and providing the set of identifiers to the data client.

Abstract: Systems and methods for synchronizing data between endpoints, including the modification of data on an endpoint without necessarily modifying data that is communicated between endpoints are disclosed. In such systems and methods the representation of data on an endpoint may be modified so that constraints on that particular endpoint are enforced, without requiring a similar or the same modification to the data when it is synchronized to other endpoints.

Abstract: A computer is programmed to parse a network that interconnects databases in a distributed database system, into a number of paths, wherein each path starts in a source database that is a source of changes and ends in a destination database that uses the changes to replicate the source database. The computer identifies databases that occur within each path in the network, and queries the identified databases to obtain statistics for each path. Statistics along each path are analyzed automatically, to identify a component in each path as a candidate for further investigation. The identified component may be marked as a bottleneck e.g. if there are no other paths connected to it. Alternatively the identified component may be a source of changes for another path that has a bottleneck or that has another candidate for further investigation. The identified bottleneck is displayed to the user with recommendations for improvement.

Abstract: A method for allowing client computers in a distributed object-based data storage system to interpret higher revision data structures. In one embodiment, clients request layout maps of objects to be accessed from respective storage managers in the system and then construct and execute directed acyclic graphs (DAG) to accomplish desired I/O operations for data access. When a client computer running an older software revision is not able to interpret a particular data organization supplied by the storage manager that was designed after that client's software was installed, the client sends to the storage manager a description of the desired data access operation. The storage manager, in turn, interprets a data layout scheme for a client on a per-access basis and returns to that client a DAG containing a data structure that describes the sequence of I/O operations necessary to effect the data access. The client can then execute the storage manager-supplied DAG to carry out the data access.

Abstract: Architecture for replicating a database through log shipping. A replication service replicates data using one or more new internal application program interfaces (APIs), a replay configuration API which abstracts configuration information for each destination (or target) instance. APIs for log file management as part of the replication process are provided for opening communications for log shipping, tracking success of log shipping and closing out log shipping communications. Log shipping APIs are also provided for log truncation control. A ship control object is provided as a base class which includes an API for other components of the replication service to operate on log files when the log files are placed into a log directory. The ship control API is utilized by the replication service and for interaction with storage system log files.

Abstract: To protect data from corruption due to restoration of an encryption key to a wrong storage system, there is provided a computer system including a first storage system and a second storage system, wherein: the first storage system, upon receiving a request to write first data to a first area in the first storage system, encrypts the first data by using a first key and writes the first data in the first area, and, upon receiving a request to write second data to a third area, encrypts the second data by using a second key and transmits a request to write the encrypted second data in a second area in the second storage system; and the computer system holds the first key, an identifier of the first storage system associated with the first key, the second key, and an identifier of the second storage system associated with the second key.

Abstract: Systems and methods for partitioning information across multiple storage devices in a web server environment. The system comprises a web server database which includes information related creating a web site. The information is divided into partitions within the database. One of the partitions includes user information and another of the partitions includes content for the web site. Portions of the content for the web site is replicated and maintained within the partition including the user information. Further, a portion of the user information is replicated and maintained in the partition where the content for the web site is maintained. The methods include dividing information into partitions, de-normalizing the received data and replicating the data portions into the various web site locations.

Abstract: Among other things, techniques and systems are disclosed for providing sync server process. Processing data sync sessions includes processing a request to initiate a sync session from one or more clients to update one or more data records that include one or more data items. The one or more clients are selectively identified as one of a trusted client and an untrusted client based on one or more properties of the sync session, wherein the trusted client is configured to support all dataclasses defined by the server. The one or more clients are detected as being configured to support field level differencing that sends changed data items only for the one or data records or record level differencing that sends all of the data items included in the one or more data records.

Abstract: Systems and methods for synchronizing data between endpoints, including the modification of data on an endpoint without necessarily modifying data that is communicated between endpoints are disclosed. In such systems and methods the representation of data on an endpoint may be modified so that constraints on that particular endpoint are enforced, without requiring a similar or the same modification to the data when it is synchronized to other endpoints.

Abstract: One embodiment is a method that builds a target database with transaction logs from an online source database. The transaction logs include both existing data in the source database and updates that occur to the source database while the target database is being built.

Abstract: A database-rearranging program which is capable of rearranging a database while maintaining high reliability, without stopping services provided by the database. When a request for rearranging the copy source database is input, a record copying module sequentially selects pages in the copy source database, and the records in the selected page are copied to the copy destination database. Further, the record copying module sets a progress of copying of each page of the copy source database to a page status management table. Thereafter, when a request for writing updated records is input, a record writing module refers to the page status management table, and when a page of the copy source database in which the updated records should be written is in an uncopied status, the updated records are written in the page of the copy source database, and when the same is in a copied status, the updated records are written in the copy source database and the copy destination database.

Abstract: Exemplary methods and systems may clone a tenant database and send updates to the clone. By doing so, methods and systems may determine a difference between the clone and the tenant, making it possible to test upgrades for a tenant based on the difference. With this capability, a provider-tenant system may upgrade tenant business applications and customize tenant databases.

Abstract: Systems and methods for synchronizing data between endpoints, including the modification of data on an endpoint without necessarily modifying data that is communicated between endpoints are disclosed. In such systems and methods the representation of data on an endpoint may be modified so that constraints on that particular endpoint are enforced, without requiring a similar or the same modification to the data when it is synchronized to other endpoints.

Abstract: Systems and methods are described for service availability that provides automated recovery of server service in a timely and application intelligent manner, maintaining application consistency and integrity, while preserving server identity. The systems and methods, referred to herein as a Service Preservation System (SPS), manage complete recovery of server data and preserve continuity of server service, reestablishing user access to server(s) after an event or disaster in which in which primary or other server(s) fail. The failures, disasters, and losses referred to herein can be at many levels and include, but are not limited to, accidental deletion of an item, loss of an entire mailbox, loss of an entire disk drive, loss of an entire server, and/or loss of an entire server site.

Abstract: In general, the invention relates to a client device. The client device includes a local data repository comprising a plurality of local case records associated with a local instance of a legal matter. The client device further includes a customization engine configured to display at least one of the plurality of local case records and a synchronization engine configured to synchronize the local instance of the legal matter with a corresponding web instance of the legal matter, wherein the web instance of the legal matter is located in a web data repository operatively connected to the client device.

Abstract: Provided are a method, system, and article of manufacture for converting backup copies of objects created using a first backup program to backup copies created using a second backup program. A plurality of backup copies of versions of an object are created using a first backup program, wherein the object has an object name. The first backup program is used to restore at least one of the backup copies to a restored version of the object having a name different from the object name. A second backup program is used to create a backup copy of each restored version of the object. A name of a designated object is assigned to each backup copy created using the second backup program. Metadata of each backup copy created using the second backup program is updated with metadata for the designated object.

Abstract: One embodiment includes a system for application-layer monitoring of communication between one or more database clients and one or more database servers. The system includes one or more decoders residing at a decoding layer above a network layer. The decoders reside at a first network location between one or more database clients residing at one or more second network locations and one or more database servers residing at one or more third network locations. The decoders receive database messages communicated from the database clients and intended for the database servers and database messages communicated from the database servers and intended for the database clients, decode the database messages, and extract query-language statements from the database messages. The system also includes a monitoring application residing at an application layer above the decoding layer. The monitoring application resides at the first network location.

Abstract: A recovery manager detects that a distributed transaction is unresolved for a first participant of said distributed transaction. The recovery manager identifies that the distributed transaction is unresolved for a second participant of said distributed transaction. The recovery manager generates a list of participants for which the distributed transaction is unresolved, the list including an entry for the first participant and an additional entry for the second participant. The recovery manager determines a result of the distributed transaction based on information received from a remote coordinator of said distributed transaction. The recovery manager notifies each participant identified in the list of the result.

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: Systems and methods for synchronizing data between endpoints, including the modification of data on an endpoint without necessarily modifying data that is communicated between endpoints are disclosed. In such systems and methods the representation of data on an endpoint may be modified so that constraints on that particular endpoint are enforced, without requiring a similar or the same modification to the data when it is synchronized to other endpoints.

Abstract: The subject matter discloses a system for adding a data item during a synchronization process, said system comprising a receiving (target) side electronic device having a database being compatible to a database of a sending (source) side, such that each data item has unique local and remote identifiers. The system comprises a control unit for assigning a local identifier and a remote identifier to the data item in the database of the receiving (target) side, such that the local identifier of the receiving (target) side is stored as the remote identifier of the sending (source) side and vice versa. After adding the data item, access to the data item stored in the database of the receiving (target) side, is enabled by receiving the remote identifier or the local identifier of the data item as stored in the database of the sending (source) side.

Abstract: The methods for handling a communication request received for a former user of a communication system include sending updated address book information for the former user to an initiator's address book, redirecting the communication request to the forwarding address for the former user, redirecting the communication request to an assigned replacement of the former user, or any combination of the above. Additionally, the replacement's address book information may be sent to the initiator's address book for updating. In one embodiment, a replication of the former user's address book is retained to assist in determining how to handle the received communication request.

Abstract: Systems and methods of accessing a database associated with a process control system send a request for information from a client application to an intermediate data server process and determine if the information is stored within a data source associated with the intermediate data server process. The systems and methods also send a request for the information from the intermediate data server process to another process if the information is not stored within the data source and access the database to retrieve the information subsequent to the other process receiving the request for the information.

Abstract: A method for communicating with remote devices wherein the method includes sending a request through an application programming interface (API), formatting the request and routing the request to a first connection associated with a first protocol. The method further includes mapping the request into a first command, wherein the first command conforms to the first protocol and sending the first command to a remote device.

Abstract: A computer-implemented method, information processing system, and computer program storage product validate a two-phase commit process. First information is received that indicates a plurality of web services to be tested. Each of the web services are associated with a different resource manager. Second information is received that indicates a plurality of application servers for performing the web services. A global transaction is created that includes a plurality of transactions based on the first information that was received. A two-phase commit process is initiated at one of the application servers for performing the global transaction. After the two-phase commit process has ended, results of the global transaction that include information regarding each of the transactions within the global transaction are displayed.

Abstract: In accordance with an embodiment of the present invention, a heterogeneous data sharing mechanism comprising a capture process and an apply process may be provided in a database system. The capture process mines or receives, at the source entity, a plurality of records that belong to a plurality of transactions. Here, first records from a first transaction in the plurality of transactions are interleaved with one or more records from one or more different transactions in the plurality of transactions. The capture process orders the plurality of records into a stream of ordered records such that all records that belong to a transaction are stored contiguously in a single block of records in the stream. Subsequently, the capture process sends the stream of ordered records from the source entity to the sink entity. Alternatively, the apply process retrieves the stream of ordered records from the capture process.

Abstract: A method and apparatus for obtaining data from a cluster of cache nodes in a tree-based structure is disclosed. A querying cache node outside a partition group queries data of a cache node of the partition group. The partition group is made of one or more cache nodes of the cluster, where an instance of a cache node in the partition group is copied to each cache node in the partition group. The instance of the data of the cache nodes of the partition group is copied to the querying cache node. The partition group is adjusted to include the querying cache node as a member of the partition group.

Abstract: A method and system for method for replicating object consisting of creating a group of objects at a first location; transmitting the group of objects from a first location to a second location over a network coupling the first location to the second location, such that the number of transmissions is minimized receiving the group of objects at the second location; and storing the group of objects at the second location. The objects are preferably data objects and are collated into group based on a probability score is computed for each data object centered on an access pattern. Advantages include minimizing the number of transmission of the group of objects thereby reducing network traffic and failure of operation during replication of the objects.

Abstract: The present application relates to a method for synchronizing heterogeneous databases using at least one processor, a first user database, a second user registers database, a third location criteria database and a fourth location occupancy database, the inputs of said first user database being likely to match the inputs of the third location criteria database, with the method including: a step of modification wherein the inputs of the fourth location occupancy database and the inputs of the second user register database are modified in response to a request; prior to the modification, the processor processes the request so as to check the matching between the inputs of the third location criteria database and the inputs of the first user database; depending on the checking, the processor sends a positive acknowledgement to the first location occupancy database and to the second user register database so as to carry out the modification.

Abstract: A method of storing all or part of data entered to an application program embedded in a personal data assistant to another application program is disclosed. A data storing method includes composing data in one of a plurality of application programs embedded in the personal data assistant, wherein the application programs have mutually different data formats, converting a format of the composed data to a suitable format for another application program manually or automatically, and storing the format-converted data in the other application program.

Abstract: A distributed storage system including support for distinct storage classes. A system may implement a web services interface, a number of storage nodes and a coordinator. The web services interface may receive, according to a web services protocol, client requests to store data objects. A request for a given object may include an indication of a particular storage class to be associated with the given object, and where each storage class respectively specifies one or more service level agreement (SLA) characteristics. The storage nodes may store replicas of the data objects. The coordinator may receive the client requests to store the data objects from the web services interface, where in response to the given client request, the coordinator may store one or more replicas of the given data object among the storage nodes according to the SLA characteristics specified by the particular storage class.

Abstract: A standby database system or another replica data system replicates changes, made to data blocks at a source database system or another primary data copy, to replicas of the data blocks at the standby database system or other replica. While replicating the changes to the data blocks thereof, the standby database system (or other replica) receives queries (or reads) issued thereto and computes the queries based on data read from the data blocks thereof.

Abstract: Methods, apparatus and computer programs are provided for data replication, such as for replicating a database or updating a cache. Source database change transactions are captured and batched together for efficient data transfer. On receipt at a target replica system, the batch of transactions within a message is separated and separate apply transactions corresponding to the source transactions are performed in parallel. A ‘transaction processed’ table is updated to reflect apply processing for each apply transaction. This table provides a confirmation of the status of each transaction that can be used during recovery processing to prevent re-apply of an apply transaction. The table can also be used to determine when it is safe to delete an incoming message from persistent storage on the target system, and to facilitate one-phase commit processing.

Abstract: A system is disclosed for synchronizing partially-replicated collections using the concept of item-set knowledge and move-out notifications. Move-out notifications are provided to allow removal of changed items from replicas when the change in the item takes that item outside of the interest set of the replicas.