Nutanix, Inc.

Mayur Vijay Sadavarte

Monoreet Mutsuddi

Parthasarathy Ramachandran

Bharat Kumar Beedu

Vanita Prabhu

Karthik Chandrasekaran

Balaji Janakiram

Karan Gupta

Angshuman Bezbaruah

Pranab Patnaik

Anoop Reddy

Ajaykrishna Raghavan

Kiran Tatiparthi

Praveen Kumar Padia

Gowtham Alluri

Rajkumar Arunkumar Joshi

Bharath Kumar Beedu

Chinmay Dinesh Kamat

Ravishankar Chandhiramoorthi

Systems for application configuration backup and restore. Techniques establish high frequency restore points of application configuration metadata. Processing commences upon receiving instructions to periodically take snapshots of application configuration metadata. To avoid incurring unnecessary costs to process snapshots of application configuration metadata when the application configuration metadata is slow-changing, the method performs a low-cost check to get the latest update time of the application configuration metadata. That time is compared to the time of the most recent snapshot of the application configuration metadata. When the time of the latest update time of the application configuration metadata is equal to the time of the most recent snapshot of the application configuration metadata, then rather than incurring the cost of generating a duplicate snapshot, the method waits for a duration without generating a new snapshot. High frequency restore points for application configuration metadata are emulated by pointing to corresponding lower frequency snapshots.

High-frequency virtual machine restore points

The disclosed systems emulate high-frequency application-consistent snapshots by forming restore point data sets based on remote site replay of I/O commands. A method embodiment commences upon identifying a primary computing site and a secondary computing site, then identifying an application to be restored from the secondary computing site after a disaster. Prior to the disaster, a group of computing entities of the application to be restored from the secondary computing site are identified. Input/output operations that are performed over any of the computing entities at the primary site are streamed to the secondary site where they are stored. An I/O map that associates a time with an indication of a last received I/O command that had been performed over a changing set of computing entities is sent to the secondary site. An agent at the secondary site accesses the I/O map and the streamed-over I/Os to construct recovery data.

Emulating high-frequency application-consistent snapshots by forming restore point data sets based on remote site replay of I/O commands

An illustrative embodiment disclosed herein is an apparatus including a processor having programmed instructions to detect an operation associated with a first object instance in a first cluster, determine that the first object instance is configured for replication to a second cluster, create an object information (info) metadata entry for the first object instance, create an object replication metadata entry for the first object instance, and simultaneously write the object info metadata entry and the object replication metadata entry to a first data structure and a second data structure, respectively.

System and method for near-synchronous replication for object store

Systems for high performance restore of data to storage devices. A method embodiment commences upon identifying a plurality of virtual disks to be grouped together into one or more consistency sets. Storage I/O commands for the plurality of virtual disks of the consistency sets are captured into multiple levels of backup data. On a time schedule, multiple levels of backup data for the virtual disks are cascaded by processing data from one or more higher granularity levels of backup data to one or more lower granularity levels of backup data. A restore operation can access the multiple levels of backup data to construct a restore set that is consistent to a designated point in time or to a designated state. Multiple staging areas can be maintained using lightweight snapshot data structures that each comprise a series of captured I/Os to be replayed over other datasets to generate a restore set.

Lossless data restore using multiple levels of lightweight snapshots

Forming lightweight snapshots for lossless data restore operations

Systems and methods for using snapshots to establish operable portions of computing entities on secondary sites for use on the secondary sites before the computing entity is fully transferred to the secondary site. Embodiments commence upon initiating replication of an entity from an originating site to a secondary site. While replication of the entire entity from the originating site to the secondary site is being carried out, the originating site transfers entity metadata to the secondary site. A non-replication user process queries the metadata to determine completion status and/or other characteristics of subcomponents of the entity. After determining the completion status of subcomponents of the entity, the non-replication user process operates on subcomponent data of the entity even before the data of the entity has been completely copied to the secondary site. The subcomponents may comprise certain tables of a database or certain rows of a table of a database.

Using snapshots to establish operable portions of computing entities on secondary sites for use on the secondary sites before the computing entity is fully transferred

Techniques for replay of groups of I/Os for disaster recovery. At a primary site, a plurality of primary site computing entities that are to be restored from the secondary computing site after a disaster recovery event are identified as belonging to an entity group. At the primary site, I/O commands that are performed over any of the entities of the entity group are observed and streamed to the secondary site, where they are persisted into a log. Periodically, the primary site sends the secondary site an I/O map that associates a time with an indication of the last performed I/O commands pertaining to any observed I/O commands that had been performed over any one or more of the computing entities of the entity group. Upon receiving a disaster recovery request, the most recent I/O map and the secondary site log are processed to construct a snapshot for the entity group.

Consistency group restoration from a secondary site

The present disclosure provides a method, apparatus, and computer program product for generating consistent snapshots without quiescing applications. The snapshots correspond to consistency groups that in turn correspond to one or more vDisks on one or more nodes. Some embodiments of the present disclosure address the problem of generating consistent backup snapshots that cover cases of multiple virtual machines (VMs) that operate in a multi-node distributed computing environment (e.g., in clusters) without quiescing the accessing entity(ies). In some embodiments, the process includes identification of a triggering snapshot event, disabling of write complete responses to requesting entities for the resources corresponding to the snapshot to be generated, generating snapshots while one or more additional write requests are received, and using one or more techniques to insure that all actions corresponding to the snapshotting function do not occur outside of a specified time frame.

Method, apparatus, and computer program product for generating consistent snapshots without quiescing applications

A system and method for capturing high frequency snapshots of an entity includes creating, by a storage sub-system associated with a distributed storage system of a virtualized environment, a cached configuration of an entity within the storage sub-system, capturing, by the storage sub-system, a snapshot of the entity from the cached configuration based on a schedule of a snapshot policy, including sending, by the storage sub-system, the snapshot to a repository indicated in the snapshot policy, and determining, by the storage sub-system, that a configuration file associated with the entity has been updated. The system and method also includes updating, by the storage sub-system, the cached configuration based upon the configuration file that has been updated.

Growing community of inventors

Sunnyvale, CA, United States of America

Mayur Vijay Sadavarte