Abstract: A data management and storage (DMS) cluster of peer DMS nodes manages data of an application distributed across a set of machines of a compute infrastructure. A DMS node associates a set of machines with the application, and generates data fetch jobs for the set of machines for execution by multiple peer DMS nodes. The DMS node determining whether each of the data fetch jobs for the set of machines is ready for execution by the peer DMS nodes. In response to determining that each of the data fetch jobs is ready for execution, the peer DMS nodes execute the data fetch jobs to generate snapshots of the set of machines. The snapshots may be full or incremental snapshots, and collectively form a snapshot of the application.

Abstract: A data management and storage (DMS) cluster of peer DMS nodes manages migration of an application between a primary compute infrastructure and a secondary compute infrastructure. The secondary compute infrastructure may be a failover environment for the primary compute infrastructure. Primary snapshots of virtual machines of the application in the primary compute infrastructure are generated, and provided to the secondary compute infrastructure. During a failover, the primary snapshots are deployed in the secondary compute infrastructure as virtual machines. Secondary snapshots of the virtual machines are generated, where the secondary snapshots are incremental snapshots of the primary snapshots. In failback, the secondary snapshots are provided to the primary compute infrastructure, where they are combined with the primary snapshots into construct a current state of the application, and the application is deployed in the current state by deploying virtual machines on the primary compute infrastructure.

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 a data management platform comprising: a storage device configured to store secondary data and one or more processors in communication with the storage device and configured to perform certain operations. The operations may include identifying an aspect of the secondary data stored in the storage device, the secondary data including a backup of respective primary data stored in a primary data source; identifying or receiving an indication of a target to receive data associated with the identified aspect of the secondary data; and transmitting the data associated with the aspect of the secondary data to the target.

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 computer architecture software for information security and, in some more particular aspects, to a frontier service engine for the real-time detection of malware in a monitored system.

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 a data management platform comprising a storage device configured to store secondary data and one or more processors in communication with the storage device and configured to perform certain operations. The operations may include identifying an aspect of the secondary data stored in the storage device, the secondary data including a backup of respective primary data stored in a primary data source; identifying or receiving an indication of a target to receive data associated with the identified aspect of the secondary data; and transmitting the data associated with the aspect of the secondary data to the target as a push transmission.

Abstract: Systems and methods for cloud object storage and versioning are provided. In an example, a cloud object storage and versioning system (COSVS) coordinates insertion of metadata into a database and data into an object store in a compute infrastructure, the compute infrastructure including the database, the object store, a data source, and a client application interacting with the data source. The COSVS has an architecture comprising a client API layer confined to provide an interface to the client application to facilitate storing or restoring of items originally obtained from the data source, and query different versions of item content originally obtained from the data source; a deduplication layer to deduplicate item content and store items originally obtained from the data source devoid of external item metadata or semantic relations among items; and a packing layer confined to store and retrieve bytes of item or object content.

Abstract: Some examples relate generally to a data management platform comprising a storage device configured to store secondary data and one or more processors in communication with the storage device and configured to perform certain operations. The operations may include identifying an aspect of the secondary data stored in the storage device, the secondary data including a backup of respective primary data stored in a primary data source; identifying or receiving an indication of a target to receive data associated with the identified aspect of the secondary data; transmitting the data associated with the aspect of the secondary data to the target as a push transmission; and performing data management operations related to the secondary data subsequent to the push transmission.

Abstract: The disclosed technology teaches finding contents of one or more virtual machines running on one or more cloud servers. The disclosed technology includes a cloud snapshot metadata manager periodically instantiating indexing virtual machines on the cloud servers. The indexing virtual machines compile metadata of one or more virtual machines on the cloud server from one or more snapshot file systems of the virtual machines. The indexing virtual machines then transmit the compiled metadata to the cloud snapshot metadata manager. The cloud snapshot metadata manager forwards the metadata to a client and causing the client to create an index of the compiled metadata from multiple virtual machine snapshots on multiple clouds and responding to queries from a user using the index of compiled metadata, without requiring the user to instantiate or to attach to the snapshots.

Abstract: Some examples relate generally to a data management platform comprising a storage device configured to store secondary data and one or more processors in communication with the storage device and configured to perform certain operations. The operations may include identifying an aspect of the secondary data stored in the storage device, the secondary data including a backup of respective primary data stored in a primary data source; identifying or receiving an indication of a target to receive data associated with the identified aspect of the secondary data; and transmitting the data associated with the aspect of the secondary data to the target as a push transmission.

