Netapp, Inc.

Anil Kumar Ponnapur

Tijin George

Atul Ramesh Pandit

Dnyaneshwar Nagorao Pawar

Roopesh Chuggani

Jose Mathew

Sriram Venketaraman

Jagavar Nehra

Akhil Kaushik

Manoj Kumar V Sundararajan

Aravind Srinivasa Raghavan

Anurag Palsule

Nagender Somavarapu

Abhishek Naidu

Rachita Kothiyal

Harish Kumar Sampangi Rama

Techniques are provided for performing a resync transfer to recover from a storage site failure. During normal operation of a first site hosting a first volume, data is replicated to a second volume hosted by a second site. If the first site fails, when clients are redirected to the second volume at the second site. When the first site recovers, data modifications made to the second volume are resynced back to the first volume. As part of synchronizing the first volume, a data warehouse is rebuilt at the first site in order to track the location of blocks present on the replication destination. Typically, the data modifications are transferred after the data warehouse is rebuilt, which results in significantly long resync times. The techniques provided herein decrease the resync time by either rebuilding the data warehouse in parallel with resyncing the data modifications or circumvent the need for rebuild.

Resync transfer for recovering from storage site failure utilizing background pull operations

Techniques are provided for an object file system for an object store. Data, maintained by a computing device, is stored into slots of an object. The data within the slots of the object is represented as a data structure comprising a plurality of nodes comprising cloud block numbers used to identify the object and particular slots of the object. A mapping metafile is maintained to map block numbers used to store the data by the computing device to cloud block numbers of nodes representing portion of the data stored within slots of the object. The object is stored into the object store, and the mapping metafile and the data structure are used to provide access through the object file system to portions of data within the object.

Snapshot storage and management within an object store

One or more techniques and/or computing devices are provided for resilient replication of storage operations. For example, a first storage controller may host first storage having a replication relationship with second storage hosted by a second storage controller. To improve resiliency against transient network issues of a network between the storage controllers, the first storage controller may implement a queue and retry mechanism to retry replication operations not acknowledge back by the second storage controller within a threshold time. The second storage controller may maintain a cumulative sequence number of a latest replication operation performed in order, an operation response map of replication operations performed out of order, and an operation finder map identifying currently implemented replication operations, which may be used to process incoming replication operations. Single write semantics, write order consistency, and reduction of write amplification may be provided.

Resilient implementation of client file operations and replication

Object store file system format for representing, storing, and retrieving data in an object store according to a structured format

A network storage server implements a method to limit simultaneous data transfers and efficient throttle management. The number of processes that can be simultaneously performed in the network storage server is limited. For the processes that do not exceed the limiting number, and are therefore allowed to be simultaneously performed, a throttle control is implemented on each of the processes to limit the amount of system resources that can be allocated to each of the processes. The processes are performed on the network storage server, and a total amount of system resources allocated to these processes does not exceed the available system resources of the network storage server.

Limiting simultaneous data transfers and efficient throttle management

Techniques introduced here allow restoration of a virtual machine container using resources of a host least likely to suffer a performance impact from additional loading associated with the restoration of the virtual container. In particular, a protection manager controls the restoration process. Restoration of virtual machine containers is accomplished without overloading any one hosting system where multiple such hosting systems are executing a plurality of virtual machines.

System and method for virtual machine host load protection

A system and method are described for coordinating deduplication operations and backup operations of a storage volume. In one embodiment, a request is identified to eliminate duplicate data from a storage volume. The storage volume may be scheduled to be backed up on a periodic basis. The duration of time required to complete an operation to eliminate duplicate data from the storage volume may be determined. The determination may be based on the amount of data modified on the storage volume since the last operation to eliminate duplicate data from the storage volume. The determined duration of time may be used to schedule the start time of the operation to eliminate duplicate data such that the operation is completed prior to the next scheduled backup of the storage volume. The operation may be initiated at the scheduled start time, ensuring the operation is completed prior to the next scheduled backup.

System and method for coordinating deduplication operations and backup operations of a storage volume

Growing community of inventors

Sunnyvale, CA, United States of America

Anil Kumar Ponnapur