A system for persistently storing metadata associated with a backup of data in a source database. The system includes a cloud storage system and a source database. The source database includes a memory including data and a first electronic processor. The first electronic processor is configured to write a backup of the data included in the memory of the source database to the cloud storage system. The first electronic processor is also configured to write metadata associated with the backup of the data (“backup metadata”) to a table included in the memory of the source database. The backup metadata is used to retrieve the data when a target database is restored to a previous state of the source database.

A data storage subsystem is disclosed that implements a process for storing and/or reconstructing system data, such as a system mapping table. In certain embodiments, table pages are systematically copied, or flushed, to non-volatile memory in a progressive manner, according to a fixed ratio of flushed table pages per table update trigger, thereby facilitating write and/or load efficiency. Full or partial reconstruction of a table may be performed within a bounded number of operations based on the size of the table, the ratio implemented, and/or other characteristics.

A verification architecture described according to embodiments of the present invention validates changes made to metadata and may comprise one or more subsystems and phases. According to some embodiments, the “mkfs” volume creation utility works in cooperation with the device driver to create a file system volume by means of reservation and initialization space for metadata structures inside the device's partition that is reserved for the specific file system volume. The storage device uses a verified area legend when checking write requests after the file system volume has been created. The verified area legends may be stored in a dedicated partition or inside the master boot record (MBR) or Globally Unique Identifier (GUID) partition table (GPT) or special memory chip (NAND flash, for example). Write requests that overlap with any extent of reserved metadata area must be verified to prevent metadata corruption.

A plurality of computing devices are communicatively coupled to each other via a network, and each of the plurality of computing devices is operably coupled to one or more of a plurality of storage devices. A plurality of failure resilient address spaces are distributed across the plurality of storage devices such that each of the plurality of failure resilient address spaces spans a plurality of the storage devices. The plurality of computing devices maintains metadata that maps each failure resilient address space to one of the plurality of computing devices. The metadata is grouped into buckets. Each bucket is stored in a group of computing devices. However, only the leader of the group is able to directly access a particular bucket at any given time.

A system includes a memory array and control logic, operatively coupled to the memory array, to perform operations including causing, during chip initialization, a first attempt of a chip initialization process to be performed based on a first configuration. The first configuration includes a first set of control settings for reading a block of the memory array during the first attempt. The operations further include determining that the first attempt has failed, and, in response to determining that the first attempt has failed, causing an automatic chip initialization retry process to be performed. Causing the automatic chip initialization retry process to be performed includes causing a second attempt of the chip initialization process to be performed using a second configuration. The second configuration includes a second set of control settings different from the first set of control settings for reading the block during the second attempt.

An information handling system may include at least one processor; and a Non-Volatile Memory Express (NVMe) solid state drive (SSD) communicatively coupled to the at least one processor; wherein the information handling system is configured to: collect telemetry information regarding the information handling system; and log the telemetry information in a vendor-specific portion of the NVMe SSD via an NVMe set command.

A method for synthetic incremental data backup, a corresponding system and a corresponding computer-readable medium are provided. The method is executed by a data device and a backup device and includes: generating an incremental backup data and an incremental block change record (BCR) of an N-th backup according to a current data of the data device of an M-th backup and a current data of the data device of the N-th backup, wherein N is an integer greater than or equal to three and M is a positive integer less than N; generating a synthetic backup data and a synthetic BCR of the N-th backup according to a synthetic backup data and a synthetic BCR of the M-th backup and the incremental backup data and the incremental BCR of the N-th backup; and storing the synthetic backup data and the synthetic BCR of the N-th backup in the backup device.

A memory tier is established in a cluster system having a deduplicated file system. The memory tier includes memory pages configured as huge pages, where writes to the huge pages are exported in a device file that is outside of a user process namespace within which processes of the deduplicated file system run. At least a portion of metadata generated by the deduplicated file system is written to the memory tier. The portion of metadata includes an index of fingerprints corresponding to data segments stored by the deduplicated file system to a storage pool. A determination is made that an instance of the deduplicated file system has failed. A new instance of the deduplicated file system is started to recover file system services by loading the index of fingerprints from the device file.

Performing disaster recovery in a cloud-based storage system, including: creating, by a storage system a snapshot of a dataset; uploading, from the storage system to a cloud computing environment, the snapshot; storing, by the cloud computing environment, the snapshot; detecting, by the cloud computing environment, that the dataset is not available on the storage system; and creating, by the cloud computing environment using the snapshot that is stored within the cloud computing environment, a cloud-based storage system that includes the dataset.

A computer-implemented method according to one embodiment includes receiving, on a first cluster site, extended attributes associated with a first data operation where the first data operation was previously performed on data of a filesystem of second cluster site. In response to a second data operation being performed on data of a filesystem of the first cluster site, extended attributes associated with the second data operation are stored to a predetermined file of the filesystem of the first cluster site. The method further includes outputting, to the second cluster site, the extended attributes stored to the predetermined file of the filesystem of the first cluster site, and in response to a determination that a predefined event has occurred on the second cluster site, using the received extended attributes to fulfill a third data operation.