Abstract: Techniques can include: receiving an extended copy request to copy content from a source location to a target location; partitioning the content into segments; and for each of the segments, performing processing including: determining, based at least in part, on a starting logical address of said each segment, one core of a plurality of cores; determining, based on one or more remapping criteria, whether to assign said each segment to the one core for extended copy processing; and responsive to determining to assign said each segment to the one core, performing second processing including: sending said each segment to the one core for extended copy processing; and updating a corresponding core mapping, for said starting logical address of said each segment, to specify to use the one core for extended copy processing of said each segment in connection with other extended copy requests.

Abstract: Techniques can include: configuring stretched volumes to perform asynchronous replication in a first mode using a first replication technique that uses a write tracking cache to track locations that are written between successive replication-related snapshots of respective source volumes of the stretched volumes; performing asynchronous replication for the stretched volumes in accordance with the first replication technique; and monitoring resource consumption of the write tracking cache during asynchronous replication processing using the first replication technique, wherein said monitoring includes: determining that a current amount of write tracking cache consumed exceeds a high watermark threshold; and responsive to determining that the current amount of write tracking cache consumed exceeds a high watermark threshold, selecting, in accordance with criteria, one or more of the stretched volumes for demotion from the first replication mode to a second replication mode that uses a second replication techniq

Abstract: Techniques can include: configuring stretched volumes to perform asynchronous replication in a first mode using a first replication technique that uses a write tracking cache to track locations that are written between successive replication-related snapshots of respective source volumes of the stretched volumes; performing asynchronous replication for the stretched volumes in accordance with the first replication technique; and monitoring resource consumption of the write tracking cache during asynchronous replication processing using the first replication technique, wherein said monitoring includes: determining that a current amount of write tracking cache consumed exceeds a high watermark threshold; and responsive to determining that the current amount of write tracking cache consumed exceeds a high watermark threshold, selecting, in accordance with criteria, one or more of the stretched volumes for demotion from the first replication mode to a second replication mode that uses a second replication techniq

Abstract: Techniques can include: receiving, at a first node, a read I/O directed to a logical address; determining that the first node does not own the logical address; sending over an interconnect a redirect request from the first node to a second node that owns the first logical address; and the second node performing processing including: determining, in accordance with one or more criteria, whether the interconnect is overloaded; responsive to determining that the interconnect is not overloaded, sending a redirect reply over the interconnect to the first node where the redirect reply includes first content stored at the first logical address; and responsive to determining that the interconnect is overloaded, sending the redirect reply over the interconnect to the first node where the redirect reply includes physical location information identifying a first physical storage location or address on non-volatile storage of the first content of the first logical address.

Abstract: A method, computer program product, and computing system for receiving a metadata input/output (IO) request on a first storage node of a storage system. The metadata IO request may be partitioned into a plurality of metadata pages. The plurality of metadata pages may include a plurality of logical metadata pages and a plurality of virtual metadata pages. A family identifier may be obtained for each logical metadata page. The family identifier is a unique identifier assigned to a group of related metadata elements that share data, and is stored in a family identifier locking table. At least one of the plurality of metadata pages may be locked from access by a second storage node using the family identifier. The metadata IO request may be processed on the plurality of metadata pages by loading the at least one of the plurality of metadata pages into a memory of the first storage node.

Abstract: Techniques can include: receiving, at a first node, a read I/O directed to a logical address; determining that the first node does not own the logical address; sending over an interconnect a redirect request from the first node to a second node that owns the first logical address; and the second node performing processing including: determining, in accordance with one or more criteria, whether the interconnect is overloaded; responsive to determining that the interconnect is not overloaded, sending a redirect reply over the interconnect to the first node where the redirect reply includes first content stored at the first logical address; and responsive to determining that the interconnect is overloaded, sending the redirect reply over the interconnect to the first node where the redirect reply includes physical location information identifying a first physical storage location or address on non-volatile storage of the first content of the first logical address.

Abstract: Techniques can include: configuring stretched volumes for asynchronous replication; specifying replication settings denoting selected replication service levels of asynchronous replication optimizations for the stretched volumes; performing asynchronous replication for the stretched volumes based on the replication settings; monitoring a current amount denoting an amount of a resource that is free and available for use; and responsive to determining that the current amount is below a minimum, performing a corrective action to increase the current amount, wherein the corrective action includes: changing a replication setting for a stretched volume from a first replication service level to a second replication service level, wherein the second replication service level is expected to consume less of the resource than the first replication service level when performing asynchronous replication for the stretched volume.

Abstract: A method, computer program product, and computing system for receiving a metadata input/output (IO) request on a first storage node of a storage system. The metadata IO request may be partitioned into a plurality of metadata pages. The plurality of metadata pages may include a plurality of logical metadata pages and a plurality of virtual metadata pages. A family identifier may be obtained for each logical metadata page. The family identifier is a unique identifier assigned to a group of related metadata elements that share data, and is stored in a family identifier locking table. At least one of the plurality of metadata pages may be locked from access by a second storage node using the family identifier. The metadata IO request may be processed on the plurality of metadata pages by loading the at least one of the plurality of metadata pages into a memory of the first storage node.

Abstract: In at least one embodiment, processing can include: receiving write operations; persistently recording, in a write cache or log, the write operations using page descriptors (PDESCs) of a PDESC pool and page buffers (PBs) of a PB pool; selecting, in accordance with criteria, write data pages stored in the PB pool for demotion to a physical large block (PLB) pool included in backend non-volatile storage, wherein each write data page selected denotes content written by a corresponding one of the write operations; responsive to the selecting, persistently storing the write data pages of the PB pool in the PLB pool; and updating PDESCs associated with the write data pages to reference corresponding storage locations in the PLB pool rather than in the PB pool.

Abstract: A method, computer program product, and computer system for receiving an XCopy command is provided. The XCopy command may be in the form of an IO operation. The IO operation may be a subextent block operation. A source range and a destination range of the XCopy command may be determined to be aligned within an alignment boundary. The Xcopy command may be determined to be smaller than a predetermined size. In response to determining the source range and destination range of the XCopy command are aligned within the alignment boundary and the XCopy command is smaller than a predetermined size, the XCopy command may be processed. The receiving of the XCopy command may be recorded in a log.

Abstract: A method, computer program product, and computer system for receiving an XCopy command is provided. The XCopy command may be in the form of an IO operation. The IO operation may be a subextent block operation. A source range and a destination range of the XCopy command may be determined to be aligned within an alignment boundary. The Xcopy command may be determined to be smaller than a predetermined size. In response to determining the source range and destination range of the XCopy command are aligned within the alignment boundary and the XCopy command is smaller than a predetermined size, the XCopy command may be processed. The receiving of the XCopy command may be recorded in a log.