Caching storage segments (e.g., pages) loaded from a remote storage such that, during recovery, the cached loaded storage segments may be at least partially recovered without reloading the storage segments from the remote storage. During normal operation of a computing system, storage segments are loaded from remote storage into local memory of a computing system. At some point, either due to eviction of the storage segment due to aging out of the storage segment, or due to writing of the storage segment, it is determined to write at least some of the loaded storage segments into local persistent storage. In conjunction with this, the corresponding storage segment is written to a respective storage address of the local persistent storage. Also, a correlation between an identifier of the storage segment and the respective address in the persistent storage is recorded in a persistent data structure.

Exemplary methods, apparatuses, and systems include determining that data in a group of memory cells of a first memory device is to be moved to a spare group of memory cells. The group of memory cells spans a first dimension and a second dimension that is orthogonal to the first dimension and the spare group of memory cells also spans the first dimension and the second dimension. The data is read from the group of memory cells along the first dimension of the group of memory cells. The data is written to the spare group of memory cells along the second dimension of the spare group of memory cells.

An embodiment method is disclosed for deriving an estimation value of a clock-error for a slave clock, wherein the slave clock is set at a nominal slave period and outputs a sequence of slave clock signals at an actual slave period, and wherein a difference between the actual slave period and the nominal slave period is approximated by the estimation value of the clock-error.

A containerized environment and application that are configured for component specific continuous replication and granular application level application. A key value store, which stores key values related to configuration data of the containerized application, is replicated continuously to a replicated key value store at a replica site. Persistent volumes may also be replicated to a replica site. The replication can be performed to multiple replica sites in an application specific manner.

The rebuilding process comprises the steps of detecting a failure on a first server that stores a first data and processes input/output requests from an application, redirecting incoming input/output requests from the application to a second server storing a second data. The second data being mirrored from the first data. The process further comprises forming, by the first server, a data loss information that identifies the lost data units in the first data. The process further comprises rebuilding, by the first server, the lost data units in the first data, by using the data that is retrieved from the second data and based on the data loss information by the second server. The process further comprises syncing up data units, other than the lost data units in the first data, with corresponding data in the second data in the second server during the rebuilding process.

A data verification apparatus includes a storage, a management unit, and a verification unit. The storage includes a first storage and a second storage. The first storage stores first data and first status information. The second storage stores second data and second status information. The management unit controls a write process and updates the first status information and the second status information in response to the write process, the write process being a process of writing the first data to the first storage on a basis of data acquired by communication with an external apparatus, and thereafter writing the second data to the second storage on a basis of the data. The verification unit verifies, in a state in which the communication is disconnected, the first data and the second data on a basis of the first status information and the second status information.

A computer system includes a BMC and a host of the BMC. The BMC receives a first message from a first remote device on a management network. The BMC determines whether the first message is directed to a storage service or fabric service executed on a central processing unit of the host. The host is a storage device. The central processing unit is in commutation with a RDMA controller through an external communication channel. The RDMA controller being managed by the storage service. The BMC extracts a service management command from the first message, when the first message is directed to the storage service or fabric service. The BMC sends, through a BMC communication channel to the host, a second message containing the service management command to the host. The BMC communication channel has been established for communicating baseboard management commands between the BMC and the host.

Switching from primary to backup data storage by preparing a backup copy of multiple data sets, where, prior to the preparing, the backup copy is updated in accordance with a backup protocol specifying synchronously updating the backup copy to reflect changes made to one type of data stored in a primary copy of the data sets, and asynchronously updating the backup copy to reflect changes made to another type of data stored in the primary copy, and where the preparing includes identifying any inconsistency in any interdependent data in the data sets of the backup copy in accordance with a predefined schema of interdependent data in the data sets, and correcting any identified inconsistency in the data sets of the backup copy in accordance with a predefined inconsistency correction protocol, and causing the backup copy to be used in place of the primary copy for directly servicing data transactions.

An error recovery method and apparatus, and a system are disclosed. At least two CPUs in a lockstep mode can exit the lockstep mode when an error occurs in at least one CPU, and the CPU in which the error occurs and a type of the error are determined. When the error can be recovered, the CPU in which the error occurs can be recovered according to a correctly running CPU. This helps the at least two CPUs run again at a position at which a service program is interrupted.

A blockchain transaction manager implements a method of managing submission of blockchain transactions to a node in a blockchain network by validating a received blockchain transaction and enqueuing the validated received blockchain transaction in a transaction queue, preparing at least one transaction attribute of the received blockchain transaction and placing the received blockchain transaction in a persistence queue, digitally signing or certifying the received blockchain transaction, attempting to submit the digitally signed or certified blockchain transaction to the node, and polling a blockchain status of the submitted blockchain transaction. Processes are provided for automatically recalculating blockchain transaction processing fees in the blockchain transaction attributes. Processes are also provided for repairing transaction attributes when the blockchain transaction has been rejected and submitting the repaired blockchain transaction to the node. Also, nonces are automatically assigned to received blockchain transactions and reassigned when the associated blockchain transaction has been rejected.