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.

Abstract: Methods, systems, and devices for data management are described. A data management system may support techniques for bulk object selection and recovery for a set of computing objects. The data management system may receive an indication of a backup snapshot group identifier which defines a selection of a group of backup snapshots for performing a bulk recovery. The backup snapshot group identifier is then translated into a materialized list of object identifiers corresponding to the set of backup snapshots for storage in a binary large object (BLOB) data store. The data management system may then perform the bulk recovery on a subset of the set of backup snapshots contained within a sliding window that is iterated through the list of object identifiers within the BLOB data store.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may receive a request to access metadata stored in a distributed metadata repository. The request may have a first semantic format compatible with a first version of the distributed metadata repository. The DMS may translate the first semantic format of the request to a second semantic format compatible with a second version of the distributed metadata repository. The DMS may perform the semantic translation according to a label in the request. Accordingly, the DMS may determine whether a current version of the metadata corresponds to the first version of the distributed metadata repository or the second version of the distributed metadata repository, and may access the metadata in the distributed metadata repository based on the request and the current version of the metadata.

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

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may identify two snapshots from two different snapshot chains and rewrite one of the snapshots as a cross-incremental snapshot over the other snapshot that includes differential data relative to the other snapshot. Based on rewriting the snapshot as the cross-incremental snapshot, the DMS may reduce the amount of storage space used by the snapshot chain of the cross-incremental snapshot (as cross-incremental snapshots may use less space than base snapshots). In some examples, the DMS may identify which snapshots to rewrite as cross-incremental snapshots based on one or more parameters. For example, the one or more parameters may include respective snapshot expiration times for each of the snapshot chains.

Abstract: Methods, systems, and devices for data management are described. A data management system may include computing nodes that host respective sets of computing pods. The data management system may identify that some computing nodes each satisfy a resource usage threshold, and may cordon some of the identified computing nodes such that no new pods may be added to the cordoned computing nodes. The system may then perform a software update for the cordoned nodes and the non-cordoned nodes, which may result in replacing a first set of pods (previously on the cordoned nodes) with an updated first set of pods on the set of non-cordoned nodes and replacing a second set of pods (previously on the non-cordoned nods) with an updated set of second pods on the set of non-cordoned nodes. The system may then eliminate the empty set of cordoned nodes based on the update.

Abstract: A method for establishing secure connectivity is described. The method may include transmitting, to one or more host nodes of a data management system (DMS), an indication of a backup service configuration that includes a public key certificate associated with a first cluster of storage nodes in the DMS and a root certificate associated with a certificate authority. The method may further include establishing a primary connection between the first cluster and the host nodes using the public key certificate. The method may further include obtaining, by a second cluster of storage nodes in the DMS, a certificate chain signed by the certificate authority. The method may further include establishing a secondary connection between the second cluster and the host nodes in response to the first cluster becoming disconnected from the host nodes, where the secondary connection is established using the certificate chain.

Abstract: Methods, systems, and devices for data management are described. A method may include obtaining a new snapshot of a relational database of a source computing environment, comparing the new snapshot of the relational database to a prior snapshot of the relational database, updating, in response to the comparison indicating that data of a row of a relational database table changed between the prior snapshot and the new snapshot, a field of a second versioning control column of a corresponding row of a backup database table of the set of backup database tables to indicate a version of the new snapshot, and adding, in response to the comparison indicating that the data of the row of the relational database table changed, an additional row to the backup database table, where a field of a first versioning control column of the additional row includes an indication of the version of the new snapshot.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may perform a lightweight consolidation operation on an expired snapshot rather than a full consolidation operation that merges the expired snapshot into another snapshot based on one or more snapshot heuristics. The lightweight consolidation operation may delete data that is not shared with (e.g., referenced by, relied upon by) any subsequent incremental snapshot without reading all of the data within the snapshot and without deleting the expired snapshot or writing data into a new file. The DMS may perform a full consolidation operation if a quantity of leaked space satisfies a threshold. Additionally, or alternatively, the DMS may perform the full consolidation operation if a snapshot chain length exceeds a threshold and if performing the full consolidation operation would reduce the used space by a threshold quantity.

Abstract: 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, meaning that data is organized in tables that have hierarchical relationships. SaaS tables may include permissive relationships to other tables (e.g., a row in one table may point to data in another table). Restoration of a SaaS computing object (e.g., one or more SaaS tables) may involve restoration of other computing objects in both dependent and permissive relationships with the SaaS computing object. Cascading metadata logic may be stored in association with a particular computing object that may indicate, for each relationship, whether to perform a restore operation and a type of cascading restore to perform when the particular computing object is to be restored to a particular computing environment.

Abstract: Methods, systems, and devices for data management are described. The initiation or forthcoming initiation of a data protection operation for a computing system may be identified. Short-term information of the computing system, including information stored in the volatile memory of the computing system, network traffic associated with the computing system, or both, may be obtained based on the initiation or forthcoming initiation of the data protection operation. Long-term information of the computing system, including information stored in the non-volatile memory of the computing system, may be obtained based on the data protection operation being initiated. Both the short-term information and the long-term information may be stored for further analysis.

Abstract: Methods, systems, and devices for data management are described. Techniques described herein may enable a database management system (DMS) to link databases of a failover group that spans multiple data centers across different clusters for the different datacenters. For example, a centralized control entity may indicate to the clusters in different datacenters that one or more databases in a first datacenter are in a same failover group as one or more other databases in a second datacenter. A database of the first datacenter may be a primary backup database from which a first cluster in the first datacenter may obtain transaction log backups. The first cluster of the datacenter may replicate the backups to a second cluster of a second datacenter, which may enable the second cluster to refrain from obtaining backups from a secondary backup database within the second datacenter.

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: Subject matter related to data management is disclosed. A request to restore target objects of a computing system may be received, where a data management system may store multiple snapshots for the target objects and metadata for the snapshots. The snapshots may be filtered using metadata for the snapshots to obtain a set of snapshots that are available for restoring respective target objects. From among the set of snapshots, suggested snapshots that are available for restoring respective target objects may be identified. The suggested snapshots may be indicated.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may provide backup and recovery services for customer computing systems or databases. The DMS may implement an active/passive partition scheme to enable reception of log files in a push manner and avoid frequent building and teardown of the stack to back up the database. The DMS may implement two storage partitions which alternate between an active and passive state. Received log files may be stored temporarily in a first storage partition in the active state. Once the first storage partition is transitioned to the passive state, the DMS may capture a snapshot of the storage partition and may store the snapshot. When the first storage partition is transitioned to the passive state, the second storage partition may be transitioned to the active state so that the DMS may continue to receive log files.

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

Abstract: A data management system (DMS) may receive entries corresponding to files and directories of a storage system that changed within a time period. The received entries may include metadata associated with the changed files and directories. The DMS may identify one or more directories that were renamed or deleted within the time period by analyzing the metadata from the received entries. The DMS may identify descendent directories and descendent files corresponding to the one or more renamed or deleted directories. The DMS may update path identifiers associated with the descendent directories and the descendent files based on the metadata from the received entries. The DMS may generate an updated index file based on updating the path identifiers for the descendent directories and the descendent files. The described techniques may enable the DMS to identify renames and deletions with greater efficiency, among other benefits.

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.