Embodiments of the present disclosure provide a data migration method and device, wherein the data migration method comprises: acquiring a migration request for a source database, creating a snapshot of to-be-migrated data in the source database and migrating the snapshot to a target database, reading a data migration log stored in a primary replica database of the source database and synchronizing the data migration log into the target database, and configuring a route for a target primary replica database of the target database according to routing rules of the primary replica database.

An illustrative embodiment disclosed herein is an apparatus including a processor having programmed instructions to detect an operation associated with a first object instance in a first cluster, determine that the first object instance is configured for replication to a second cluster, create an object information (info) metadata entry for the first object instance, create an object replication metadata entry for the first object instance, and simultaneously write the object info metadata entry and the object replication metadata entry to a first data structure and a second data structure, respectively.

A method of synchronizing a plurality of end points is disclosed. A spoke is connected to a hub. The connecting of the spoke to the hub includes performing inbound synchronization of all of a set of data items or a subset of the set of data items with a replica. One or more additional spokes are connected to the hub. The connecting of the one or more additional spokes to the hub includes performing inbound synchronization of all of an additional set of data items or a subset of the additional set of data items with an additional replica. A subset of a set of data items stored in the replica or the additional replica is selected for outbound synchronization with any of a plurality of spokes except a spoke from which the subset of data items originated.

A storage system performs data replication with a recovery point objective (RPO). The storage system replicates data at intervals through data transfers over a network. The storage system determines bandwidth of the network. The storage system determines the intervals for replicating the data, based on size of data transfers, network bandwidth, and the recovery point objective.

A method may include receiving data from the plurality of databases for an applicant to be placed on one or more waiting lists with one or more requirements. A user profile associated with the waiting list may be created based on the received data, and may be received from the applicant. An applicant ranking on the one or more waiting lists may be determined based on a match between the user profile and the one or more requirements. At least one of a need or a desire of the applicant may be monitored based on periodic activity of the applicant on the one or more waiting lists. Periodic changes to the one or more requirements may be monitored. The applicant ranking may be updated on the one or more waiting lists, and the updated one or more waiting lists may be synchronized with the plurality of databases.

Snapshots from a first LSU (R1) on a first storage system (A1) may be replicated to a second replica LSU (R2) on a second storage system (A2), for example, concurrently to remotely replicating (e.g., synchronously) write operations for R1 to R2. A process, P, on A1 executing the replication of the snapshots from R1 to R2 may be a separate process than the one or more processes on A1 executing remote replication of write operations for R1 to R2. During a consistency window on A1, outstanding write operations for R1 at the time the consistency window opened may be logged, and a pair of snapshots, SS1.sub.1 and SS1.sub.2 may be activated on R1 and R2, respectively. After the consistency window has closed, the SS1.sub.2 snapshot metadata and snapshot data may be updated based on the outstanding write operations.

Techniques are provided for dependency aware parallel splitting of operations. For example, a count of pending data operations being executed by a first node and replicated in parallel to a second node are tracked. A metadata operation is executed at the first node based upon the count being less than a threshold (e.g., the count being zero). A first list of affected inodes modified by the metadata operation is identified. A dependency of the metadata operation with respect to pending metadata operations replicated to the second node is determined. The metadata operation is dispatched to the second node based upon the dependency indicating that the metadata operation is independent of the pending metadata operations.

A data storage method and apparatus, an electronic device, a non-transitory computer-readable storage medium, and a computer program product are provided. The method includes: receiving a storage request carrying multimedia data transmitted by a target device, storing multimedia data in local space of a target storage node, and generating a target storage proof of the multimedia data, the target storage proof indicating that the target storage node has stored the multimedia data, and transmitting the target storage proof to a consensus node, to cause the consensus node, after receiving an uploading request about the multimedia data transmitted by the target device, to perform consensus verification on the multimedia data according to the target storage proof, and store a data identifier of the multimedia data that passes the consensus verification in a blockchain of the consensus node.

An example of an apparatus including a network interface to receive first metadata and second metadata. The first metadata is associated with a first data source and the second metadata is associated with a second data source. The apparatus includes a processor to determine a first series of variance values associated with first metadata and second metadata, and to determine a second series of variance values associated with first metadata and second metadata. Furthermore, the apparatus includes a memory storage unit to store the first series of variance values and the second series of variance values. The apparatus includes an analysis engine to analyze the first series of variance values and the second series of variance values to confirm compatibility between the first data source and the second data source. The second series of variance values is to be analyzed after the first series of variance values is passed.

Techniques for determining replication modes may include: issuing, while unsolicited data transfer mode is enabled for a first link, first write operations over the first link; issuing, while unsolicited data transfer mode is disabled for the first link, second write operations over the first link; determining a first performance metric for the first link in accordance with the first write operations; determining a second performance metric for the first link in accordance with the second write operations; and determining, in accordance with the first and second performance metrics whether to enable or disable unsolicited data transfer mode for the first link for a first time period. The first and second performance metrics may be response times. Unsolicited data transfer mode, when enabled, allows write data payload to be sent to a target without receiving an acknowledgement regarding receipt of a write command block for the write operation from the target.