An object of the invention is to reduce a data transfer amount between storage systems. Provided is a storage system connected to another storage system via a network. The storage system includes a memory, a processor configured to execute a program stored in the memory, and a storage device. By executing the program, the processor provides a virtual volume, generates a plurality of snapshots at different timings for the virtual volume, holds a base snapshot, which is a reference snapshot among the plurality of snapshots, in the storage device, and transmits difference data indicating a difference between a snapshot generated after the base snapshot and a snapshot generated immediately before the snapshot to the other storage system and holds the difference data in the other storage system.

Described herein are embodiments of a database system. The database system receives a read command to read at least some stored data. The database system may generate a plurality of snapshots of data stored in a first data storage node of a plurality of data storage nodes. The database system may determine whether data is being written to the first data storage node. Responsive to determining that data is not being written to the first data storage node, the database system may process the read command at least in part by reading at least some data stored on the first data storage node. Responsive to determining that data is being written to the first data storage node, the database system may process the read command at least in part by reading at least some data from a snapshot of the plurality of snapshots.

An approach is provided for autonomous and optimal cloning, reinstating, and archiving of a containerized application. Application metadata is obtained from a catalog. Cloning rules specifying cloning an application are obtained. Application components are selected for cloning and the cloning is determined to be compliant with the cloning rules. The application components are cloned and data for the clone is saved to a clone repository. The catalog is updated with specifications of the cloned application components. Reinstating rules specifying reinstating a clone of the application are obtained. Reinstating the clone is determined to be compliant with the reinstating rules. The catalog is updated with specifications of the reinstated clone. In one embodiment, the catalog is updated with inferred associations among applications and identified rules associated with the application, where the inferred associations and identified rules are generated by a trained machine learning-based classifier.

In order to quickly recover a management information file, an Edge file storage stores user files and a management information file that manages management states of the user files in the Edge file storage. The Edge file storage manages operation logs indicating operation contents concerning user files accepted by nodes in association with the respective nodes. The Edge file storage extracts operation logs for a user file associated with a targeted management information file as a management information file stored in a failed node from the operation logs corresponding to the nodes. The Edge file storage aggregates operation logs that are extracted from the operation logs corresponding to the nodes and are used for the user file associated with the targeted management information file. The Edge file storage recovers the targeted management information file based on the aggregated operation log.

A method for managing file based backups (FBBs) includes obtaining, by a FBB metadata file manager and by an application, a file request for a file stored in a FBB, wherein the FBB is stored in a backup storage system, identifying, using a FBB metadata file of the FBB, a storage location of the file, initiating generation of a temporary storage device, storing a copy of the file in the temporary storage device using the storage location and the FBB, and initiating, after the storing, access to the copy of the file for the application.

A method and system for source versus target metadata-based data integrity checking. Concerning backup operations directed to protecting given data, said given data may be subjected to corruption detection at the source prior to initiating a backup operation, however, said given data may not be checked for data integrity following transfer of said given data to a target storage medium prior to committing the said given data thereto. That is, at least presently, the prospect of data corruption compromising given data during the time window through which the given data journeys, usually via a network, from its source to a target storage medium, is often overlooked. The disclosed method and system, accordingly, propose a scheme directed to detecting corruption amongst data transferred from a source to a target storage medium, and handling said data given the determined integrity of said data.

One example method includes receiving, by a backup appliance, a request concerning a dataset, performing, by the backup appliance, an inquiry to determine if end-to-end encryption is enabled for a volume of a target storage array, receiving, by the backup appliance, confirmation from the storage array that end-to-end encryption is enabled for the volume, and based on the confirmation that end-to-end encryption is enabled for the volume, storing the dataset in the volume without performing encryption, compression, or deduplication, of the dataset prior to storage of the dataset in the volume.

Exemplary security applications and systems are described herein. Such embodiments may be configured to provide backup functionality and ransomware protection for cloud storage systems. The described embodiments may monitor cloud storage systems to detect and classify various events. And the embodiments may perform any number of actions based on classified events, such as transmitting notifications to users, preventing a user or application from accessing the cloud storage system, and/or restoring infected files.

A method, computer program product, and computing system for using a storage path to facilitate disaster recovery are described. A method may comprise receiving a selection of the storage path to facilitate access to a cloud storage device by the cloud computing client. The method may further comprise configuring the storage path to facilitate access to the cloud storage device by the cloud computing client, wherein the storage path is dedicated to the cloud computing client, and wherein a cloud computing site infrastructure is inaccessible to the cloud computing client via the storage path. The method may also comprise configuring a backup routine to generate a backed-up client resource and transmit the backed-up client resource to the cloud storage device via the storage path. The method may additionally comprise transmitting a list of backed-up client resources stored at the cloud storage device.

Embodiments for handling configuration drift in a data storage system having a plurality of storage nodes. A configuration drift manager system defines a golden configuration dataset for the data storage system, obtains a current configuration dataset of each storage node of the plurality of storage nodes, each of the golden and configuration datasets comprising a plurality of sentences defining a node configuration parameter; determines a distance between each sentence of the golden configuration dataset with each other sentence of the current configuration datasets for each of the plurality of storage nodes; ranks each node based on a distance of its sentences with the golden configuration dataset, and triggers an action on a corresponding node based on its respective ranking.