Abstract: Techniques for creating identical snapshots can include: performing synchronous replication between a first storage object of a first system and a second storage object of a second system; enabling change tracking for the first storage object that records in a log which portions of the first storage object are written or modified; responsive to enabling change tracking, creating a snapshot S2 of the second storage object of the second system; responsive to creating the snapshot S2 of the second storage object; creating a snapshot S1 of the first storage object of the first system; responsive to creating the snapshot S1 of the first storage object, disabling change tracking for the first storage object; and copying written or modified content of the first storage object as identified in the log to the snapshot S2 of the second storage object of the second system.

Abstract: A data path connection can be established between a target of a remote source system and an initiator of a local destination system. A storage object of the remote source system exposed over such a data path connection can be mapped to a local storage object name of the local destination system. Such a remote storage object of the remote source system can be accessed as a local storage object of the local destination system using the local storage object name. Within the destination system, the local storage object name of the destination system can be used as a proxy to access the remote storage object of the remote source system. Accessing the remote storage object from the destination system can be used in several data mobility use cases, including, but not limited to, offloaded data copy across arrays, snapshot mobility and backup use-cases.

Abstract: A data path connection can be established between a target of a remote source system and an initiator of a local destination system. A storage object of the remote source system exposed over such a data path connection can be mapped to a local storage object name of the local destination system. Such a remote storage object of the remote source system can be accessed as a local storage object of the local destination system using the local storage object name. Within the destination system, the local storage object name of the destination system can be used as a proxy to access the remote storage object of the remote source system. Accessing the remote storage object from the destination system can be used in several data mobility use cases, including, but not limited to, offloaded data copy across arrays, snapshot mobility and backup use-cases.

Abstract: Techniques for creating and using snapshots may include: receiving a request to create a new snapshot of a source object; determining whether a first generation identifier associated with the source object matches a second generation identifier associated with a base snapshot of the source object; determining whether the source object has been modified since the base snapshot was created; and responsive to determining the first generation identifier matches the second generation identifier and also determining that the source object has not been modified since the base snapshot was created, associating the new snapshot with the base snapshot thereby indicating that the new snapshot and the base snapshot have matching content and denote a same point in time copy of the source object.

Abstract: A method, computer program product, and computer system for triggering, by a computing device, a synchronization activity on a storage object. A request may be executed for a copy operation resulting from the synchronization activity to copy the storage object from a source to a destination when a current number of concurrent copy operations is below a maximum number of copy operations. The request for the copy operation resulting from the synchronization activity to copy the storage object from the source to the destination may be placed in a queue when the current number of concurrent copy operations is at least at the maximum number of copy operations. One or more attributes of the request in the queue may be identified. The request for the copy operation may be executed according to a replication policy based upon, at least in part, the one or more attributes of the request in the queue.

Abstract: A method, computer program product, and computing system for receiving a plurality of discrete write requests on a first computing device until the end of a consolidation window; combining the plurality of discrete write requests received into a consolidated write request; and transmitting the consolidated write request to a second computing device.

Abstract: A method, computer program product, and computing system for receiving a plurality of discrete write requests on a first computing device until the end of a consolidation window; combining the plurality of discrete write requests received into a consolidated write request; and transmitting the consolidated write request to a second computing device.

Abstract: Techniques for creating and using snapshots may include: receiving a request to create a new snapshot of a source object; determining whether a first generation identifier associated with the source object matches a second generation identifier associated with a base snapshot of the source object; determining whether the source object has been modified since the base snapshot was created; and responsive to determining the first generation identifier matches the second generation identifier and also determining that the source object has not been modified since the base snapshot was created, associating the new snapshot with the base snapshot thereby indicating that the new snapshot and the base snapshot have matching content and denote a same point in time copy of the source object.

Abstract: A method, computer program product, and computer system for receiving, at a computing device, a write request from a host, wherein a first portion of a process may receive the write request. A callback and context may be set in the write request by the first portion of the process. The write request may be passed to a second portion of the process. The first process may be provided with the context. The first process may use the context to replicate the write request data to a destination.

Abstract: A method, computer program product, and computer system for receiving, at a computing device, a write request from a host, wherein a first portion of a process may receive the write request. A callback and context may be set in the write request by the first portion of the process. The write request may be passed to a second portion of the process. The first process may be provided with the context. The first process may use the context to replicate the write request data to a destination.

Abstract: A method, computer program product, and computer system for triggering, by a computing device, a synchronization activity on a storage object. A request may be executed for a copy operation resulting from the synchronization activity to copy the storage object from a source to a destination when a current number of concurrent copy operations is below a maximum number of copy operations. The request for the copy operation resulting from the synchronization activity to copy the storage object from the source to the destination may be placed in a queue when the current number of concurrent copy operations is at least at the maximum number of copy operations. One or more attributes of the request in the queue may be identified. The request for the copy operation may be executed according to a replication policy based upon, at least in part, the one or more attributes of the request in the queue.

Abstract: A method is used in managing snapshots of data. Identity information of a snapshot of data is updated. The snapshot represents a state of the data at a particular prior point in time. A new snapshot of the data is created. The new snapshot is created based on the identity information of the snapshot.

Abstract: A method, computer program product, and computing system for defining a first virtual object, wherein the first virtual object includes a first ready state indicator. At least a second virtual object is defined, wherein the at least a second virtual object includes at least a second ready state indicator. The first virtual object and the at least a second virtual object are grouped within a group virtual object.

Abstract: A storage system uses a block-level file system to manage physical storage of data blocks of logical units, the file system being mounted on an owning one of a set of storage processors. The storage processors redirect received storage requests to the owning storage processor, and periodically the amount of redirection is evaluated. If the amount of redirection is higher than a threshold, then the file system is dismounted at the owning storage processor and mounted at another storage processor to reduce the amount of redirection.

Abstract: A method, computer program product, and computing system for identifying a target storage device upon which a plurality of logical storage devices are to be defined. The target storage device includes a plurality of physical storage blocks. At least a first logical storage device and a second logical storage device are defined for mapping within the target storage device. Each of the first and second logical storage devices includes a plurality of logical storage slices. At least a portion of the logical storage slices for each of the first and second logical storage devices are non-sequentially mapped to at least a portion of the plurality of physical storage blocks included within the target storage device to generate an interlaced target storage device.

Abstract: In a data storage system, a fixture communication channel is created for communications between a fixture and another component, where the fixture is a component of a device driver that provides extended input/output functionality with respect to one or more storage devices. A handle identifies the fixture communication channel, and callbacks are registered with a driver handler and reference callback functions of the fixture. Fixture communication messages each include the handle and a message-specific operation code for an operation to be performed by the fixture, and each is conveyed by (1) issuing a fixture-control input/output control command to the handler that includes the handle and message-specific operation code, and (2) at the handler, using the handle and message-specific operation code to select a callback and invoke a corresponding callback function of the fixture.

Abstract: This invention enables managing data consistency between different data volumes by managing I/O traffic in a data storage environment. A methodology for managing data consistency, in accordance with the principles of the invention, comprises the steps of arresting processing of I/O traffic during an administrative operation, queuing any I/O that follow the arresting step in a queuing data structure and processing each queued I/O until the I/O processing is completed. Certain implementations of the invention include a system, a computer program product, or an apparatus, wherein each embodiment is configured for carrying out the steps involved in the methodology.