A system and method includes partitioning a network into first and second sub-networks connected by a network connection. A first component with first configuration data and a first local server are located in the first sub-network; a second component with second configuration data and a second local server are located in the second sub-network. The first configuration data is stored on the first and second local servers. The network connection is interrupted and the first configuration data is updated on the first local server. The network connection is re-connected, and if the first configuration data on the second local server is unchanged, the first configuration data on the second local server is overwritten.

Example embodiments relate generally to systems and methods for continuous data protection (CDP) and more specifically to an input and output (I/O) filtering framework and log management system to seek a near-zero recovery point objective (RPO).

Systems and techniques are provided for a tree structure for byzantine fault tolerance. A validator computing device may receive a candidate block from a block producer. The block producer may be a second validator computing device of the distributed network. The validator computing device may determine whether or not the candidate block is valid. The validator computing device may sign an indication of whether or not the candidate block is valid to generate a signature. The validator computing device may send the signature to a third validator computing device that is a sibling node to the validator computing device. The validator computing device may receive a second signature from the third validator computing device. The validator computing device may combine the signature and the second signature to generate a combine signature if the signature and the second signature agree.

Snapshots may be used to implement remote replication, for example, asynchronously, between a first storage system, A1, and a second storage system, A2. A1 may take a first snapshot, SS2.sub.1, of a logical storage unit, R1. After the snapshot SS2.sub.1 it taken, any dependent write operations associated with SS2.sub.1 may be reconciled, and differences between SS2.sub.1 and the last snapshot for R1, SS1.sub.1, may be determined and recorded as a difference set. One or more replication instructions for R1 that include the write operations (or data and metadata corresponding thereto) of the difference set may be sent from A1 to A2. A2 may apply the differences to R2, and then take (activate) a snapshot of R2, SS2.sub.2, which is a replica of SS2.sub.1. After A2 activates SS2.sub.2, A2 may send an acknowledgement to A1 indicating that SS2.sub.2 has been activated, and A2 may take a next snapshot of R1.

Techniques are provided to recover from partial device errors of storage devices in a data storage system. A storage control system manages a storage device which comprises storage capacity that is logically partitioned into segments of equal size. The storage control system groups at least some of the segments of the storage device into a segment group. Each segment of the segment group is configured to store one or more data items and associated metadata items. The storage control system generates a parity data segment based on the segments of the segment group, and persistently stores the parity data segment in association with the segment group. In response to detecting a storage device error associated with a corrupted segment of the segment group, the storage control system utilizes the parity data segment and non-corrupted segments of the segment group to recover at least one missing data item of the corrupted segment.

Snapshots of a first logical storage unit (LSU) (R1) on a first storage system (A1) may be taken while replication is inactive between A1 and a second storage system (A2), such that these outstanding snapshots are not replicated to a second replica LSU (R2) on A2. Upon replication becoming active, the outstanding snapshots may be replicated to R2 without disrupting or impairing the remote replication of write operations between R1 and R2 as part of standard remote replication. A process on A1 executing the replication of the outstanding snapshots from R1 to R2 may be a separate process than one or more processes on A1 executing standard remote replication including the replication of write operations from R1 to R2. The process may be given low priority on A1 so as to not impair performance of other operations, including standard remote replication and replicating outstanding write operations on A1.

Various embodiments are directed to techniques for coordinating at least partially parallel performance and cancellation of data access commands between nodes of a storage cluster system. An apparatus may include a processor component of a first node coupled to a first storage device storing client device data; an access component to perform replica data access commands of replica command sets on the client device data, each replica command set assigned a set ID; a communications component to analyze a set ID included in a network packet to determine whether a portion of a replica command set in the network packet is redundant, and to reassemble the replica command set from the portion based if the portion is not redundant; and an ordering component to provide the communications component with set IDs of replica command sets of which the access component has fully performed the set of replica data access commands.

A method of fault-tolerant process control includes providing a network process control system in an industrial processing facility (IPF) including a plant-wide network coupling a server to computing platforms each including computing hardware and memory hosting a software application for simultaneously supporting a process controller and another process controller or an I/O gateway. The computing platforms are coupled together by a private path redundancy network for providing a hardware resource pool. At least some of the computing platforms are directly coupled by an I/O mesh network to a plurality of I/O devices to field devices that are coupled to processing equipment. Upon detecting at least one failing device in the hardware resource pool, over the private path redundancy network a backup is placed into service for the failing device from the another process controller or I/O gateway that is at another of the computing platforms in the hardware resource pool.

A computer-implemented method of continuous restore for containerized applications includes initiating a continuous restore process for a containerized application having an application template and application data, where the containerized application executes on a first cluster. A backup plan for the containerized application is generated. A persistent volume containing the application data in the first cluster is identified and some of the application data is moved from the persistent volume to a backup target based on the backup plan schedule. The backup plan is received at a data synch process executing on a second cluster. A persistent volume is created on the second cluster. Some of the application data is moved from the backup target to the created persistent volume on the second cluster based on the backup plan schedule. The containerized application is recovered at the second cluster based on some of the application data moved to the persistent volume on the second cluster by the data synch process such that the recovered containerized application is operational at the most recent backup point-of-time of the backup plan schedule.

A system determines that a primary event processor, included in a primary data center, is associated with a failure. The primary event processor is included in the primary data center and configured to process first events stored in a main event store of the primary data center. The system identifies a secondary event processor, in a secondary data center, that is to process one or more first events based on the failure. The primary event processor and the secondary event processor are configured to process a same type of event. The system causes, based on a configuration associated with the primary or secondary event processor, the one or more first events to be retrieved from one of the main event store or a replica event store. The replica event store is included in the secondary data center and mirrors the main event store of the primary data center.