Abstract: For a source device with an activated snapshot, time series-based prediction of source device write IO operations is implemented, on a per-extent basis, to predict a subset of the source device extents that are likely to be hot (receive write IO operations) during an upcoming time window. Snapshot tracks corresponding to tracks of the predicted hot extents are pre-deduplicated, to accelerate write IO operations on the source device. In instances where the time series-based prediction correctly predicts write IO operations on tracks of an extent, and the tracks of the extent of the source device are pre-deduplicated on the snapshot, it is possible to implement the write IO operations as a redirect on write operation, without first replicating the original track of source data for use by the snapshot. Write IO operations on tracks that are not pre-deduplicated are implemented as copy on write operations.

Abstract: Metadata page prefetch processing for incoming IO operations is provided to increase storage system performance by reducing the frequency of metadata page miss events during IO processing. When an IO is received at a storage system, the IO is placed in an IO queue to be scheduled for processing by an IO processing thread. A metadata page prefetch thread reads the LBA address of the IO and determines whether all of the metadata page(s) that will be needed by the IO processing thread are contained in IO thread metadata resources. In response to a determination that one or more of the required metadata pages are not contained in IO thread metadata resources, the metadata page prefetch thread instructs a MDP thread to move the required metadata page(s) from metadata storage to IO thread metadata resources. The IO processing thread then implements the IO operation using the prefetched metadata.

Abstract: Metadata page prefetch processing for incoming IO operations is provided to increase storage system performance by reducing the frequency of metadata page miss events during IO processing. When an IO is received at a storage system, the IO is placed in an IO queue to be scheduled for processing by an IO processing thread. A metadata page prefetch thread reads the LBA address of the IO and determines whether all of the metadata page(s) that will be needed by the IO processing thread are contained in IO thread metadata resources. In response to a determination that one or more of the required metadata pages are not contained in IO thread metadata resources, the metadata page prefetch thread instructs a MDP thread to move the required metadata page(s) from metadata storage to IO thread metadata resources. The IO processing thread then implements the IO operation using the prefetched metadata.

Abstract: Host IO write operations on a given storage group are grouped into cycles of a write destage pipeline for the storage group. Host writes are collected during a capture cycle, while host writes from a previous capture cycle are analyzed and destaged during an apply cycle. After the previous apply cycle has completed, a cycle switch occurs and the current capture cycle becomes the new apply cycle. Anomaly detection is implemented before any IO write operations are destaged during the apply cycle, and if an anomaly is detected the write destage is stopped. The entire apply cycle is either destaged to disk, or is discarded, depending on whether the anomaly is confirmed. By maintaining the order of writes across different cycles, which act as consistency points, it is possible to implement ransomware protection in real time on host write operations, while using ordered write destage to maintain data consistency.

Abstract: In asynchronous remote replication, write IOs are accumulated in capture cycles and sent to a remote storage system in transmit cycles. In order to cause metadata cache hits at the remote storage system, write IO data and associated metadata hints such as logical block addresses being updated are sent in successive cycles. The metadata hints, which are received at the remote storage system before the corresponding write IO data, are used to prefetch metadata associated with the logical block addresses being updated to replicate the write IO.

Abstract: Ransomware activity detection and data protection is implemented by a remote R2 storage array on an asynchronous remote data replication facility, on which data from a primary R1 storage array is replicated to the remote storage array. Write operations on storage volumes in a remote data replication group are collected in a capture cycle on the primary storage array, along with IO pattern metadata describing both read and write operations on the storage volumes. At the end of the capture cycle, the update and metadata is transmitted to the remote storage array. The remote storage array receives the update and metadata and temporarily stores the update prior to applying it to its copy of the storage volumes. Ransomware anomaly detection is implemented using the update and metadata, and if ransomware activity is detected, the data on the remote R2 storage array is protected, and the update is not applied.

