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: A data management and storage (DMS) cluster of peer DMS nodes manages data of a tenant of a multi-tenant compute infrastructure. The compute infrastructure includes an envoy connecting the DMS cluster to virtual machines of the tenant executing on the compute infrastructure. The envoy provides the DMS cluster with access to the virtual tenant network and the virtual machines of the tenant connected via the virtual tenant network for DMS services such as data fetch jobs to generate snapshots of the virtual machines. The envoy sends the snapshot from the virtual machine to a peer DMS node via the connection for storage within the DMS cluster. The envoy provides the DMS cluster with secure access to authorized tenants of the compute infrastructure while maintaining data isolation of tenants within the compute infrastructure.

Abstract: Methods, systems, and devices for data management are described. A cloud data backup and recovery system may include a destination system and a source system. The destination system may be operable to provide backup and recovery services for the source system. The destination system may communicate a set of push/pull notifications with the source system. Each push/pull notifications may indicate an event is being performed in the source system. The destination system may determine an event is being performed in the source system based on transmitting a push notification or receiving a pull notification, where the push or pull notification may include metadata associated with the event. The destination system may retrieve, from the source system, data that is modified by the event based on the metadata. The destination system may synchronize a database of the destination system based on the data retrieved from the source system.

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: In some embodiments, a process for restoring a version of a virtual machine using a data storage system comprises identifying a particular version of a virtual machine to be restored, determining a base image from which the particular version may be derived, determining a set of incremental files for generating the particular version, generating a file associated with the particular version using the base image and the set of incremental files, and outputting at least a portion of the file.

Abstract: Some examples relate generally to computer architecture software for data classification and information security and, in some more particular aspects, to verifying audit events in a file system.

Abstract: Methods, systems, and computer programs are presented for providing backup recoverable ranges in a database system. One method includes an operation for determining if a backup chain is within a recoverable range. The recoverable range defines a time interval in which data from a database system is recoverable to a point in time within the time interval. The method further includes an operation for preserving the backup chain when the backup chain is within the recoverable range. When the backup chain is not within the recoverable range, the method includes operations for checking a retention policy for the backup chain, determining whether to preserve or expire the backup chain based on the retention policy, and preserving the backup chain based on the determination on the retention policy.

Abstract: Techniques for preventing recovery of specific data elements based on a recovery prevention configuration defined by a user are disclosed. In some embodiments, a computer system performs operations comprising: receiving a recovery prevention configuration from a first computing device of a first user, the recovery prevention configuration comprising at least one recovery prevention parameter specified by the first user via one or more user interface elements displayed on the first computing device, the at least one recovery prevention parameter being configured to identify one or more backup data elements stored in a secondary storage system; storing the recovery prevention configuration in a database in association with the secondary storage system; and filtering out the one or more backup data elements stored in the secondary storage system from a data recovery process based on the at least one recovery prevention parameter of the stored recovery prevention configuration.

Abstract: Techniques for data management are described. A file may be saved that includes a representation of an exported database, where the representation may be based on a live database being exported from a computing system via an export operation that spans a time period. A determination that one or more transactions were committed to the live database during the time period may be made. Based on the determination, a log indicating the one or more transactions may be obtained from the computing system. Based on the log, a determination of whether the exported database captured the one or more transactions may be made. Based on the determination, the file may be updated to represent an updated database that reflects an updated version of the live database, the updated version of the live database reflection application of the one or more transactions to the exported database.

Abstract: Methods and systems for improving the performance of a primary system that is running one or more virtual machines and capturing snapshots of the one or more virtual machines over time are described. The performance penalty on the primary system when a hypervisor running the one or more virtual machines is used to capture the snapshots of the one or more virtual machines may be reduced by leveraging storage array snapshots to reduce the amount of time that the hypervisor must freeze virtual disks of the one or more virtual machines. In this case, changed block tracking information for changed data blocks associated with the snapshots may be acquired from the hypervisor and the changed data blocks themselves may be pulled from the storage array snapshots without requiring the hypervisor to keep the virtual disks of the one or more virtual machines in a frozen state.

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: 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: A cross-platform data migration method and a cross-platform data migration system include determining that a first database is compatible with a second database, receiving a user request associated with an instruction to migrate data from the first database to the second database, determining that backup data corresponding to a current state of the first database is available, mounting the backup data onto the second platform via a distributed file system protocol, converting the backup data from the source endian format to a target endian format, and restoring the backup data in the target endian format to the second platform.

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: In some examples, a cluster protection system comprises at least one processor and a memory storing instructions which, when executed by the at least one processor, cause the system to perform operations comprising identifying a target cluster or an object in a container management framework, identifying application data and metadata associated with the target cluster or the object, generating a first snapshot of the target cluster or the object, the first snapshot including at least the metadata, storing the first snapshot in offsite cloud storage, generating a second snapshot of the target cluster, the second snapshot including at least the application data, and storing the second snapshot in a persistent volume in onsite storage.

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: Aspects of data management are described. A cluster-level state machine may be instantiated for an update procedure for updating software for a cluster of storage nodes, where the update procedure may be configured to serially update the plurality of storage nodes. The cluster-level state machine may be configured to monitor the update procedure at a cluster level. One or more node-level state machines may be instantiated for the update procedure, where the one or more node-level state machines may be configured to monitor the performance of the update procedure at a storage node level. During an update procedure, the state of the cluster-level state machine may reflect a state of the cluster of storage nodes and the state of a node-level state machine may reflect a state of a respective one or more storage nodes.

Abstract: A data management system (DMS) may facilitate the storage tiering of snapshots on cloud environments. For example, the DMS may transmit snapshot signaling to a first cloud environment that instructs the first cloud environment to capture a first snapshot of a computing object and to store the first snapshot in a first type of cloud storage at the first cloud environment. The DMS may determine that the first snapshot has been stored in the first type of cloud storage for a duration of time that satisfies an archival threshold. Based on the archival threshold being satisfied, the DMS may transmit archival signaling that instructs the first cloud environment to store the first snapshot to a second type of cloud storage. The second type of cloud storage may be associated with a longer access latency than the first type of cloud storage.

Abstract: Examples relate generally to systems and methods for orchestrating a recovery in the event of a ransomware attack on a compute infrastructure. More specifically, some examples include techniques for application migration in cloud data management, ransomware recovery, and mitigation of lost data.

Abstract: Techniques for managing proxy virtual machines are disclosed. In some embodiments, a computer system deploys proxy virtual machines on a data center in an intelligent way in order to optimize performance and efficiency for backing up data from and restoring data to the data center, using the topology of the data center to determine how many proxy virtual machines to deploy and on which specific hosts to deploy the proxy virtual machines. Rather than determining the number of proxy virtual machines to deploy based on a coaxing out of all of the ports on each proxy virtual machine to handle a planned quantity of backup jobs, the computer system may calculate the number of proxy virtual machines to use based on a rule that ports be left available for un-planned on-demand restore jobs.