Embodiments of the disclosure provide systems and methods for enabling disaster recovery from a source cluster to a target cluster in a multi-cluster cloud-computing environment. A domain cluster configures a replicated data volume to be updated with data from a data volume of the source cluster, wherein the replicated data volume resides in the target cluster; determines that the target cluster is to replace the source cluster as an active cluster; rebuilds, in the target cluster, a new container instance to replace the container instance on the source cluster; configures the container instance to utilize the replicated data volume in the target cluster; and discontinues recognition of the data volume and container instance on the source cluster as being authoritative.

Embodiments of the disclosure provide systems and methods for enabling disaster recovery from a source cluster to a target cluster in a multi-cluster cloud-computing environment. A domain cluster configures a replicated data volume to be updated with data from a data volume of the source cluster, wherein the replicated data volume resides in the target cluster; determines that the target cluster is to replace the source cluster as an active cluster; rebuilds, in the target cluster, a new container instance to replace the container instance on the source cluster; configures the container instance to utilize the replicated data volume in the target cluster; and discontinues recognition of the data volume and container instance on the source cluster as being authoritative.

An example operation may include one or more of retrieving, into a new node to be instantiated in a blockchain network, a state database checkpoint of a state database created at a block number of a blockchain of the blockchain network, retrieving, into the new node, blocks of the blockchain from the checkpoint block number to a current block number, constructing an initial state database from the received state database checkpoint, and executing, at the new node, the transactions of the retrieved blocks on the initial state database to generate a current state database.

Failover methods and systems for a storage environment are provided. During a takeover operation to take over storage of a first storage system node by a second storage system node, the second storage system node copies information from a first storage location to a second storage location. The first storage location points to an active file system of the first storage system node, and the second storage location is assigned to the second storage system node for the takeover operation. The second storage system node quarantines storage space likely to be used by the first storage system node for a write operation, while the second storage system node attempts to take over the storage of the first storage system node. The second storage system node utilizes information stored at the second storage location during the takeover operation to give back control of the storage to the first storage system node.

A computing device for use in a distributed storage network (DSN) to recover corrupt encoded data slices. The computing device requests, from storage units of the DSN, encoded data slices corresponding to a data segment. In response, the computing device receives at least a decode threshold number of encoded data slices and at least one integrity error message that provides an indication of a corrupt encoded data slice, such that less than a decode threshold number of valid slices is received. Utilizing at least one correction approach involving stored integrity data, the computing device corrects the corrupt slice(s) to produce a decode threshold number of encoded data slices in order to decode the corresponding data segment. A variety of correction approaches may be employed, including a multi-stage approach that utilizes data from both valid and invalid slices.

A network device includes at least one processor, a storage device and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the network device to: write data to the storage device; replicate the data at one or more remote network devices via at least one deterministic transmission medium; and output an acknowledgement in response to determining that the data has been written to the storage device prior to receiving confirmation of successful replication of the data at the one or more remote network devices. The methods, systems or computer readable mediums leverage the deterministic and measurable nature of the transmission media to reduce the Recover Point Objective durations.

A method, computer system, and a computer program for quick disaster recovery of cloud-native environments is provided. The present invention may include replicating at a secondary server site software executing in a cloud-native environment on a primary server site. The present invention may also include detecting a failure associated with the software executing in the cloud-native environment. The present invention may then include whether the detected failure is causing down time for the software executing in the cloud environment. The present invention may further include deploying the replicated software on the secondary server site in response to determining that the detected failure is causing down time.

The present disclosure relates to a digital asset conflict resolution system that provides conflict resolution of composite-part-based synchronized digital assets. In particular, the digital asset conflict resolution system detects conflicts within composite-part-based digital assets and resolves the conflicts at a composite-part level (i.e., composite-part level) within the digital asset based on format-specific rules. In various embodiments, the digital asset conflict resolution system utilizes format-specific rules and rule sets to automatically resolve conflicts at the composite-part level within a digital asset without duplicating the digital asset and without requiring immediate user involvement.

A server system including a first server to execute first role, other server to execute at other role, spare server and management layer server. The management layer server is configured to allocate first group of users to access first server and other group of users to access other server, receive status information sent by first server and status information sent by other server, analyse status information to determine an operational status of first server and operational status of other server, update role of spare server to first role when operational status of first server indicates failed state and reallocate first group of users to the spare server, and update a role of another spare server to the other role when the operational status of the other server indicates a failed state and reallocate the other group of users to the other spare server.

Techniques for achieving application high availability via application-transparent battery-backed replication of persistent data are provided. In one set of embodiments, a computer system can detect a failure that causes an application of the computer system to stop running. In response to detecting the failure, the computer system can copy persistent data written by the application and maintained locally at the computer system to one or more remote destinations, where the copying is performed in a manner that is transparent to the application and while the computer system runs on battery power. The application can then be restarted on another computer system using the copied data.