Abstract: Selective packing of small block write operations is implemented prior to compression, to improve compression efficiency and hence reduce bandwidth requirements of a Remote Data Replication (RDR) facility. Compression characteristics of write IO operations are forecast, and write IO operations with similar forecast compression characteristics are pooled. Write IO operations are also grouped according to extent, device, and storage group. Write operations from a given compression pool are then preferentially selected from the extent-level grouping, next from the device-level grouping, and then from the SG-level grouping, to create an IO package. The IO package is then compressed and transmitted on the RDR facility. By creating an IO package prior to compression, it is possible to achieve greater compression than would be possible if each individual write IO operation were to be individually compressed to thereby reduce network bandwidth of the RDR facility.

Abstract: One or more aspects of the present disclosure relate to maximizing data migration bandwidth. In embodiments, one or more network characteristics corresponding to network communications between a first storage array and a second storage array is determined. Further, one or more network metrics of at least one acknowledgment communication from the second storage array to the first storage array can be analyzed. Additionally, one or more input/output (IO) messages are transmitted from the first storage array to the local storage array during an acknowledgment period corresponding to receipt of the at least one acknowledgment communication from the second storage array by the first storage array based on the one or more network metrics.

Abstract: A remote data replication facility includes a primary storage array and a backup storage array, on which tracks of data are replicated from the primary storage array to the backup storage array as they are received by the primary storage array. Remote data verification is implemented on the remote data replication facility by comparing track fingerprints, track temporal write metadata, and track spatial write metadata, for a given track on the primary storage array, with corresponding track fingerprints, track temporal write metadata, and track spatial write metadata, for the given track on the backup storage array. If any difference is determined in the combination of track fingerprints, track temporal write metadata, track spatial write metadata, for a given track, the integrity of the data at the backup storage array is not verified for the track.

Abstract: A method for reconstituting a data storage unit of a volume, the method comprising: initializing a reconstituted data storage unit that includes a plurality of portions; identifying a first type-1 data structure that corresponds to the data storage unit and a first snapshot of the volume, the first snapshot being created at a first point-in-time, the first type-1 data structure including a first bitmap, the first bitmap including a first plurality of bits, each of the first plurality of bits corresponding to a different portion of the data storage unit; retrieving, from the first snapshot, one or more portions of the data storage unit that correspond to bits in the first bitmap that are set, and storing the portions that are retrieved from the first snapshot in the reconstituted data storage unit; and returning the reconstituted data storage unit.

Abstract: Host IO write operations on a given storage group are grouped into cycles of a write destage pipeline for the storage group. Host writes are collected during a capture cycle, while host writes from a previous capture cycle are analyzed and destaged during an apply cycle. After the previous apply cycle has completed, a cycle switch occurs and the current capture cycle becomes the new apply cycle. Anomaly detection is implemented before any IO write operations are destaged during the apply cycle, and if an anomaly is detected the write destage is stopped. The entire apply cycle is either destaged to disk, or is discarded, depending on whether the anomaly is confirmed. By maintaining the order of writes across different cycles, which act as consistency points, it is possible to implement ransomware protection in real time on host write operations, while using ordered write destage to maintain data consistency.

Abstract: Ransomware activity detection and data protection is implemented by a remote R2 storage array on an asynchronous remote data replication facility, on which data from a primary R1 storage array is replicated to the remote storage array. Write operations on storage volumes in a remote data replication group are collected in a capture cycle on the primary storage array, along with IO pattern metadata describing both read and write operations on the storage volumes. At the end of the capture cycle, the update and metadata is transmitted to the remote storage array. The remote storage array receives the update and metadata and temporarily stores the update prior to applying it to its copy of the storage volumes. Ransomware anomaly detection is implemented using the update and metadata, and if ransomware activity is detected, the data on the remote R2 storage array is protected, and the update is not applied.

Abstract: A storage system is configured to accept subsequent versions of write data on a given track to multiple respective slots of shared global memory. A track index table presents metadata at the track level, and can hold up to N slots of data. All slots of shared global memory holding data owed to the source volume and to snapshots of the source volume are bound to the track in the track index table. Each time a write occurs on a track, the track index table is used to determine when a write pending slot for the track is owed to a snapshot copy of the storage volume. When a write pending slot contains data that is owed to a snapshot copy of the source volume, a new slot is allocated to the write IO and bound to the track in the track index table.

