Rubrik, Inc.

Rohit Agrawal

Mudit Malpani

Prasenjit Sarkar

Ramya Thulasingam

David Anthony Terei

Prateek Pandey

Disheng Su

Amelia Vu

Shaswat Chaubey

Haitao He

Ningshan Li

Sujeet Gholap

Koki Yoshida

Richard Yuh

A data management system (DMS) may use a staggered full snapshot rollout approach to obtain full snapshots of multiple computing objects. The DMS may identify that a quantity of the multiple objects scheduled for full backups by the DMS exceeds a threshold quantity. The DMS may initiate, at a first time, and based on the quantity of objects exceeding the threshold quantity, a first set of full snapshots corresponding to a first subset of objects included in the multiple objects. The DMS may initiate, at a second time subsequent to the first time, a second set of full snapshots corresponding to a second subset of objects included in the multiple objects. The second subset of objects may be different than the first subset of objects. The DMS may continue to obtain full snapshots of respective subsets of the multiple objects until all of the scheduled full snapshots are obtained.

Obtaining full snapshots for subsets of objects over time

In some examples, a cluster comprises peer nodes and a distributed data store implemented across the peer nodes, a method of remote linking of data objects for data transfer between a first node cluster and a second node cluster among the peer nodes, the method comprising: creating a data object group including multiple remote data objects, wherein a plurality of remote data objects in the data object group represent a same first virtual machine and are registrable on at least the first and second node clusters of the peer DMS nodes; creating or identifying remote links to a plurality of the remote data objects in the data object group; designating a member of the data object group as an active member of the group; and assigning a task to the active member to be completed using remote links.

Remote snappable linking

Methods, systems, and devices for data management are described. A data management system (DMS) may determine to generate a backup instance of an application that includes multiple user accounts. The DMS may identify a time window for generation of the backup instance based on a set of backup parameters associated with the application. The DMS may calculate respective runtime durations for the user accounts based on respective quantities of data objects in the user accounts and respective backup job types associated with the data objects. The DMS may determine respective values of a semaphore parameter based on the respective runtime durations and the time window, where the semaphore parameter defines a threshold quantity of data objects to be processed in parallel. The DMS may generate the backup instance of the application based on processing the user accounts in accordance with the respective values of the semaphore parameter.

Dynamic resource scaling for large-scale backups

In some examples, a duster comprises peer nodes and a distributed data store implemented across the peer nodes, a method of remote linking of data objects for data transfer between a first node cluster and a second node cluster among the peer nodes; the method comprising: creating a data object group including multiple remote data objects, wherein a plurality of remote data objects in the data object group represent a same first virtual machine and are registrable on at least the first and second node clusters of the peer DMS nodes; creating or identifying remote links to a plurality of the remote data objects in the data object group; designating a member of the data object group as an active member of the group; and assigning a task to the active member to be completed using remote links.

In some examples, a data management and storage (DMS) cluster comprises peer DMS nodes and a distributed data store implemented across the peer DMS nodes. The peer DMS nodes are configured to collectively implement operations in a method of remote linking of snappables for data transfer between a first node cluster and a second node cluster among the peer DMS nodes.

Methods and systems for reducing the data recovery time when failing back to a primary system from a secondary data backup system using virtual machine conversions and incremental exportation for backed-up virtual machine snapshots are described. Upon detection that the primary system is available to receive replicated snapshots for a virtual machine, the secondary data backup system may identify a first virtual machine snapshot out of a chain of snapshots for the virtual machine (e.g., the earliest in time snapshot within the chain or a middle snapshot in the middle of the chain) and transfer a full image snapshot for the first virtual machine snapshot to the primary system. Thereafter, data changes between the next virtual machine snapshot to be transferred to the primary system and the most-recently hydrated virtual machine on the primary system may be identified and then transferred to the primary system.

Growing community of inventors

Mountain View, CA, United States of America

Rohit Agrawal