Rubrik, Inc.

Google Inc.

Foley & Lardner LLP

Anshul Mohan Gupta

Nikhil Rao

Ian Baker

Jay Akkad

Deepti Kochar

Kevin Rui Luo

Adam Coimbra

Hao Wu

David T Wang

Wei Guang Lu

Tarun Kumar Jain

Vijay Karthik

Neil Dhillon

Vaibhav Bhagee

Stavan Parikh

Srishti Srivastava

Abhay Mitra

Abdullah Reza

Vivek Sanjay Jain

Suman Swaroop

Sai Kiran Katuri

David Wang

Amelia Vu

Satwant Rana

Ayush Mishra

Takeshi Suzuki

Sarvar M Patel

Philip Andrew McDonnell

Guilherme Vale Ferreira Menezes

Shobhit Saxena

Muraliraja Muniraju

Benjamin Kreuter

Sachin Kulkarni

Karn Seth

Shivanshu Agrawal

Thai Duong

Daniel Hefenbrock

Nitin Rathor

Vaibhav Gosain

Lewi Abseno

Vinay Goel

Patrick McDonald

Mihaela Ion

Wei Lu

Stavan Parkih

Methods, systems, and devices for data management are described. A data management system (DMS) may receive a request to back up a software-as-a-service (SaaS) application including a set of computing objects. The computing objects within the set of computing objects may include respective sets of pages. The DMS may access, based on the request, first sets of metadata and first sets of data elements of a first set of pages included in a first computing object. The DMS may store, for each page in the first set of pages included in the first computing object, a respective first set of metadata in one or more first fields of a respective page structure defined by a page schema at the DMS and a respective first set of data elements in a second field of the respective page structure defined by the page schema.

Backup and recovery for computing objects with hierarchical page structures

Secure communication in mobile digital pages is provided. The system receives an electronic document and validates the electronic document for storage in a cache server. The system receives a request for the electronic document and provides it to a viewer component on a client computing device. The viewer component loads the electronic document in an iframe. The viewer component executes a runtime component to receive, via a secure communication channel, a tag from the electronic document. The system receives the tag and selects a data value for transmission to the viewer component. The viewer components provides the data value to cause the runtime component to execute an action with the data value.

Secure communication in mobile digital pages

Secure digital assistant integration with web pages is provided. The system receives an intent manifest data structure that maps actions of a digital assistant with link templates of an electronic resource developed by a third-party developer device. The system validates the electronic resource based on the intent manifest data structure. The system receives, from a data exchange component of an iframe of the electronic resource loaded by a client computing device, an identifier of the client computing device. The system receives a foreground state of the electronic resource from an onsite state sharing API. The system selects a data value for a parameter based on the foreground state and the intent manifest data structure. The system provides the data value. An authorization component generates an authorization prompt, receives input, and transmits the data value to an onsite intent execution API of the electronic resource to execute an action.

Secure digital assistant integration in web pages

Methods, systems, and devices for data management are described. Software-as-a-service (SaaS) applications may host customers' information in a distributed environment that is not directly accessible to the customers. SaaS applications may store data in the form of relational tables. Snapshots for SaaS applications may maintain hierarchical relationships between computing objects and tables to enable cascading recovery. A data management system (DMS) may identify the computing object hierarchy for an organization's data as hosted by a SaaS application and also may identify the APIs associated with accessing each computing object, which may each include multiple tables. Tables that are accessed via a same API may be organized as logical entities. The DMS may store the hierarchical relationship between the tables, and as the tables are stored as logical entities, the DMS may organize the tables in the backup database based on which APIs are used to access the relevant tables.

Relational software-as-a-service data protection

Methods, systems, and devices for data management are described. Software-as-a-service (SaaS) applications may host customers information in a distributed environment that is not directly accessible to the customers. In some SaaS applications each organization may have a settings computing object, a features computing object, and a set of projects computing objects. The hierarchical relationships in each of the projects computing objects may depend on the tables in the settings and features computing objects. A data management system (DMS) may include discovery, backup, refresh, and restore frameworks that maintain hierarchical relationships between computing objects and tables including the dependency of projects computing objects on settings or features computing objects.

