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

Abstract: Methods, systems, and devices for data management are described. A new network configuration may be received for a cluster of nodes, where the respective nodes may have respective routable network addresses in accordance with an existing network configuration of the cluster. The new network configuration may be configured to change the respective routable network addresses. Based on receiving the new network configuration, a driving network interface between the existing network configuration and the new network configuration may be identified. It may be determined that the respective nodes are communicatively coupled over the driving network interface using respective local network addresses of the respective nodes. Based on the respective nodes being communicatively coupled via the driving network interface using the respective local network addresses, a process for configuring the new network configuration at the cluster may be executed via the driving network interface.

Abstract: Methods, systems, and devices for data management are described. A system supporting malware detection may obtain event data such as risk scores corresponding to events associated with a set of computing entities. Using the event data, the system may construct a graph that includes nodes that represent the set of computing entities, and edges that represent the events, where the edges are between initiator and affected nodes and are associated with the respective event risk scores. Using the graph, respective node risk scores may be calculated for at least some nodes of the graph, and one or more anomalous nodes may be identified based on the one or more anomalous nodes having respective node risk scores that satisfy a threshold. The system may then output an indication of one or more computing entities corresponding to the one or more anomalous nodes.

Abstract: Techniques for data management are described. A request to mount a version of a database based on data stored at a computing system may be received. Based on receiving the request, a container at the computing that is configured to support operating the version of the database may be configured. Based on creating the container, a database request for the version of the database may be received at the container. In response to the database request, the container may access a set of data stored at the computing system, the set of data being associated with the version of the database. The container may output a response to the database request based on accessing the set of data.

Abstract: Example embodiments relate generally to data resynchronization methods and systems in 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: Techniques for backing a file system with a cloud-based object store are disclosed. In some embodiments, a computer system performs operations comprising: receiving, by a user space file system, a first request to write a first set of data to a file; based on the receiving of the first request to write the first set of data to the file, writing, by the user space file system, the first set of data to the file in a cloud-based key-value object store; receiving, by the user space file system, a second request to read a second set of data from the file; and based on the receiving of the second request to read the second set of data from the file, fetching, by the user space file system, the second set of data from the file in the cloud-based key-value object store.

Abstract: Methods, systems, and devices for data management are described. Software-as-a-service (SaaS) applications may host their 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, meaning that data is organized in tables that have hierarchical parent and child relationships. Snapshots for SaaS applications may maintain hierarchical relationships between computing objects and tables to enable cascading recovery of SaaS applications. Based on a request to restore a computing object of a relational SaaS application, a data management system (DMS) may identify the associated computing objects to be recovered with the requested computing object based on the stored hierarchical information, and may call the relevant application programming interfaces (APIs) to restore the requested computing object and the associated computing objects to be recovered with the requested computing object.

Abstract: Methods, systems, and devices for data management are described. A first data source may be identified to move from a source cloud deployment (that operates in accordance with a first release cadence for updating database schema) to a destination cloud deployment (that operates in accordance with second, different release cadence for updating database schema). The first source database is then migrated from the source cloud deployment to an intermediate cloud deployment hosted on the source cloud deployments that allows the schema of the first data source to remain unchanged for a duration of time that the first data source is hosted on the intermediate cloud deployment. The database schema associated with the first data source is then updated to an updated (most recent) database schema in accordance with the second release cadence of the destination cloud deployment, and migrated from the intermediate cloud deployment to the destination cloud deployment.

Abstract: Systems and methods for facilitating an analysis of software vulnerabilities are described. The system receives a first request to present software vulnerabilities of a virtual machine on a production machine. The first request includes a first selection including a virtual machine identifier identifying the virtual machine on the production machine. The software vulnerabilities include a first software vulnerability. The system presents a first electronic user interface including software vulnerabilities for the virtual machine. The system receives a second request including a second selection identifying a first software vulnerability. The system presents a second electronic user interface including presenting recovery point identifiers corresponding to snapshot images stored on a database. The snapshot images being of the production machine and including the virtual machine and the first software vulnerability.

