A spare robot controller for replacing any one of a plurality of initial robot controllers configured to control operation of respective industrial robots includes a key storage storing a plurality of shared keys and a secure storage. The spare robot controller is configured to decrypt, using one of the shared keys, an encrypted backup copy of the initial robot controller to be replaced, and to store resulting data in the secure storage. In embodiments, the is configured to extract data from the secure storage during operation and to encrypt the extracted data, using a selected one of the shared keys, for storage as a backup copy in a backup storage available to all of the initial robot controllers.

A clustered pair of storage systems configured for active-active bidirectional synchronous replication expose a stretched volume over paths to both storage systems. Writes to the stretched volume received at each system are replicated to the peer system. The cluster can use a time-to-live (TTL) mechanism by which a non-preferred system continuously requests a TTL grant from the preferred system to remain in the cluster. Algorithms that reduce or avoid data unavailability are described and can include assessing the health of the systems in the cluster. An unhealthy system can trigger a one-sided polarization algorithm to notify the peer system that it is polarization winner. An improved polarization technique using a witness to decide the polarization winner includes a system adding a time delay before contacting the witness if the system is unhealthy. A control component can detect an unhealthy system and disable the active-active bidirectional synchronous replication.

A configuration for a component of a primary node is synchronized with a configuration for a component of a partner node in a different cluster by replicating the primary node configuration with the partner node. A baseline configuration replication comprises a snapshot of a component configuration on the primary. The baseline configuration can be generated by traversing through the configuration objects, capturing their attributes and encapsulating them in a package. The baseline package can then be transferred to the partner node. The configuration objects can be applied on the partner node in the order in which they were captured on the primary node. Attributes of the configuration objects are identified that are to be transformed. Values for the identified attributes are transformed from a name space in the primary node to a name space in the partner node.

A flight management system for an aircraft and method of securing open world data using such a system. The flight management system includes at least two flight management computers including one computer termed active forming part of an active guidance subsystem configured to supply data for guiding the aircraft. Another computer is termed inactive at the current time. The flight management system includes a validation subsystem that includes the inactive flight management computer and a validation unit connected to the flight management computers. The validation subsystem is independent of the active guidance subsystem and configured to validate open world data and to transmit at least to the active flight management computer data that is validated during the validation.

Embodiments of the present disclosure include an error recovery method comprising detecting a computing error, restarting a first artificial intelligence processor of a plurality of artificial intelligence processors processing a data set, and loading a model in the artificial intelligence processor, wherein the model corresponds to a same model processed by the plurality of artificial intelligence processors during a previous processing iteration by the plurality of artificial intelligence processors on data from the data set.

One example method includes intercepting an IO issued by an application of a VM, the IO including IO data and IO metadata, storing the IO data in an IO buffer, writing the IO metadata and a pointer, but not the IO data, to a splitter journal in memory, wherein the pointer points to the IO data in the IO buffer, forwarding the IO to storage, and asynchronous with operations occurring along an IO path between the application and storage, evacuating the splitter journal by sending the IO data and the IO metadata from the splitter journal to a replication site.

A method, computer program product, and computing system for identifying a replication link failure between a first volume of a first storage array and a second volume of a second storage array, wherein a first storage protocol identifier is associated with each of the first volume and the second volume. One of the first volume and the second volume may be defined as inaccessible and the other of the first volume and the second volume as accessible, thus defining an inaccessible volume and an accessible volume. The first storage protocol identifier associated with the inaccessible volume may be replaced with a second storage protocol identifier. Access to the inaccessible volume may be provided via the second storage protocol identifier.

A method for performing a backup operation includes obtaining, by a backup agent, a backup request for a file system, and in response to the backup request: generating a first application partition for an application associated with the file system, performing a dependency analysis on the application to identify application dependency information, populating a first application partition with a copy of the application dependency information and a copy of application data associated with the application, and initiating a storage of a backup to a backup storage system, wherein the backup comprises the first application partition.

A self-healing data synchronization process includes an initial stage in which a collection of data change events is received, a set of data record(s) corresponding to the data change event(s) is identified, and a syncing of the set of data record(s) is initiated. Data that indicates which data record(s) successfully synced and which failed is stored. During a subsequent stage of the self-healing process, data change events that occurred during a preceding time horizon are identified, a corresponding first set of data record(s) are identified, a difference between the first set and a second set of data record(s) that successfully synced during the time horizon is determined as a third set of data record(s), and any data record that was attempted to be synced during the time horizon but failed is excluded from the third set. A sync of any data record remaining in the third set is then initiated.

Techniques for implementing RDMA-based recovery of dirty data in remote memory are provided. In one set of embodiments, upon occurrence of a failure at a first (i.e., source) host system, a second (i.e., failover) host system can allocate a new memory region corresponding to a memory region of the source host system and retrieve a baseline copy of the memory region from a storage backend shared by the source and failover host systems. The failover host system can further populate the new memory region with the baseline copy and retrieve one or more dirty page lists for the memory region from the source host system via RDMA, where the one or more dirty page lists identify memory pages in the memory region that include data updates not present in the baseline copy. For each memory page identified in the one or more dirty page lists, the failover host system can then copy the content of that memory page from the memory region of the source host system to the new memory region via RDMA.