Abstract: Described herein are systems and methods that manage machine backups, including the creation of virtual machine packages sufficient to instantiate virtual machines corresponding to the backups. In one aspect, a compute infrastructure includes many machines, which may be either physical or virtual. From time to time, snapshots of the states of these target machines are pulled and saved. Virtual machine packages corresponding to these snapshots are also created. A virtual machine package can be used to instantiate a virtual machine (VM) emulating the target machine with the saved state on a destination virtual machine platform. At some point, the initial VM package for a target machine is created by converting the snapshot to a VM package. However, this may take a long time. Later VM packages can instead be created by updating a prior VM package according to differences between the corresponding snapshots, rather than performing the full conversion process.

Abstract: According to various embodiments, with respect to a target set of files being managed (e.g., protected by data snapshots), each file in the target set of files is classified into one of two or more filesets (discontiguous filesets), where each of these filesets comprises one or more files that are related to each other by one or more factors, such as frequency of file change or purpose of existence (e.g., used by a software application). Once classified, files within the target set of files can be uniquely processed by a data management operation (e.g., incremental data snapshot process) according to their association to a discontiguous fileset.

Abstract: A method for updating configuration settings of a backup database supported by a data management system is described. The method may include receiving, from a first user in a first user group, a request to update configuration settings of the backup database. The method may further include determining that the first user is authorized to update the configuration settings of the backup database based on a set of permissions associated with the first user. The method may further include identifying a second user in a second user group that is authorized to approve the request from the first user. The method may further include transmitting an indication of the request to the second user and receiving a notification that the second user has approved the request from the first user. The method may further include updating the configuration settings of the backup database in response to the notification.

Abstract: A data backup and recovery method and system using allocated data blocks include identifying a first snapshot associated with a virtual machine; accessing changed block tracking data associated with data changes occurred in the virtual machine, the data changes corresponding to a set of changed data blocks; accessing block allocation status data associated with the set of changed data blocks; identifying one or more allocated data blocks from the set of changed data blocks that are associated with allocated status based on the block allocation status data; and storing the one or more allocated data blocks to a storage device.

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. In some systems, a client may request for a data management system (DMS) to execute a first instance of a query to obtain, from a database, first information that is responsive to the query. The DMS may identify, in response to the query being executed in an execution time that is greater than a threshold amount of time, an improved version of the query that is associated with a second execution time that is less than the threshold amount of time. The DMS may store the improved version of the query. The DMS may retrieve the improved version of the query in response to receiving a second instance of the query. The DMS may execute the improved version of the query after retrieving the improved version from storage to obtain, from the database, second information that is responsive to the query.

Abstract: A data management system (DMS) may support the backing up of scalable computing objects, such as hierarchical computing objects. For example, the DMS may backup a computing system and facilitate that capture and storage of snapshots of the computing system. The DMS may determine to capture a first snapshot of a computing object within the computing system. The DMS may identify components corresponding to respective portions of the computing object and cause the computing system to generate respective snapshots of the components. That is, the DMS may cause the computing system to generate multiple individual snapshots that together may constitute snapshot of the computing object. The DMS may generate the first snapshot that includes metadata for the snapshots of the components. The metadata may include a first identifier for the first snapshot and respective identifiers for the respective snapshots of the components.

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

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: In some examples, a data management and storage (DMS) platform comprises peer DMS nodes in a node cluster, a distributed data store comprising local and cloud storage, and at least one processor configured to perform operations in a method of creating a local consolidated patch file from a patch file chain stored in the cloud storage. Example operations comprise, in a first dry-run phase, creating a patch file image of data blocks in one or more cloud patch files stored in the cloud storage; in a second data-transfer phase, downloading at least some of the data blocks from the cloud patch files identified by the patch file image; and creating and storing, in the local storage, the local consolidated patch file using the downloaded data blocks.

Abstract: Methods, systems, and devices for data management are described. A first application in a destination computing environment of a data management system (DMS) may determine that a bulk-push criterion is satisfied for a second application in a source computing environment of the DMS. The first application may transmit, to an asynchronous metadata service, a request indicating the second application for which the bulk-push criterion is satisfied. The request may be configured to cause the asynchronous metadata service to query a database in the source computing environment, identify a latest version of one or more rows that include metadata associated with the second application, and generate data records indicating the latest version of the one or more rows that include the metadata associated with the second application. The first application may receive the data records via an asynchronous data stream between the first application and the second application.

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: Some examples relate generally to managing and storing data, and more specifically to the real-time detection of ransomware, system (or insider) threats, or the misappropriation of credentials by using file system audit events.

Abstract: A object data backup and restore method and system provide for identifying an object from a first entity space in a cluster of a client compute environment; generating a snapshot of the object; copying the volume data to a second entity space in the cluster; detecting that the first entity space has been deleted from the cluster; receiving a request to restore the object to a point-in-time version associated with the snapshot; and restoring, via the snapshot tool, the object using the volume data copied to the second entity space and the content data of the snapshot.

Abstract: Systems and methods to utilize a tablespace to export to a native database recovery environment are described. The system receives file information and script information at a source host that operates in a native database recovery environment. The file information and the script information are received from a backup host that utilizes foreign snapshot files and foreign incremental files for storing the file information. The file information includes native snapshot files and native incremental files. The script information includes one or more scripts that execute, at the source host, to perform operations comprising: mounting the directories; opening an auxiliary database; restoring a tablespace in the auxiliary database; recovering the tablespace in the auxiliary database based on the native incremental files; exporting the tablespace metadata information from the auxiliary database; recovering the tablespace in the database based on the tablespace metadata information; and unmounting the directories.

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 storage cluster may dynamically select a data transport mode for supporting a backup or export job. The storage cluster may receive a trigger indication to create, a backup of data of a source virtual machine. The storage cluster may select a data transport mode to use for reading the data from the source virtual machine to create the backup at the storage cluster. The selection may be from a set of data transport modes that includes a proxy virtual machine mode and a direct-to-host mode. The storage cluster may transmit, to a host for the source virtual machine, a request to activate the selected data transport mode, and receive the data from the source virtual machine via the selected data transport mode. The storage cluster may use the data to create the backup.

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 and systems for managing the automated retrieval, aggregation, and selection of virtual machines, virtual disks, and electronic files using an integrated data management and storage system are described. In some cases, the integrated data management and storage system may acquire a query with search criteria to identify a set of objects accessible via the integrated data management and storage system, determine the set of objects that satisfies the search criteria, determine a first subset of the set of objects less than all of the set of objects to render, render and display a listing of the first subset, determine a selection of a first plurality of the first subset, and initiate concurrent actions on the first plurality using the integrated data management and storage system. The size of the first subset may vary over time and be determined based on prior user feedback.

Abstract: A data management system (DMS) may perform techniques for snapshotting a host environment data store using a resource volume. The DMS may transmit, to the host environment a first request for a full backup of a data store of the host environment, where the first request results in mounting of a resource volume in an empty state. The DMS may generate a snapshot of the resource volume after completion of the backup at the host. The DMS may transmit one or more second requests for incremental backups, where the second requests result in mounting of the volume in a state corresponding to a previous backup of the host. The DMS may generate a second snapshot of the resource volume. For a subsequent full backup, the DMS may cause mounting of the volume in the empty state to the host rather than mounting the resource volume corresponding to a prior snapshot.