Backup and recovery for software-as-a-service data

Techniques for database discovery are described. A networked computing system comprises a backup node cluster of a backup service in communication with a host database node cluster of a host, a host database at least initially undiscovered by the backup node cluster, one or more processors coupled with memory storing instructions that, when executed, perform operations comprising at least installing a backup agent on at least one node of the host database node cluster, registering the host at the backup service, based on the host registration, triggering a host database discovery process to discover the undiscovered database automatically, the discovery process including a discovery call, in response to the discovery call, receiving metadata relating to the discovered database, and communicating with the discovered database.

Automated discovery of databases

Methods, systems, and devices for data management are described. A data management system (DMS) may support backup and recovery of a filesystem. The DMS may, as part of the backup, obtain a snapshot of the filesystem. The DMS may mount the snapshot within a user space of a node of the DMS. The user space may be isolated from other processes that execute on the node of the DMS. The DMS may generate, within the user space based on the mounted snapshot, index files that index the filesystem. In response to a subsequent request to access one or more files, the DMS may retrieve the one or more files from the snapshot mounted in the user space based on the index files.

Filesystem recovery and indexing within a user space

Methods, systems, and devices for data management are described. A data management system (DMS) may obtain metadata associated with a snapshot stored by the DMS and including information associated with data paths in the snapshot. The DMS may scan an index registry for identifiers of the data paths to determine whether the index registry includes namespace and hierarchical index information that map the data paths to path identifiers and to descendent data paths within the snapshot, respectively. The DMS may generate term and count index information based on the metadata. The term and count index information may map terms to data paths that include the terms and numerical values associated with the terms, respectively. The DMS may store, in the index registry, the term and count index information with an identifier of a corresponding index group. The namespace and hierarchical index information may be common to multiple index groups.

Metadata search, filtering, and aggregation using indexes

In some examples, a data management system processes snapshots of a distributed file system, the distributed file system having files, each file comprising multiple data chunks. The data management system performs operations including storing file-to-chunk mapping in file system metadata; creating, for each chunk, a chunk generation ID by associating each chunk with a file system generation ID; in a next-generation snapshot of the distributed file system, incrementing, for all chunks in the next-generation snapshot, the respective chunk generation IDs; and taking a snapshot of the file system metadata and storing an updated file-to-chunk mapping associated with the next-generation snapshot.

Snapshot and restoration of distributed file system

In some examples, a networked computing system comprises a backup node cluster of a backup service in communication with a host database node cluster of a host, a host database at least initially undiscovered by the backup node cluster, one or more processors coupled with memory storing instructions that, when executed, perform operations comprising at least installing a backup agent on at least one node of the host database node cluster, registering the host at the backup service, based on the host registration, triggering a host database discovery process to discover the undiscovered database automatically, the discovery process including a discovery call, in response to the discovery call, receiving metadata relating to the discovered database, and communicating with the discovered database.

In some examples, a data management system generates snapshots in a distributed file system based on a protocol or a user triggered event, The data management system identifies a snappable file in a distributed file system and a first data block in the snappable file, the first data block including data and attribute data. The system scans an index file to access the attribute data of the first data block and initiates construction of a patch file based on the accessed attribute data. The system repeats the scanning of the index file to access attribute data of at least a further second data block, the second data block including data and attribute data, and completes construction of the patch file based on the accessed attribute data of the first and second data blocks. The system generates conversion simulation information by collecting attribute data for all the data blocks of the constructed patch file, and writes the simulation information to a patch file image.

Online data format conversion

Synchronization of access controls between computing devices is provided. The system receives a request from a first device. The system performs a session handover to a second device responsive to determining an incompatibility. The system modifies a parameter in an access control database. The system receives a request from a third device. The system provides the digital component to the third device.

Synchronizing access controls between computing devices

Growing community of inventors

Sunnyvale, CA, United States of America

Anshul Mohan Gupta