Abstract: A data management system may support a configuration backup of a first backup system that manages backup procedures for data of a host environment that is separate from the first backup system. The data management system may transmit, to the first backup system, a request to generate the configuration backup that includes information for the one or more backup procedures managed by the first backup system. The data management system may cause the configuration backup to be stored in a separate storage location. In response to first backup system failure, the data management system may transmit, to a second backup system, a request to apply one or more configurations for the first backup system to the second backup system based on the stored configuration backup for the first backup system.

Abstract: A data management system (DMS) may support intelligent snapshot protection techniques. For example, the DMS may backup a computing system and facilitate that capture and storage of snapshots of the computing system. The DMS may identify a deletion event associated with one or more of the snapshots, the deletion event being associated with the one or more snapshots being deleted at a first time. The DMS may determine that deletion event is anomalous and retain the one or more snapshots beyond the first time. For example, the DMS may determine that one or more parameters associated with the deletion event are indicative of the deletion event being anomalous. In response, the DMS may retain the one or more snapshots for a retention period beyond the first time.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may obtain a snapshot of a file system that includes multiple files and permission sets associated with the files. A permission may indicate one or more access approvals for associated principals. The DMS may assign unique values to the permission sets, where each unique value identifies a respective permission set. The DMS may store a first mapping between the files and the unique values based on the permission sets that correspond to the files. The DMS may store a second mapping between the principals and the unique values based on an evaluation of the permission sets. The DMS may use the first mapping and the second mapping to identify, for a principal, a set of files to which the principal has access.

Abstract: A data management and storage (DMS) cluster of peer DMS nodes manages data of a tenant of a multi-tenant compute infrastructure. The compute infrastructure includes an envoy connecting the DMS cluster to virtual machines of the tenant executing on the compute infrastructure. The envoy provides the DMS cluster with access to the virtual tenant network and the virtual machines of the tenant connected via the virtual tenant network for DMS services such as data fetch jobs to generate snapshots of the virtual machines. The envoy sends the snapshot from the virtual machine to a peer DMS node via the connection for storage within the DMS cluster. The envoy provides the DMS cluster with secure access to authorized tenants of the compute infrastructure while maintaining data isolation of tenants within the compute infrastructure.

Abstract: A data management and storage (DMS) cluster of peer DMS nodes manages migration of an application between a primary compute infrastructure and a secondary compute infrastructure. The secondary compute infrastructure may be a failover environment for the primary compute infrastructure. Primary snapshots of virtual machines of the application in the primary compute infrastructure are generated, and provided to the secondary compute infrastructure. During a failover, the primary snapshots are deployed in the secondary compute infrastructure as virtual machines. Secondary snapshots of the virtual machines are generated, where the secondary snapshots are incremental snapshots of the primary snapshots. In failback, the secondary snapshots are provided to the primary compute infrastructure, where they are combined with the primary snapshots into construct a current state of the application, and the application is deployed in the current state by deploying virtual machines on the primary compute infrastructure.

Abstract: Example embodiments relate generally to systems and methods for continuous data protection (CDP) and more specifically to an input and output (I/O) filtering framework and log management system to seek a near-zero recovery point objective (RPO).

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may obtain a snapshot of a file system that includes multiple files and permission sets associated with the files. A permission set may indicate one or more access approvals for associated principals. The DMS may scan the files to identify unique pairs each including a unique combination of a respective permission set and a respective sensitive information type. The DMS may store a first mapping that maps the unique pairs to respective values that indicate an amount of sensitive information, of the respective sensitive information type, that is included in one or more files associated with the unique pair. The DMS may identify a respective set of sensitive data types included in files to which a principal has access based on the first mapping and an evaluation of the permission sets.

Abstract: A data management and storage (DMS) cluster of peer DMS nodes manages migration of an application between a primary compute infrastructure and a secondary compute infrastructure. The secondary compute infrastructure may be a failover environment for the primary compute infrastructure. Primary snapshots of virtual machines of the application in the primary compute infrastructure are generated, and provided to the secondary compute infrastructure. During a failover, the primary snapshots are deployed in the secondary compute infrastructure as virtual machines. Secondary snapshots of the virtual machines are generated, where the secondary snapshots are incremental snapshots of the primary snapshots. In failback, the secondary snapshots are provided to the primary compute infrastructure, where they are combined with the primary snapshots into construct a current state of the application, and the application is deployed in the current state by deploying virtual machines on the primary compute infrastructure.

