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.

Abstract: A target-less point in time image (snapshot) of a storage volume is allowed to be built after activation, by enabling the snapshot data to be modified to create a crash-consistent replica of the source data after the snapshot has been activated. The data of the snapshot remains immutable from a user standpoint, but the snapshot is able to be quickly activated before all of the data of the snapshot has been included in the snapshot, to thus reduce an amount of time IO operations on the source volume are quiesced. A first snapshot of a storage volume is created on a primary storage system and a corresponding second snapshot of the storage volume is activated on a backup storage system before all the data of the first snapshot is received at the backup storage system. Entries of the activated second snapshot are then changed to point to correct back-end allocations.

Abstract: A target-less point in time image (snapshot) of a storage volume is allowed to be built after activation, by enabling the snapshot data to be modified to create a crash-consistent replica of the source data after the snapshot has been activated. The data of the snapshot remains immutable from a user standpoint, but the snapshot is able to be quickly activated before all of the data of the snapshot has been included in the snapshot, to thus reduce an amount of time IO operations on the source volume are quiesced. A first snapshot of a storage volume is created on a primary storage system and a corresponding second snapshot of the storage volume is activated on a backup storage system before all the data of the first snapshot is received at the backup storage system. Entries of the activated second snapshot are then changed to point to correct back-end allocations.

Abstract: Storage objects and targetless snaps of the storage objects are represented using a system replication data pointer table (SRT), direct index lookup (DIL) tables, and virtual replication data pointer tables (VRTs). The SRT is a system level track-based data structure that stores metadata indicative of the actual (physical layer) allocations for all targetless snapshots in a storage array. The size of the SRT in terms of total entries corresponds to the overall storage capacity of the managed drives of the storage array. Each utilized entry of the SRT includes backend metadata with a pointer to a managed drive and metadata that identifies the associated storage object and track via the VRTs and DIL tables. SRT metadata is created and discarded as backend allocations are utilized and freed so the SRT is a dynamic data structure that can efficiently adjust its size and corresponding memory requirements.

Abstract: A snapshot for use in a cascaded snapshot environment includes a device level source sequence number and a Direct Image Lookup (DIL) data structure. The device level source sequence number indicates the level of the snapshot in the cascade, and the snapshot DIL indicates the location of the data within the snapshot cascade. A target device for use in the cascaded snapshot environment includes a device level target sequence number, a track level sequence data structure, and a DIL. When the target device is linked to a snapshot, the device level target sequence number is incremented, which invalidates all tracks of the target device. The snapshot DIL is copied to the target device, but a define process is not run on the target device such that the tracks of the target device remain undefined. IO operations use the device level target sequence number to identify data on the target device.

Abstract: A thin device (TDev) is tagged to identify the TDev as being used to access snapshot data on the storage system. If a snapshot is to be shipped to a cloud repository, the tagged TDev is linked to the snapshot, and mounted to a cloud tethering subsystem. When the tagged TDev is linked to the cloud tethering subsystem, the snapshot subsystem reads the thin device tag and, if the thin device is tagged, selectively does not execute a define process on the tagged thin device. By not executing the define process, the tracks of the thin device do not contain metadata identifying the location of the snapshot data on the storage system. Writes to source do not require a private copy of the old data for the snapshot, even if the snapshot is created in a different storage resource pool than the source data volume.

Abstract: A snapshot for use in a cascaded snapshot environment includes a device level source sequence number and a Direct Image Lookup (DIL) data structure. The device level source sequence number indicates the level of the snapshot in the cascade, and the snapshot DIL indicates the location of the data within the snapshot cascade. A target device for use in the cascaded snapshot environment includes a device level target sequence number, a track level sequence data structure, and a DIL. When the target device is linked to a snapshot, the device level target sequence number is incremented, which invalidates all tracks of the target device. The snapshot DIL is copied to the target device, but a define process is not run on the target device such that the tracks of the target device remain undefined. IO operations use the device level target sequence number to identify data on the target device.