Abstract: Targetless snapshots of a storage object are characterized in terms of likelihood of access using time-series analysis. Metadata of replication data structures of individual targetless snapshots is maintained in either uncompressed or compressed form based on the characterization of the targetless snapshot. Metadata is compressed at the page level, with same-pages of all replication data structures of cold snapshots of a storage object being compressed together. Compressed pages of targetless snapshot metadata are maintained of storage devices selected based on storage device performance and the time-series characterization of the targetless snapshot.

Abstract: A storage system is configured to accept subsequent versions of write data on a given track to multiple respective slots of shared global memory. A track index table presents metadata at the track level, and can hold up to N slots of data. All slots of shared global memory holding data owed to the source volume and to snapshots of the source volume are bound to the track in the track index table. Each time a write occurs on a track, the track index table is used to determine when a write pending slot for the track is owed to a snapshot copy of the storage volume. When a write pending slot contains data that is owed to a snapshot copy of the source volume, a new slot is allocated to the write IO and bound to the track in the track index table.

Abstract: Direct Image Lookup (DIL) metadata is used to perform differential operation for snapshots and linked targets. Each snapshot contains metadata to store “images” to perform direct lookup of user data for any part of any snapshot in the system. Metadata pages of DIL image data represent sets of tracks of data. Metadata pages of subsequent snapshots for the same sets of tracks are compared, and where there are no changes to a given metadata page for a given set of tracks between subsequent snapshot copies, the differential process is not run on the tracks associated with the metadata page. If a given metadata page associated with a set of tracks has changed between subsequent snapshots, the differential process is used to identify which tracks in the subsequent snapshot contain different data than the corresponding tracks of the previous snapshot. Similar differential processing also is implemented for relinked target devices.

Abstract: Targetless snapshots of a storage object are characterized in terms of likelihood of access using time-series analysis. Metadata of replication data structures of individual targetless snapshots is maintained in either uncompressed or compressed form based on the characterization of the targetless snapshot. Metadata is compressed at the page level, with same-pages of all replication data structures of cold snapshots of a storage object being compressed together. Compressed pages of targetless snapshot metadata are maintained of storage devices selected based on storage device performance and the time-series characterization of the targetless snapshot.

Abstract: A first direct index lookup table represents the current state of a storage object using entries with references corresponding to tracks of the storage object. A second direct index lookup table represents a first targetless snapshot of the storage object. A virtual replication data pointer table maps the entries of both the first direct index lookup table and the entries of the second direct index lookup table to backend storage via a system replication data pointer table. Updates to the storage object are represented using new entries in the first direct index lookup table and the system replication data pointer table. Movement of a track that is represented in multiple targetless snapshots that are represented by multiple direct index lookup tables is represented by updating the corresponding virtual replication data pointer table and system replication data pointer table rather than updating each of the direct index lookup tables.

Abstract: Aspects of the present disclosure relate to improving response rates of input/output (IO) requests targeting undefined virtual storage devices. In embodiments, an (IO request can be received by a storage array. Additionally, a determination of whether the IO request targets an undefined target track can be made. Further, source data related to the IO request can be located. For instance, a direct image lookup (DIL) can be performed to locate the source data. Also, a storage-related operation on the undefined target track can be performed using instructions provided by the IO request, such as updating a version of the undefined track. Further, a storage resource allocation for the undefined target track can be destaged.

Abstract: Aspects of the present disclosure relate to improving response rates of input/output (IO) requests targeting undefined virtual storage devices. In embodiments, an (IO request can be received by a storage array. Additionally, a determination of whether the IO request targets an undefined target track can be made. Further, source data related to the IO request can be located. For instance, a direct image lookup (DIL) can be performed to locate the source data. Also, a storage-related operation on the undefined target track can be performed using instructions provided by the IO request, such as updating a version of the undefined track. Further, a storage resource allocation for the undefined target track can be destaged.