Abstract: Creating a modifiable cloned image of a dataset, including: generating, based on a dataset stored within a source data repository, a tracking copy of replica data on a target data repository; generating, after receiving an indication to begin accepting modifications to the tracking copy of the replica data, a cloned image of the dataset that is modifiable without modifying the tracking copy of the replica data; and responsive to a storage operation directed to the target data repository, modifying the cloned image of the dataset without modifying the tracking copy of the replica data.

Abstract: Modifying a clone image of a dataset, including: generating, based on metadata describing one or more updates to a dataset, a tracking copy of replica data on a target data repository; generating, after receiving an indication to begin accepting modifications to the tracking copy of the replica data, a cloned image of the dataset that is modifiable without modifying the tracking copy of the replica data; and responsive to a storage operation directed to the target data repository, modifying the cloned image of the dataset without modifying the tracking copy of the replica data.

Abstract: Migrating similar data to a single data reduction pool, including: determining that storage space consumption may be reduced by migrating similar data between a first storage system and a second storage system; and initiating a migration of the similar data, including selecting a migration direction from one of either migrating the first data from the first storage system to the second storage system and migrating the second data from the second storage system to the first storage system.

Abstract: Storage efficiency driven migration includes: determining a level of similarity between first data stored on a first storage system and second data stored on a second storage system; determining, in dependence upon the level of similarity, that an expected amount of storage space reduction from migrating similar data exceeds a threshold level; and responsive to determining that the expected amount of storage space reduction exceeds the threshold level, initiating a migration of one or more portions of the first data from the first storage system to the second storage system.

Abstract: In a particular embodiment, a storage service agent on an edge device is configured to access a particular set of storage system application programming interfaces (APIs) of at least one enterprise storage system, where the storage service agent communicatively coupled to a cloud-based storage service. The storage service agent invokes one or more storage system APIs of the particular set of storage system APIs in response to a control message from the cloud-based storage service.

Abstract: Non-disruptively moving a storage fleet control plane, including deploying, on an edge device, one or more agents that are managed by a control plane residing in a cloud computing environment; mediating one or more API requests, generated by the control plane, directed to the one or more agents on the edge device; and migrating, in response to a first condition, the control plane to the edge device.

Abstract: Modifying a clone image of a dataset, including: generating, based on metadata describing one or more updates to a dataset, a tracking copy of replica data on a target data repository; generating, after receiving an indication to begin accepting modifications to the tracking copy of the replica data, a cloned image of the dataset that is modifiable without modifying the tracking copy of the replica data; and responsive to a storage operation directed to the target data repository, modifying the cloned image of the dataset without modifying the tracking copy of the replica data.

Abstract: Cloning a tracking copy of replica data, including receiving, at a target data repository from a source data repository, metadata describing one or more updates to a dataset stored within the source data repository; generating, based on the metadata describing the one or more updates to the dataset, a tracking copy of replica data on the target data repository; and generating, based on the tracking copy, a cloned image of the dataset that is modifiable without modifying the tracking copy of the replica data.

Abstract: Managing host definitions across a plurality of storage systems, including: creating, on a first storage system, a host definition describing a host that accesses a dataset that is replicated across a plurality of storage systems; determining whether a second storage system that the dataset is replicated across includes a definition of the host; responsive to determining that the second storage system does not include a definition of the host, copying the host definition created on the first storage system to the second storage system; responsive to determining that the second storage system does include a definition of the host: linking the host definition created on the first storage system to the definition of the host on the second storage system or retaining the definition of the host on the second storage system.

Abstract: In an embodiment, in response to receiving from a client computer a client request to connect to a server: processing the client request in a network protection device including applying one or more translations and one or more security checks, generating a server acknowledgment to the client computer as if the server acknowledged receiving the client request from the client computer, processing the server acknowledgement in the network protection device including applying one or more translations and one or more security checks and sending the server acknowledgment to the client computer; in response to receiving a client acknowledgment of receiving the server acknowledgment, determining that a first path between the client computer and the network protection device is operational; generating a server request to the server; processing the server request in the network protection device, determining that a second path between the network protection device and the server is operational.

Abstract: In an embodiment, in response to receiving from a client computer a client request to connect to a server: processing the client request in a network protection device including applying one or more translations and one or more security checks, generating a server acknowledgment to the client computer as if the server acknowledged receiving the client request from the client computer, processing the server acknowledgement in the network protection device including applying one or more translations and one or more security checks and sending the server acknowledgment to the client computer; in response to receiving a client acknowledgment of receiving the server acknowledgment, determining that a first path between the client computer and the network protection device is operational; generating a server request to the server; processing the server request in the network protection device, determining that a second path between the network protection device and the server is operational.