Disclosed herein are various embodiments for an employee data replication system. An embodiment operates by receiving a request to replicate employee data hosted by a host system. At least one of: a live date corresponding to when the employee data is to be live on the enterprise system or a selection of one or more applications to be used on the enterprise system is identified. A cutoff date for the employee data is calculated based on one or more of the live date and the selection of one or more applications, the cutoff date indicating an oldest date for which the employee data is to be replicated to the enterprise system. Employee data is replicated from the host system to the enterprise system based on the cutoff date, and an indication is provided that the replication has completed.

Methods and systems for cross cluster replication are provided. Exemplary methods include: periodically requesting by a follower cluster history from a leader cluster, the history including at least one operation and sequence number pair, the operation having changed data in a primary shard of the leader cluster; receiving history and a first global checkpoint from the leader cluster; when a difference between the first global checkpoint and a second global checkpoint exceeds a user-defined value, concurrently making multiple additional requests for history from the leader cluster; and when a difference between the first global checkpoint and the second global checkpoint is less than a user-defined value, executing the at least one operation, the at least one operation changing data in a primary shard of the follower cluster, such that an index of the follower cluster replicates an index of the leader cluster.

Techniques are provided for enforcing policies at a sub-logical unit number (LUN) granularity, such as at a virtual disk or virtual machine granularity. A block range of a virtual disk of a virtual machine stored within a LUN is identified. A quality of service policy object is assigned to the block range to create a quality of service workload object. A target block range targeted by an operation is identified. A quality of service policy of the quality of service policy object is enforced upon the operation using the quality of service workload object based upon the target block range being within the block range of the virtual disk.

A device, system and method for mode-based synchronization of data records is provided. Booking data is received, at one or more computing devices, from one of a first and second client device. When received from the first client device, in a first order mode for the booking data, the device(s): cause an order management system (OMS) to generate: order data at a first database; and cause a legacy system to generate a corresponding passenger name record (PNR) at a second database, the corresponding PNR being slaved to the order data. When received from the second client device, in a legacy mode for the booking data, the device(s): cause the legacy system to generate, a PNR and/or ticket data at the second database; and cause the OMS to generate corresponding order data at the first database, the corresponding order data being slaved to the PNR and/or the ticket data.

Techniques are provided for tracking a number of transactions-of-interest in a transaction-recording blockchain using a control blockchain. A transaction-of-interest is a transactions that is in a particular state. A request to perform an action is received. Upon receiving the request and determining that the action corresponds to a new transaction-of-interest, a control blockchain is checked to determine the current number of transactions-of-interest in the transaction-recording blockchain and maximum allowed number of transaction-of-interest for the transaction-recording blockchain. In response to determining that the current number of transaction-of-interest in the transaction-recording blockchain are less than the maximum allowed: allowing the action to occur, adding a new block to the transaction-recording blockchain, and updating the control blockchain to indicate the new number of transaction-of-interest. In response to determining that the current number of transaction-of-interest are at least at the maximum allowed number, prohibiting the addition of a new block to the transaction-recording blockchain.

Devices, methods, and systems for multi-user commissioning are described herein. One system includes a mobile computing device comprising computer readable instructions stored thereon that are executable by a processor to: retrieve configuration data for a physical controller from a remote database, install the configuration data on the physical controller, receive data associated with a status of the physical controller after the configuration data is installed on the physical controller, and synchronize the data associated with the status of the physical controller with the remote database.

A data synchronization method and device for databases, and a storage medium are disclosed. The method includes: in the case where transaction response results fed back by multiple data nodes are all successful, receiving transaction commit request messages sent by a client, and writing a global transaction ID into a transaction processing list; sending the transaction commit request messages to the multiple data nodes; receiving transaction commit results fed back by the multiple data nodes; and in the case where the transaction commit results fed back by the multiple data nodes are all successful, applying to a global transaction manager to release the global transaction ID.

Maintaining a synchronous replication relationship between two or more storage systems, including: receiving, by at least one of a plurality of storage systems across which a dataset will be synchronously replicated, timing information for at least one of the plurality of storage systems; and establishing, based on the timing information, a synchronous replication lease describing a period of time during which the synchronous replication relationship is valid, wherein a request to modify the dataset may only be acknowledged after a copy of the dataset has been modified on each of the storage systems.

The invention provides for a cloud-based solution that saves all the data in the cloud storage. The peer devices synchronize data among each other independent of the operating system since the data is synced via web services. Synchronization of data among peer devices is possible even when cloud service is unavailable via a router, Wi-Fi, Bluetooth, NFC or any other mechanism. The peer devices form a hierarchical structure, which designates a master, and the master communicates with the cloud-based service to synchronize data. The master then synchronizes data with the other peer devices in the hierarchy. New devices can be added to the peer devices and can join the hierarchy.

Replicated instances in a database environment provide for automatic failover and recovery. A monitoring component can periodically communicate with a primary and a secondary replica for an instance, with each capable of residing in a separate data zone or geographic location to provide a level of reliability and availability. A database running on the primary instance can have information synchronously replicated to the secondary replica at a block level, such that the primary and secondary replicas are in sync. In the event that the monitoring component is not able to communicate with one of the replicas, the monitoring component can attempt to determine whether those replicas can communicate with each other, as well as whether the replicas have the same data generation version. Depending on the state information, the monitoring component can automatically perform a recovery operation, such as to failover to the secondary replica or perform secondary replica recovery.