Rubrik, Inc.

Jonathan Carlyle Derryberry

Arvind Nithrakashyap

Arvind Jain

Soham Mazumdar

Kenny To

Bipul Sinha

Adam Gee

Sai Kiran Katuri

David Anthony Terei

Prateek Pandey

Dharma Teja Bankuru

Vikas Jain

Fabiano C Botelho

Mudit Malpani

Jiangbin Luo

Janmejay Singh

Sharvanath Pathak

Arpit Agarwal

Amelia Vu

Aravind Menon

Harish Raman Shanker

Gaurav Jain

Sagar Kashinath Honnungar

Jayanth Madheswaran

Mohammad Bavarian

Pradeep Madhavarapu

Satwant Rana

Anmol Arora

Jun Xu

Vinay Patil

Charlotte Tong

A data management system may support techniques for immutable storage of snapshot data entities, which may each include data corresponding to one or more snapshots, in a cloud environment. The data management system may determine respective retention periods and respective immutability periods for the snapshot data entities. The data management system may extend the respective immutability period for a first snapshot data entity based on the respective retention period for the first snapshot data entity being greater than or equal to a threshold duration. Additionally or alternatively, the data management system may maintain (refrain from extending) the respective immutability period for a second snapshot data entity based at least in part on the respective retention period for the second snapshot data entity being less than the threshold duration.

Immutable storage of snapshot data in a public cloud environment

Methods, systems, and devices for data management are described. A data management system may include a control-plane common to multiple customers, where customer data for each customer is stored on a private data plane (e.g., at a remote node cluster). Each node cluster includes a controller which manages the nodes of the node cluster. A taskchain controller of the control plane may directly communicate with the nodes of the multiple node clusters, for example, via respective proxy services hosted at the node controllers or via respective service buses. The taskchain controller may communicate a command to add a new node to the node controller, and the node controller may create a new node based on the command. Future communications (e.g., commands to perform data protection tasks such as backup or restore operations) may be routed to the node via the proxy service or a service bus.

Reliable and high-performance connectivity between control-planes and data-planes for a data management system

Methods and systems for managing, storing, and serving data within a virtualized environment are described. In some embodiments, a data management system may manage the extraction and storage of virtual machine snapshots, provide near instantaneous restoration of a virtual machine or one or more files located on the virtual machine, and enable secondary workloads to directly use the data management system as a primary storage target to read or modify past versions of data. The data management system may allow a virtual machine snapshot of a virtual machine stored within the system to be directly mounted to enable substantially instantaneous virtual machine recovery of the virtual machine.

Data management system

Systems and methods for cloud object storage and versioning are provided. In an example, a cloud object storage and versioning system (COSVS) coordinates insertion of metadata into a database and data into an object store in a compute infrastructure, the compute infrastructure including the database, the object store, a data source, and a client application interacting with the data source. The COSVS has an architecture comprising a client API layer confined to provide an interface to the client application to facilitate storing or restoring of items originally obtained from the data source, and query different versions of item content originally obtained from the data source; a deduplication layer to deduplicate item content and store items originally obtained from the data source devoid of external item metadata or semantic relations among items; and a packing layer confined to store and retrieve bytes of item or object content.

Cloud object storage and versioning system

Methods and systems for backing up and restoring different point in time versions of a virtual machine, an application, a database, or an electronic file using independently managed snapshot chains are described. In some cases, different point in time versions of a virtual machine may be captured and stored using one or more snapshot chains. Each snapshot chain may correspond with a base image (e.g., a full image snapshot) and one or more incremental files (e.g., two forward incremental files) that derive from the base image. A snapshot chain may be split into a plurality of shards or sub-chains such that the width of each shard or the maximum data size of the files in each shard is less than a threshold data size (e.g., is less than 1 TB). Data operations (e.g., consolidation and reverse operations) may be performed on the individual shards or sub-chains in parallel.

Blobstore system for the management of large data objects

Sharding of full and incremental snapshots

Automated generation of cloned production environments

Identification of virtual machines using a distributed job scheduler

Growing community of inventors

Union City, CA, United States of America

Jonathan Carlyle Derryberry