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: Aspects of data management are described. Information for updating software for a data management cluster from a first version associated with a first configuration for operating multiple storage nodes of the data management cluster and a second version associated with a second configuration for operating multiple storage nodes of the data management cluster may be obtained. Based on the information, an update procedure for the data management cluster may be performed, where after a first portion of the update procedure, the first version may be installed on a first set of the storage nodes and the second version may be installed on a second set of the storage nodes. Based on storage nodes in the data management cluster having different software versions, the data management cluster may be operated using the first configuration, the second configuration, or both, during the update procedure.

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.

Abstract: Some computing systems may implement a user interface to provide a visualization of system contents to a user. To place a widget or component within the user interface, a user may select from a plurality of candidate display regions that have different respective sizes. The size of the first widget may be adjusted from a prior size to a first size in response to the first widget being moved to at least partially overly a first candidate display region, and may be further adjusted from the first size to a second size in response to the first widget being moved to at least partially overly a second candidate display region. The widget may then be displayed within the second candidate display region after adjusting the size of the first widget to the second size.

Abstract: Methods, systems, and devices for data management are described. The described techniques may enable a data management system (DMS) to determine an amount of data to be pulled from a source cluster prior to performing a replication of a source file stored on the source cluster. For example, before copying any data from the source cluster to a target cluster, the DMS may read an index file associated with the source file to determine data blocks that are different from data blocks of a base file stored on the target cluster, which may indicate indices of data blocks of the source file that may be replicated from the source cluster to the target cluster as part of the replication operation. By profiling the data to be copied before copying the data to the target cluster, the DMS may optimize the replication process to reduce latency, among other examples.

Abstract: Some users of a data management system (DMS) may use multiple computing environments to replicate and store virtual machines (VM)s, such as for backup and recovery purposes. For example, different replication environments may include one or more private data centers, one or more cloud environments or any combination thereof. A user may schedule a failover procedure for an application. A DMS may perform a failover procedure that reduces downtime and eliminates data loss. The DMS may capture and replicate a snapshot of a VM running on a source computing environment to a target computing environment, power down the VM on the source computing environment, capture and replicate a second snapshot of the VM to the target computing environment, and power on the VM at the target computing environment. As the additional snapshot includes a relatively small amount of data replication at the target computing environment may proceed quickly, reducing downtime.

Abstract: Methods, systems, and devices for data management are described. A client may transmit, to a server, a login request for an application. The login request may include authentication parameters associated with a user. The client may receive, from the server, an access token that supports access via a user interface to one or more services associated with the application before expiration of a time-to-live for the access token. The client may transmit, prior to expiration of the time-to-live for the access token and based on a session inactivity timeout timer being active, a refresh request for a new access token. The refresh request may include an indication of the access token. The application may receive the new access token in response to the refresh request, and the new access token supports access to the one or more services before expiration of a time-to-live for the new access token.

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.