A file directory tree structure of a selected storage snapshot is dynamically divided into different portions. A plurality of the different file directory tree structure portions are analyzed in parallel to identify any changes of the selected storage snapshot from a previous storage snapshot. To analyze each of the plurality of the different file directory tree structure portions, a processor is further configured to traverse and compare a corresponding file directory tree structure portion of the selected storage snapshot with a corresponding portion of a file directory tree structure of the previous storage snapshot while at least another one of the plurality of the different file directory tree structure portions of the selected storage snapshot is being analyzed in parallel.

Generally described, one or more aspects of the present application correspond to techniques for managing snapshots in a partially encrypted state and providing access to partially encrypted snapshots. These snapshot management techniques allow a snapshot that is being encrypted to be accessed prior to the encryption being completed. Such a snapshot may have some blocks that have been encrypted, and other blocks that have not yet been encrypted. In order to provide access to such a snapshot in a partially encrypted state, a system may allow the encryption status of the blocks in the snapshot to be checked at the block level instead of at the snapshot level (or at some other intermediary level therebetween), according to some embodiments. By doing so, the system can reduce the delays resulting from snapshots that are locked during the encryption process.

A file system and a related method are presented. The file system includes an object storage configured to store file data for one or more files and a plurality of namespace entries corresponding to file data and/or metadata of the one or more files as one or more objects. Each namespace entry of the plurality of namespace entries includes an operation type conducted on the file data and/or metadata captured in a particular snapshot and a version number corresponding to the particular snapshot. The file system further includes an indexing system configured to generate the plurality of namespace entries; store the plurality of namespace entries as one or more objects in the object storage; and identify, in response to a search query, one or more files for retrieval from the object storage based on a list of the plurality of namespace entries sorted on the version numbers.

A system and method for data discovery. A method includes performing a scan of a plurality of snapshots, each snapshot corresponding to a respective disk of a plurality of disks; identifying a plurality of data store files in the plurality of disks based on file metadata found during the scan; and detecting at least one data store based on the identified plurality of data store files, wherein each of the at least one data store is in a disk of the plurality of disks including one of the plurality of data store files.

Dynamic snapshot scheduling techniques are provided using storage system metrics. One method comprises obtaining a schedule for generating snapshots of a portion of a storage system; automatically adjusting snapshot generation parameters in the schedule based on: (i) a current storage pool usage metric, (ii) an input/output metric of at least one storage resource in the portion of the storage system, (iii) a measure of snapshots in a destroying state, and/or (iv) a measure of a number of created snapshots; and initiating a generation of a snapshot of the storage system portion in accordance with the adjusted schedule. A snapshot generation frequency may be increased in response to an increase of: the current storage pool usage metric, the number of snapshots in the destroying state, and/or the number of created snapshots. A snapshot generation frequency may be decreased in response to an increase of the I/O metric of the at least one storage resource.

Embodiments of the present disclosure relate to a method, an electronic device, and a computer program product for identifying a memory snapshot. The method includes determining, based on operation-related historical information for a plurality of memory snapshots, a probability that the plurality of memory snapshots are operated within a first time period. The method further includes, if the determined probability is less than a threshold associated with a duration of the first time period, identifying the plurality of memory snapshots for deletion. By use of the method, memory snapshots with a low probability of being operated in a future period of time can be identified, so that such memory snapshots are deleted to reduce usage of storage resources.

Systems as described herein may include generating an aggregated service status report for a real-time service delivery platform. A plurality of services running in a service domain may be determined. A request for a status of system behavior corresponding to a particular service may be received. Service connection details of the particular service may be discovered and metric data of real-time data movement may be tracked. Real-time snapshot aggregation of the particular service may be provided. In a variety of embodiments, a real-time system behavior report for the service across availability zones may be presented.

Creating point-in-time versions of files for applications at a storage system includes maintaining at the storage system a data structure correlating each of a plurality of applications with files for each of the applications and correlating each of the files with portions of the data storage system, using the data structure to determine specific files for a particular one of the applications for which a point-in-time version is being created, using the data structure to determine specific portions of the storage system corresponding to the specific files, suspending writes to the specific portions, completing previous writes to the specific portions following suspending writes, and performing a snapshot of the specific files following completing previous writes. The portions of the data storage may be extents. A host may provide information to the storage system to correlate applications with files and to correlate files with portions of the data storage system.

A copy data management system for a modern application includes a modern application module and a copy data management module. The modern application module includes a service unit, an object storage gateway, a production object storage, and a database. The service unit is configured to generate a large object, a small object, and service metadata. The object storage gateway is configured to write and read the large object and the small object in the production object storage, merge small objects into a large object, and generate object metadata. The database is configured to store the service metadata and the object metadata. The copy data management module includes a metadata processing unit and a disaster recovery object storage. The metadata processing unit is configured to back up the database. The object storage gateway is also configured to back up the production object storage to the disaster recovery object storage.

The described embodiments set forth techniques for preserving clone relationships between files at a computing device. In particular, the techniques involve identifying clone relationships between files in conjunction with performing operations on the files where it can be beneficial to preserve the clone relationships. The operations can include, for example, preserving clone relationships between files that are being copied from a source storage device (that supports file cloning) to a destination storage device that supports file cloning. Additionally, the operations can include preserving clone relationships when backing up and restoring files between a source storage device (that supports file cloning) and a destination storage device that does not support file cloning. In this manner, the various benefits afforded by the clone relationships between files can be retained even as the files are propagated to destination storage devices that may or may not support file cloning.