Abstract: Some examples relate generally to a data management platform comprising: a storage device configured to store secondary data and one or more processors in communication with the storage device and configured to perform certain operations. The operations may include identifying an aspect of the secondary data stored in the storage device, the secondary data including a backup of respective primary data stored in a primary data source; identifying or receiving an indication of a target to receive data associated with the identified aspect of the secondary data; and transmitting the data associated with the aspect of the secondary data to the target.

Abstract: Some examples relate generally to a data management platform comprising a storage device configured to store secondary data and one or more processors in communication with the storage device and configured to perform certain operations. The operations may include identifying an aspect of the secondary data stored in the storage device, the secondary data including a backup of respective primary data stored in a primary data source; identifying or receiving an indication of a target to receive data associated with the identified aspect of the secondary data; transmitting the data associated with the aspect of the secondary data to the target as a push transmission; and performing data management operations related to the secondary data subsequent to the push transmission.

Abstract: A method of identifying historical snapshots for a virtual machine (VM) is provided. Some example operations include receiving a request for a historical snapshot of a VM, the request indicating an ID for the VM. A detection is made that the ID for the VM in the request received is a new ID assigned to a VM. A determination is made whether the new ID corresponds to a newly created VM or an existing VM that has been previously registered using a previous ID, wherein the determining includes accessing a property of the VM including a use case identifier associated with an instant recovery request for a specific VM. Based on identifying that the new ID corresponds to a newly created VM, a new VM Group (VMG) object is created for the newly created VM corresponding to the new ID.

Abstract: A method of identifying historical snapshots for a virtual machine (VM) is provided. Some example operations include receiving a request for a historical snapshot of a VM, the request indicating an ID for the VM. A detection is made that the ID for the VM in the request received is a new ID assigned to a VM. A determination is made whether the new ID corresponds to a newly created VM or an existing VM that has been previously registered using a previous ID, wherein the determining includes accessing a property of the VM including a use case identifier associated with an instant recovery request for a specific VM. Based on identifying that the new ID corresponds to a newly created VM, a new VM Group (VMG) object is created for the newly created VM corresponding to the new ID.

Abstract: Methods and systems for efficiently downloading archived snapshot data from the cloud or from an archival data store are described. In a disaster recovery scenario in which an entire storage appliance for backing up different point in time versions of a virtual machine has failed (e.g., due to a fire), archived snapshot data for the different point in time versions may be acquired by a second storage appliance from an archival data store (e.g., cloud-based data storage) using one or more snapshot mapping files. A snapshot mapping file may include pointers to a plurality of data blocks within the archival data store for generating a full image snapshot associated with a particular point in time version of the virtual machine. The plurality of data blocks may comprise the minimum number of data blocks necessary to construct the particular point in time version of the virtual machine.

Abstract: A method of identifying historical snapshots for a virtual machine (VM) is provided. Some example operations include receiving a request for a historical snapshot of a VM, the request indicating an ID for the VM. A detection is made that the ID for the VM in the request received is a new ID assigned to a VM. A determination is made whether the new ID corresponds to a newly created VM or an existing VM that has been previously registered using a previous ID, wherein the determining includes accessing a property of the VM including a use case identifier associated with an instant recovery request for a specific VM. Based on identifying that the new ID corresponds to a newly created VM, a new VM Group (VMG) object is created for the newly created VM corresponding to the new ID.

Abstract: A method of identifying historical snapshots for a virtual machine (VM) is provided. Some example operations include receiving a request for a historical snapshot of a VM, the request indicating an ID for the VM. A detection is made that the ID for the VM in the request received is a new ID assigned to a VM. A determination is made whether the new ID corresponds to a newly created VM or an existing VM that has been previously registered using a previous ID, wherein the determining includes accessing a property of the VM including a use case identifier associated with an instant recovery request for a specific VM. Based on identifying that the new ID corresponds to a newly created VM, a new VM Group (VMG) object is created for the newly created VM corresponding to the new ID.

Abstract: A data management and storage (DMS) cluster of peer DMS nodes manages migration of an application between a primary compute infrastructure and a secondary compute infrastructure. The secondary compute infrastructure may be a failover environment for the primary compute infrastructure. Primary snapshots of virtual machines of the application in the primary compute infrastructure are generated, and provided to the secondary compute infrastructure. During a failover, the primary snapshots are deployed in the secondary compute infrastructure as virtual machines. Secondary snapshots of the virtual machines are generated, where the secondary snapshots are incremental snapshots of the primary snapshots. In failback, the secondary snapshots are provided to the primary compute infrastructure, where they are combined with the primary snapshots into construct a current state of the application, and the application is deployed in the current state by deploying virtual machines on the primary compute infrastructure.