Abstract: Methods, systems, and devices for data management are described. A user account may be generated at a first computing system that is managed by an operator and separate from a second computing system that is managed by a customer of the operator. The user account may provide a user of the customer access to an instance of an application running at the first computing system for the customer. Based on a request from the user of the customer for support with the instance of the application, a second user account for the customer may be enabled. The second user account may provide a user of the operator temporary access to the instance of application.

Abstract: Methods for establishing a second database and maintaining synchronization between a first database and the second database in a data management system are described. According to the method, a snapshot of a state of the first database may be acquired and mounted to a second server. The second database may be restored to the second server based on the mount. The second database may replicate the state of the first database. Synchronization may be enabled between the first database and the second database. One or more metrics associated with replication of data between the databases may be identified. A backup process for transaction logs associated with the first database may be initiated and the transaction logs may be mounted to the second server based on the metrics. One or more transactions may be applied to the second database based on the transaction logs mounted to the second server.

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

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS), configured to manage backup data stored across a set of storage nodes for one or more customers of the DMS, may obtain an indication that an activation value of a feature for a first customer of the one or more customers has changed. The feature may be associated with management of the backup data, and the activation value may indicate if the feature is enabled for the first customer. The DMS may output, to a message queue accessible to the set of storage nodes and based on the indication that the activation value for the feature for the first customer has changed, a notification for one or more storage nodes to invalidate a cache entry associated with the feature for the first customer.

Abstract: The disclosed technology teaches recovering a first virtual machine or an instance with an Internet Protocol address, a first root volume and one or more data volumes that are corrupted. The first virtual machine is hosted by a first cloud server that hosts plurality of virtual machines. The disclosed technology includes instructing the first cloud server to launch a recovery virtual machine. The recovery virtual machine launches one or more new data volumes based upon captured file system images in one or more snapshots taken of corrupted data volumes of the first virtual machine prior to becoming corrupted. The recovery virtual machine detaches the corrupted data volumes and attaches the new data volumes launched to the first virtual machine. The Internet Protocol address of the first virtual machine remains unchanged.

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: Systems and methods for an extended recovery of an exported database are described. The method includes communicating a database from a source host operating in a native database recovery environment, the database being communicated to a backup host operating in a foreign database recovery environment, the native database recovery environment including native snapshot files and native incremental files for storing the database, the foreign database recovery environment including foreign snapshot files and foreign incremental files for storing the database. The method further includes receiving file information and script information, at the source host, the file information including the native snapshot files and the native incremental files, the script to perform operations for causing a recovering of the database in the foreign database recovery environment based on the changes to the database in the foreign database recovery environment after the point-in-time.

Abstract: Methods, systems, and devices for data management are described. For example, the method may include a backup system receiving a request to recover a target computing object using a snapshot of one or more computing objects, the one or more computing objects including the target computing object, determining, by the backup system in response to the request, whether the snapshot is prohibited from restoration based on whether information associated with the snapshot is flagged for quarantine, executing, by the backup system after determining that the snapshot is not prohibited from restoration, a quarantine enforcement procedure in association with recovering the snapshot, and monitoring, by the backup system, one or more performance metrics associated with execution of the quarantine enforcement procedure.

Abstract: Methods, systems, and devices for data management are described. A first procedure for capturing first point-in-time data for a data object may be performed and may include initiating a first type of operation to back up the first point-in-time data, the first operation being native to the data object and enabling sections of files to be backed up in parallel on a per-section basis. A second procedure for restoring the first point-in-time data to the computing system may also be performed. Performing the second procedure may include executing, based on recreating the first point-in-time data, the first type of operation to backup sections of first files of the first point-in-time data in parallel on the per-section basis to the computing system. And further include initiating a second type of operation to restore second files of the first point-int-time data in parallel on a per-file basis to the computing system.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may facilitate multi-layer data structure recovery. For example, the DMS may receive a request to recover a data structure backed up by the DMS to a destination environment. The data structure may include virtual machines that are organized according to a first topology that includes multiple logical layers. In response to the request, the DMS may determine the first topology using metadata associated with the structure and determine destination resources of the destination environment to which to recover the virtual machines. The destination resources may be organized according to a second topology that is the same as or based on the first topology and that includes multiple logical layers, and the DMS may recover the virtual machines to the destination environment.