Netapp, Inc.

Rajesh Desai

Akhil Kaushik

John K Edwards

Blake H Lewis

Vijay Mohan Deshmukh

Ravi Krishna Budhia

Vikas Yadav

Kapil Kumar

Pranab Patnaik

Kai Tan

Jose Mathew

Abhishek Naidu

Onkar Bhat

Divya Yogesh

A system and method for enabling data replication is described. A set of protocol messages can be associated with a set of corresponding set of requests. The associated set of protocol messages can be provided to each of a source storage system and a destination storage system. The source storage system and the destination storage system can be heterogeneous storage systems that implement different types of file systems or file layouts. The source storage system and the destination storage system are enabled to perform a data replication process, in which at least a set of data is to be replicated from the source storage system to the destination storage system, using at least a protocol message from the associated set of protocol messages. The protocol message can correspond to a request for a list of snapshots stored at the source storage system.

Enabling data replication processes between heterogeneous storage systems

A technique to name data is disclosed to allow preservation of storage efficiency over a link between a source and a destination in a replication relationship as well as in storage at the destination. The technique allows the source to send named data to the destination once and refer to it by name multiple times in the future, without having to resend the data. The technique also allows the transmission of data extents to be decoupled from the logical containers that refer to the data extents. Additionally, the technique allows a replication system to accommodate different extent sizes between replication source and destination while preserving storage efficiency.

Handling data extent size asymmetry during logical replication in a storage system

One or more techniques and/or systems are provided for data recovery objective modeling. For example, a data recovery objective model may be defined for a storage network environment. The data recovery objective model may be defined based upon a client data ingest rate corresponding to a data change rate by one or more clients of data stored by a first storage controller. The data recovery objective model may be defined based upon an effective throughput of a data transfer utility for replicating modified data from first storage of the first storage controller to second storage of a second storage controller. Statistical utilization data may be collected from the storage network environment, and may be evaluated using the data recovery objective model to determine a data recovery objective metric. If the data recovery objective metric does not satisfy a client specified objective, then a computing resource recommendation may be provided.

Data recovery objective modeling

One or more techniques and/or computing devices are provided for granular replication for data protection. For example, a first storage controller may host a first volume. A consistency group, comprising a subset of files, logical unit numbers, and/or other data of the first volume, is defined through a consistency group configuration. A baseline transfer, using a baseline snapshot of the first volume, is used to create a replicated consistency group within a second volume hosted by a second storage controller. In this way, an arbitrary level of granularity is used to synchronize/replicate a subset of the first volume to the second volume. If a synchronous replication relationship is specified, then one or more incremental transfer are performed and a synchronous replication engine is implemented. If an asynchronous replication relationship is specified, then snapshots are used to identify delta data of the consistency group for updating the replication consistency group.

Granular consistency group replication

Various embodiments are generally directed an apparatus and method for receiving a recovery point objective for a workload, the recovery point objective comprising an amount of time in which information for the workload will be lost if a failure occurs, and determining a service level objective for a replication transfer based on the recovery point objective, the replication transfer to replicate information on a destination node to maintain the recovery point objective. Various embodiments include dynamically controlling one or more resources to replicate the information on the destination node based on the service level objective and communicating information for the replication transfer from the source node to the destination node.

Techniques for dynamically controlling resources based on service level objectives

Growing community of inventors

Sunnyvale, CA, United States of America

Rajesh Desai