The present disclosure includes apparatuses and methods for proactive corrective actions in memory based on a probabilistic data structure. A number of embodiments include a memory, and circuitry configured to input information associated with a subset of data stored in the memory into a probabilistic data structure and proactively determine, at least partially using the probabilistic data structure, whether to take a corrective action on the subset of data stored in the memory.

A storage system has a cluster structure in which a node is connected with a different node, the node having a volatile memory for storing first update data from a host and a first non-volatile memory for storing second copy data of second update data from the host to the different node, and having a copy management processing unit for storing first copy data of the first update data into a second non-volatile memory of the different node, and a storage service processing unit for transmitting, to the host, a response with respect to an update request of the first update data in response to the storage of the first copy data of the first update data by the copy management processing unit into the second non-volatile memory of the different node.

A data center includes: a server including a control plane; a data plane that is configured to receive network connection information from the control plane; and a storage group including a plurality of first storage devices. The data plane may be configured to set connections between the server and the plurality of first storage devices based on the network connection information corresponding to each first storage device of the plurality of first storage devices.

Systems and methods for re-aligning data replication configuration of a cross-site storage solution after a failover are provided. According to one embodiment, after a failover, the new primary distributed storage system orchestrates flipping of the data replication configuration of a peered consistency group (CG) to reestablish zero RPO and zero RTO protections for the peered CG. The primary causes the secondary distributed storage system to perform an atomic database operation on its remote configuration database to (i) delete an existing source configuration that identifies the secondary as a source of data replication; and (ii) persist a new destination configuration identifying the secondary as a destination of data replication. Then, the primary performs an atomic database operation on its local configuration database to (i) delete an existing destination configuration identifying the primary as the destination; and (ii) persist a new source configuration identifying the distributed storage system as the source.

A method, computer program product, and computing system for processing memory page metadata received from a cache memory system within a data storage system to determine if the memory page metadata includes corruption due to a power failure event; if the memory page metadata includes post-acknowledgement data corruption, initiating a data recovery process to attempt to recover content associated with the post-acknowledgement data corruption; and if the memory page metadata includes pre-acknowledgement data corruption, reobtaining content associated with the pre-acknowledgement data corruption.

The present disclosure discloses a method, a system, and a solid-state drive for data processing. The method includes detecting the user operations on a first storage area which is visible to an operating system in a solid-state drive; if the user operation is a reading or writing operation, keeping the data of the first storage area and the data of a mirrored data storage area of a second storage area to be synchronization; if the user operation is a deleting operation or a TRIM operation, keeping the data of the first storage area and the data of the mirrored data storage area of the second storage area to be synchronization, and backing up the deleted data from the first storage area to a deleted data storage area of the second storage area. The second storage area is set to be invisible to the operating system in the solid-state disk.

A data center includes: a server including a control plane; a data plane that is configured to receive network connection information from the control plane; and a storage group including a plurality of first storage devices. The data plane may be configured to set connections between the server and the plurality of first storage devices based on the network connection information corresponding to each first storage device of the plurality of first storage devices.

Systems, apparatuses and methods may provide for technology that conducts a first copy of firmware data from a first partition in a storage device to a second partition in the storage device, detects a recovery condition with respect to the firmware data in the first partition, and automatically conducts a second copy of the firmware data from the second partition to the first partition in response to the recovery condition. In one example, the firmware data defines one or more settings for firmware code.

Techniques perform storage management. Such techniques involve: in response to receiving, at a first processor of a storage system, a write request from a host for writing user data, caching the user data in a first cache of the first processor, and generating cache metadata in the first cache, the cache metadata including information associated with writing the user data; sending the user data and the cache metadata to a second cache of a second processor, for the second processor to perform, in the second cache, data processing related to cache mirroring by the second processor; and sending, to the host, an indication of completion of the write request, without waiting for the second processor to complete the data processing. Such techniques can improve system performance such as reducing latency, and shortening length of the I/O handling path of write request.

Systems and methods for re-aligning data replication configuration of a cross-site storage solution after a failover are provided. According to one embodiment, after a failover, the new primary distributed storage system orchestrates flipping of the data replication configuration of a peered consistency group (CG) to reestablish zero RPO and zero RTO protections for the peered CG. The primary causes the secondary distributed storage system to perform an atomic database operation on its remote configuration database to (i) delete an existing source configuration that identifies the secondary as a source of data replication; and (ii) persist a new destination configuration identifying the secondary as a destination of data replication. Then, the primary performs an atomic database operation on its local configuration database to (i) delete an existing destination configuration identifying the primary as the destination; and (ii) persist a new source configuration identifying the distributed storage system as the source.