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: 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: 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: 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: A data backup server may obtain, for a set of databases that includes a primary database and a set of standby databases configured to be synchronized with the primary database. The data backup server may identify, based on the role information, a data backup group that includes a subset of the databases. In some examples, the first database may be included in the data backup group based on being a primary database, the one or more second databases may be included in the data backup group based at least in part on being standby databases of a first type, and the one or more third databases may be excluded from the data backup group based on being standby databases of a second type. The data backup server may then perform a backup procedure based on generating a snapshot of a database within the data backup group.

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.

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