Abstract: A remote data facility includes a primary storage volume on a first storage system mirrored to a backup storage volume on a second storage system. A nocopy clone of a production volume is added to the primary storage volume. A define process is used to cause the tracks of the nocopy clone to point to backend allocations of tracks of memory of the production volume. As tracks of the nocopy clone are defined, corresponding flags are marked as invalid to cause data associated with the tracks to be replicated across the remote data facility to the backup storage volume. Incremental clones can be added to the primary storage volume, defined, and replicated on the remote data facility using the same process. Nocopy clones and target-less nocopy snapshots of the backup storage volume are used to restore the production volume using failover/failback mechanisms of the remote data facility.

Abstract: A thin device (TDev) is tagged to identify the TDev as being used to access snapshot data on the storage system. If a snapshot is to be shipped to a cloud repository, the tagged TDev is linked to the snapshot, and mounted to a cloud tethering subsystem. When the tagged TDev is linked to the cloud tethering subsystem, the snapshot subsystem reads the thin device tag and, if the thin device is tagged, selectively does not execute a define process on the tagged thin device. By not executing the define process, the tracks of the thin device do not contain metadata identifying the location of the snapshot data on the storage system. Writes to source do not require a private copy of the old data for the snapshot, even if the snapshot is created in a different storage resource pool than the source data volume.

Abstract: A no-copy clone of a logical storage unit is created. A define process is initiated for defining a target logical storage unit as the clone before activation of the target logical storage unit. By initiating the define process before activating the logical storage unit, there is a greater likelihood that, when a write operation is received for a data portion on the source logical storage unit or target logical storage unit after activation of the target LSU, the data portion will already be defined and not need to be defined when performing the write operation. When a write operation is received at the source logical storage unit, if the target logical storage unit is not active yet, the data of the write operation may be written to an allocated physical location for the data portion shared between the source and target logical storage units without updating any clone metadata.

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: Storage objects and targetless snaps of the storage objects are represented using a system replication data pointer table (SRT), direct index lookup (DIL) tables, and virtual replication data pointer tables (VRTs). The SRT is a system level track-based data structure that stores metadata indicative of the actual (physical layer) allocations for all targetless snapshots in a storage array. The size of the SRT in terms of total entries corresponds to the overall storage capacity of the managed drives of the storage array. Each utilized entry of the SRT includes backend metadata with a pointer to a managed drive and metadata that identifies the associated storage object and track via the VRTs and DIL tables. SRT metadata is created and discarded as backend allocations are utilized and freed so the SRT is a dynamic data structure that can efficiently adjust its size and corresponding memory requirements.

Abstract: A remote data facility includes a primary storage volume on a first storage system mirrored to a backup storage volume on a second storage system. A nocopy clone of a production volume is added to the primary storage volume. A define process is used to cause the tracks of the nocopy clone to point to backend allocations of tracks of memory of the production volume. As tracks of the nocopy clone are defined, corresponding flags are marked as invalid to cause data associated with the tracks to be replicated across the remote data facility to the backup storage volume. Incremental clones can be added to the primary storage volume, defined, and replicated on the remote data facility using the same process. Nocopy clones and target-less nocopy snapshots of the backup storage volume are used to restore the production volume using failover/failback mechanisms of the remote data facility.

Abstract: A no-copy clone of a logical storage unit is created. A define process is initiated for defining a target logical storage unit as the clone before activation of the target logical storage unit. By initiating the define process before activating the logical storage unit, there is a greater likelihood that, when a write operation is received for a data portion on the source logical storage unit or target logical storage unit after activation of the target LSU, the data portion will already be defined and not need to be defined when performing the write operation. When a write operation is received at the source logical storage unit, if the target logical storage unit is not active yet, the data of the write operation may be written to an allocated physical location for the data portion shared between the source and target logical storage units without updating any clone metadata.