Abstract: Methods, apparatuses, and computer readable media are configured to perform operations comprising: obtaining, by a data management system (DMS), a first snapshot of a computing system; generating, by the DMS, one or more vectors based at least in part on data from the first snapshot; and adding, by the DMS, the one or more vectors to a vector database along with metadata or a pointer to the metadata, wherein the metadata is associated with the data from the first snapshot, and wherein the vector database comprises a knowledge repository that is accessible to an application associated with the DMS, the application further associated with communication with a large language model (LLM).

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may obtain a snapshot of a file system that includes multiple files and permission sets associated with the files. A permission set may indicate one or more access approvals for associated principals. The DMS may scan the files to identify unique pairs each including a unique combination of a respective permission set and a respective sensitive information type. The DMS may store a first mapping that maps the unique pairs to respective values that indicate an amount of sensitive information, of the respective sensitive information type, that is included in one or more files associated with the unique pair. The DMS may identify a respective set of sensitive data types included in files to which a principal has access based on the first mapping and an evaluation of the permission sets.

Abstract: Example embodiments relate generally to systems and methods for continuous data protection (CDP) and more specifically to an input and output (I/O) filtering framework and log management system to seek a near-zero recovery point objective (RPO).

Abstract: 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.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may obtain a snapshot of a file system that includes multiple files and permission sets associated with the files. A permission set may indicate one or more access approvals for associated principals. The DMS may scan the files to identify unique pairs each including a unique combination of a respective permission set and a respective sensitive information type. The DMS may store a first mapping that maps the unique pairs to respective values that indicate an amount of sensitive information, of the respective sensitive information type, that is included in one or more files associated with the unique pair. The DMS may identify a respective set of sensitive data types included in files to which a principal has access based on the first mapping and an evaluation of the permission sets.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may obtain a snapshot of a file system that includes multiple files and permission sets associated with the files. A permission may indicate one or more access approvals for associated principals. The DMS may assign unique values to the permission sets, where each unique value identifies a respective permission set. The DMS may store a first mapping between the files and the unique values based on the permission sets that correspond to the files. The DMS may store a second mapping between the principals and the unique values based on an evaluation of the permission sets. The DMS may use the first mapping and the second mapping to identify, for a principal, a set of files to which the principal has access.

Abstract: 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.

Abstract: A data management and storage (DMS) cluster of peer DMS nodes manages data of a tenant of a multi-tenant compute infrastructure. The compute infrastructure includes an envoy connecting the DMS cluster to virtual machines of the tenant executing on the compute infrastructure. The envoy provides the DMS cluster with access to the virtual tenant network and the virtual machines of the tenant connected via the virtual tenant network for DMS services such as data fetch jobs to generate snapshots of the virtual machines. The envoy sends the snapshot from the virtual machine to a peer DMS node via the connection for storage within the DMS cluster. The envoy provides the DMS cluster with secure access to authorized tenants of the compute infrastructure while maintaining data isolation of tenants within the compute infrastructure.

Abstract: A data management system may support a configuration backup of a first backup system that manages backup procedures for data of a host environment that is separate from the first backup system. The data management system may transmit, to the first backup system, a request to generate the configuration backup that includes information for the one or more backup procedures managed by the first backup system. The data management system may cause the configuration backup to be stored in a separate storage location. In response to first backup system failure, the data management system may transmit, to a second backup system, a request to apply one or more configurations for the first backup system to the second backup system based on the stored configuration backup for the first backup system.

Abstract: Methods, systems, and devices for data management are described. In some examples, a data management system (DMS) may obtain a snapshot of an identity management system (IMS) that governs access to a set of computing objects for principals. The DMS may generate membership data structures for the principals based on the snapshot. A membership data structure for a principal may indicate one or more other principals included in the principal. The DMS may obtain access control lists (ACLs) for the set of computing objects. An ACL for a computing object may indicate access approvals, access denials, or any combination thereof for one or more associated principals. The DMS may generate mapping functions based on the ACLs. Applying a mapping function for an ACL to membership data structures for principals may yield a set of permitted users that have access to a computing object that is associated with the ACL.

Abstract: Methods, systems, and devices for data management are described. In some examples, a data management system (DMS) may obtain a snapshot of an identity management system (IMS) that governs access to a set of computing objects for principals. The principals may include users and groups of users. The DMS may obtain metadata for the principals based on information included in the snapshot. Metadata for a principal may include direct group membership information that indicates one or more groups of which the principal is a direct member. The DMS may assign unique values to the principals. The DMS may perform a graph traversal procedure to identify, based on the direct group membership information, a hierarchical structure of the principals. The DMS may generate, based on the graph traversal procedure, membership data structures for the principals. A membership data structure may indicate one or more principals that descend from a corresponding principal.

Abstract: A data management system may support a configuration backup of a first backup system that manages backup procedures for data of a host environment that is separate from the first backup system. The data management system may transmit, to the first backup system, a request to generate the configuration backup that includes information for the one or more backup procedures managed by the first backup system. The data management system may cause the configuration backup to be stored in a separate storage location. In response to first backup system failure, the data management system may transmit, to a second backup system, a request to apply one or more configurations for the first backup system to the second backup system based on the stored configuration backup for the first backup system.