A method for facilitating data synchronization across a plurality of platforms is provided. The method includes retrieving a change event, the change event corresponding to an event stream from a first platform; parsing the change event to identify a record and a data operation; examining a synchronization database to determine whether a corresponding record is persisted in a database of a second platform; inserting the record into the synchronization database when the corresponding record is not persisted in the platform, the inserted record including a change indicator; and updating, by using the synchronization database, the database of the second platform to include the record.

A Processing-In-Memory (PIM) device includes an error correction code (ECC) logic circuit and an error accumulation detection circuit. The error correction code (ECC) logic circuit configured to detect an erroneous bits included in first data to generate a parity bit, and to detect an error correction capability of the first data to generate an error correction fail signal. The error accumulation detection circuit configured to generate an error accumulation signal counted by a pulse of the error correction fail signal. The error correction capability set to the maximum number of erroneous bits that can be corrected by performing an ECC operation on the first data.

A data storage device restoring method is provided, which is adapted to a data storage device. The data storage device includes an SSD controller, a power management circuit, a non-volatile memory, and a reset circuit. The data storage device restoring method includes: the power management circuit determines whether a normal signal from the SSD controller is received within a predetermined time; if not, the power management circuit resupplies power to the data storage device but stops supplying power to the non-volatile memory, thereby the SSD controller stays in a read-only memory mode to automatically execute the data storage device restoring process.

To be able to support the efficient handling of problems during maintenance. A management board determines an accomplishment sequence of handling manipulation for failures on a maintenance target. The management board includes a CPU, memory, and a storage device. The memory or the storage device stores: condition information associating the handling manipulation with a condition concerning at least accomplishment or non-accomplishment of the manipulation; and failure handling information that associates a failure occurring on the maintenance target with the handling manipulation. The CPU is configured to determine the accomplishment sequence of the handling manipulations so that multiple handling manipulations for multiple failures occurring on the maintenance target satisfy the condition.

A request manager analyzes API calls from a client to a host application for state and performance information. If current utilization of host application processing or memory footprint resources exceed predetermined levels, then the incoming API call is not forwarded to the application. If current utilization of the host application processing and memory resources do not exceed the predetermined levels, then the request manager quantifies the processing or memory resources required to report the requested information and determines whether projected utilization of the host application processing or memory resources inclusive of the resources required to report the requested information exceed predetermined levels. If the predetermined levels are not exceeded, then the request manager forwards the API call to the application for processing.

Techniques for database and file management herein include a processor and a memory device storing instructions that cause the processor to perform operations comprising creating a request based on an extensible markup language (XML) or an interpreted scripting language object, wherein the request comprises unauthenticated data for validation. The operations can also include transmitting the request to a remote device), updating metadata corresponding to the request to indicate the successful validation by the remote device, validating a response file, and detecting a discrepancy between the unauthenticated data and the authenticated data accessible by the remote device. Additionally, the operations include obtaining correction data to resolve the discrepancy, and executing a transaction based on the request and the correction data.

A storage device and an operating method thereof are provided. The storage device includes a non-volatile memory, an interconnect, a device controller and a buffer memory. The interconnect exchanges data with a host, receives a logging target setting request and a logging period setting request with respect to debugging information from the host, receives a debugging information logging request from the host, and receive a read request from the host. The device controller includes a buffer memory and controls the non-volatile memory, controls a logging operation on the debugging information based on a logging target and a logging period, which are requested by the host, in response to the debugging information logging request, and transmits the debugging information to the host in response to the read request. The device controller is further configured to logs the debugging information in the buffer memory according to the debugging information logging request.

Described is an improved approach to implement fast detection of node death. Instead of just relying on multiple heart beats to fail in order to determine whether a node is dead, the present approach performs an on demand validation using RDMA to determine whether the node is reachable, where the approach of using RDMA is significantly faster than the heartbeat approach.

A storage controller has an operating system (OS) and power control firmware configured to manage use of battery power during a power outage event. The OS specifies to the power control firmware first and second sets of physical components that should be shed by power control firmware during a two-phase vault process. Upon a power failure, the power control firmware turns off power to the first set of physical components and notifies the OS of the power failure. The OS determines whether to abort or continue the vault process. If the OS aborts the vault process, the power control firmware restores power to the first set of physical components. If the OS continues the vault process, the power control firmware turns off power to the second set of physical components, the OS saves application state, and moves all data from volatile memory to persistent memory.

Systems and methods are disclosed for detecting shingled overwrite errors. When a read error is encountered when reading from shingled recording tracks, a processor may determine whether the read error is an error caused by shingled overwriting. The processor may determine whether the read error is caused by shingled overwriting by determining read signal quality of one or more sectors preceding the read error, such as based on a bit error count or bit error ratio (BER), and comparing the read signal quality to a threshold value. The processor may determine that the read error is caused by shingled overwriting when the read signal quality value is lower than the threshold.