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.

Abstract: Some examples relate generally to computer architecture software for information security and, in some more particular aspects, to machine learning based on changes in snapshot metadata for anomaly and ransomware detection in a file system.

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 include multiple disks. A distributed file system may be stored across the multiple disks. The DMS may receive a request to perform a first job for the distributed file system. The DMS may send the first job for execution, during a time period, by a set of disks. The first job may correspond to input/output (I/O) operations associated with a first priority that is higher than second priorities associated with second jobs for execution by the set of disks. Respective timings for executing the second jobs may be based on respective availabilities of resources at the set of disks. The DMS may synchronize, during the time period, the respective availabilities of resources across the set of disks based on the set of disks executing the first job associated with the first priority.

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: Methods, systems, and devices for data management are described. Point-in-time data that includes one or more files may be generated from data management information stored at a data management system having multiple nodes. One or more sets of virtual partitions may be created for at least one file of the one or more files. One or more external file descriptors associated with respective locations of the at least one file and one or more sets of internal file descriptors associated with respective external file descriptors and locations of corresponding sets of virtual partitions may be generated in response to a request. One or more subsequent requests to read the at least one file may be routed to the nodes based on the one or more sets of internal file descriptors. Based on the routing, the respective portions of the one or more files may be output in parallel.

Abstract: Methods, systems, and devices for data management are described. Authorization may be received, from a user of a customer of an operator of a first computing system, to access an instance of a first application running at the first computing system for the customer via a user account for the customer. Based on receiving the authorization, a request from a user of the operator to access a second application associated with generating a one-time credential associated with the user account may be received. The second application may run at the first computing system. Based on authenticating the user of the operator for access to the second application, the one-time credential may be provided to the user of the operator, which may use the one-time credential to gain temporary access to the instance of the first application via the user account.

Abstract: Methods, systems, and devices for data management are described. The method may include obtaining a first fingerprint of one or more first data blocks obtained from a source data system, where the one or more first data blocks correspond to one or more data objects and are in accordance with a first storage format, obtaining, a second fingerprint of one or more second data blocks as stored in the backup system, where the one or more second data blocks correspond to the one or more data objects and are stored in the backup system in accordance with a second storage format, and comparing, in accordance with a mapping between data objects of the source data system and data blocks in the backup system, the first fingerprint and the second fingerprint to validate whether the one or more data objects are stored correctly at the backup system.