At least a portion of a virtual machine is hosted on at least one node of a first subset of a plurality of nodes of a secondary storage system. The virtual machine comprises a plurality of portions that can be distributed between the plurality of nodes and is configured into a first state of a plurality of states, such that, in the first state, the plurality of portions is distributed between a first subset of the plurality of nodes and each of the first subset of nodes stores a portion of the virtual machine in its corresponding storage device. A node from the second subset of the plurality of nodes to host the virtual machine in a second state of the plurality of states is selected based on at least one of storage, memory or processing resources of one or more nodes of a second subset of the plurality of nodes.

Methods and systems for managing, storing, and serving data within a virtualized environment are described. In some embodiments, a data management system may manage the extraction and storage of virtual machine snapshots, provide near instantaneous restoration of a virtual machine or one or more files located on the virtual machine, and enable secondary workloads to directly use the data management system as a primary storage target to read or modify past versions of data. The data management system may allow a virtual machine snapshot of a virtual machine stored within the system to be directly mounted to enable substantially instantaneous virtual machine recovery of the virtual machine.

Automatic network configuration for the recovery of virtual machines. A network configuration can be automatically provisioned by discovering the network topology of a source site and then matching the virtual machines to their locations or subnets in the network topology. The network is then implemented on a target site such that the required connectivity is present in the recovered target site even when the infrastructure of the source site and the target site are different.

Embodiments for systems and methods of providing a boot order for containers in a cloud native application environment by collecting container environment data from a first container site; determining dependencies and connections between the containers and applications executed within the containers based on a number of system parameters; calculating a recommended order for booting or rebooting the containers during a disaster recovery process; and communicating the recommended order to a system administrator through a graphical user interface (GUI) for acceptance or modification by the system administrator.

Disclosed are various examples for virtual-machine-specific failover protection. In some examples, a power-on request is received for a protected virtual machine. Virtual-machine-specific failover protection is enabled for the protected virtual machine. The protected virtual machine is executed on a first host of a cluster, and a dynamic virtual machine slot for the protected virtual machine is created on a second host of the cluster. The dynamic virtual machine slot is created to match a hardware resource configuration of the protected virtual machine. An anti-affinity rule is maintained between the protected virtual machine and the dynamic virtual machine slot.

A computer-implemented method according to one embodiment includes initializing a new gateway node at a first site in response to a failure of an old gateway node at the first site; creating, at the new gateway node, a list of dirty directories at the first site; synchronizing, with a second site by a background thread at the first site, all directories within the list of dirty directories; and synchronizing, with the second site by a foreground thread at the first site, new operations performed within the first site after the initialization of the new gateway node.

A method, computer program product, and computing system for receiving, at a first baseboard management controller (BMC) of a first node, a fence request from a central processing unit (CPU) of the first node. The first BMC of the first node may communicate with a second BMC of a second node, wherein the first node and the second node are communicatively coupled to a plurality of storage drives. The first BMC and the second BMC may determine which node of the first node and the second node to fence from the plurality of storage drives. One of the first node and the second node may be fenced, via one of the first BMC and the second BMC, from the plurality of storage drives, thus defining a fenced node.

A system and method determining a Chain Identification Number (CID) of a source snapshot to be replicated from a source site to a target site of a virtual computing system, determining a predetermined number of potential reference snapshots based on the CID of the source snapshot, computing a closeness value between the source snapshot and each of the potential reference snapshots, and creating a list of the potential reference snapshots based on the closeness value of each of the potential reference snapshots. One snapshot from the list is selected as a reference snapshot. The source snapshot is replicated to the target site based on the reference snapshot.

A method can include receiving, by a high-availability (HA) service running in a data center having a plurality of virtual machines (VMs) and a hypervisor, credentials for the hypervisor and a list of VMs, the hypervisor credentials and the list of VMs received from a power and capacity management (PCM) service, the PCM service configured to selectively power VMs from the list of VMs on and off; sending, from the HA service to the PCM service, a health check request to determine if the PCM service is able of selectively power the VMs from the list of VMs on and off; and in response to determining the PCM service is unable to selectively power the VMs from the list of VMs on and off, powering on, by the HA service, one or more of the VMs from the list of VMs using the hypervisor credentials received from the PCM service.

Concepts and technologies are disclosed herein for providing a network virtualization policy management system. An event relating to a service can be detected. A first policy that defines allocation of hardware resources to host the virtual network functions can be obtained, as can a second policy that defines deployment of the virtual network functions to the hardware resources. The hardware resources can be allocated based upon the first policy and the virtual network functions can be deployed to the hardware resources based upon the second policy.