Abstract: A data management and storage (DMS) cluster of peer DMS nodes manages data backup and disaster recovery using a service level agreement. The backup data can be replicated from a primary compute infrastructure to the secondary compute infrastructure. For example, primary snapshots of virtual machines of the application in the primary compute infrastructure are generated, and provided to the secondary compute infrastructure. If the primary compute infrastructure is lost, the secondary compute infrastructure is initialized to replicate the primary compute infrastructure. Applications that were running in the primary compute infrastructure can failover to run in the secondary compute infrastructure. The replicated backup data is used to facilitate the migration. During a failover, the primary snapshots are deployed in the secondary compute infrastructure as virtual machines.

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.

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: An example method of managing and storing data includes pulling and saving a first snapshot of a first state of a target machine running on a cloud service and creating a first virtual machine (VM) package associated with the first snapshot. The first VM package sufficient to instantiate a VM emulating the target machine with the first state on an on-premise destination VM platform. The method includes pulling and saving a second snapshot of a second state of the target machine, wherein the second state occurs after the first state. A second VM package is created and associated with the second snapshot, the second VM package sufficient to instantiate the VM emulating the target machine with the second state on the destination VM platform. The second VM package is created by updating the first VM package according to differences between the first snapshot and the second snapshot.

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.

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 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: 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: 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: 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 backing up and restoring different point in time versions of a virtual machine, an application, a database, or an electronic file using independently managed snapshot chains are described. In some cases, different point in time versions of a virtual machine may be captured and stored using one or more snapshot chains. Each snapshot chain may correspond with a base image (e.g., a full image snapshot) and one or more incremental files (e.g., two forward incremental files) that derive from the base image. A snapshot chain may be split into a plurality of shards or sub-chains such that the width of each shard or the maximum data size of the files in each shard is less than a threshold data size (e.g., is less than 1 TB). Data operations (e.g., consolidation and reverse operations) may be performed on the individual shards or sub-chains in parallel.

Abstract: The disclosed technology teaches keeping a linked snapshot history, stored in sequence and spanning multiple VMs, even when VMs are unregistered and reregistered and are moved from one data center to another data center, and to take incremental snapshots across multiple linked VMs. Upon receiving a request for a VM snapshot, detect that the ID is a new ID assigned by an external machine in a hosted service environment and determine whether the new ID corresponds to a newly-created VM or an existing previously-registered VM using a previous ID. Upon identifying that the new ID corresponds to a newly-created VM, the disclosed method includes creating a new VMG for the newly-created VM. If the new ID does not correspond to a newly created VM, then identify an existing VMG for the VM and using the VMG, determine snapshot histories for the ID and return a historical snapshot from the histories.

Abstract: The disclosed technology teaches catch-up replication, replicating to a target machine, a set of snapshots including replicated snapshots and un-replicated snapshots, stored in sequence at a source machine, that backup one or more virtual machines.

Abstract: The disclosed technology teaches keeping a linked snapshot history, stored in sequence and spanning multiple VMs, even when VMs are unregistered and reregistered and are moved from one data center to another data center, and to take incremental snapshots across multiple linked VMs. Upon receiving a request for a VM snapshot, detect that the ID is a new ID assigned by an external machine in a hosted service environment and determine whether the new ID corresponds to a newly-created VM or an existing previously-registered VM using a previous ID. Upon identifying that the new ID corresponds to a newly-created VM, the disclosed method includes creating a new VMG for the newly-created VM. If the new ID does not correspond to a newly created VM, then identify an existing VMG for the VM and using the VMG, determine snapshot histories for the ID and return a historical snapshot from the histories.

Abstract: Methods and systems for throttling per-node network bandwidths over time to maximize the aggregate bandwidth of a distributed cluster of nodes without exceeding a global bandwidth allowance for the entire cluster are described. The throttling of the individual node network bandwidths may include periodically adjusting individual node bandwidth settings for each node of a plurality of nodes within the cluster using node network interfaces. The adjusting of the individual node bandwidth settings for each node of the plurality of nodes may take into account the number and type of jobs running within the cluster at a particular point in time. The updates to the individual node bandwidth settings may be transmitted such that a first subset of the plurality of nodes with decreasing individual node bandwidth allocations are updated prior to updating a second subset of the plurality of nodes with increasing individual node bandwidth allocations.

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.