Virtualization software installed in a standalone host is remediated according to a desired state model using a desired image of a virtualization software that is used to remediate virtualization software running in hosts which are logically grouped as a cluster of hosts not including the standalone host. The method of remediating the virtualization software installed in the standalone host includes the steps of generating a desired image of the virtualization software of the standalone host from a desired image of the virtualization software of the hosts in the cluster, and upon detecting a difference between an image of the virtualization software currently running in the standalone host and the desired image of the virtualization software of the standalone host, instructing the standalone host to remediate the image of the virtualization software currently running therein to match the desired image of the virtualization software of the standalone host.

Featured are a method and apparatus for managing various point-in-time copies of workloads or applications using a software system called workload manager. An aspect of the invention is to receive backup images of point-in-time backup images of workload from a backup client and realize corresponding virtual resource from backup image on the cloud platform that is part of the workload manager appliance. Workload manager maintains catalog of point-in-time copies of workloads. Each item in the catalog refers resource entries on the cloud platform. When user wishes to instantiate a point-in-time copy, workload manager instantiates all the resources identified in the catalog entry. User can also restore a particular point-in-time workload to production system or migrate a particular point-in-time workload to remote application.

Methods for backup and recovery are disclosed. The method includes determining, based on attributes of at least one of one or more files included in data to be backed up, priorities of data blocks associated with the at least one file and storing the data to be backed up and indications of the determined priorities of the data blocks to a second storage device. The methods may determine data blocks that are more important for recovery while backing up data, so that backup data can be recovered faster in future.

A charge calculation method executed by a processor included in a computer to execute a process, the process includes determining a degree of possibility that a virtual machine having redundant configuration exists in a plurality of virtual machines that provide a service, calculating a difference of charges for using the service before and after a first virtual machine among the plurality of virtual machines is migrated to an another location different from a location where the first virtual machine is located, and displaying the degree of possibility and the difference with respect to the service.

A virtualized computing environment of a telecommunications network comprises a cluster of virtual machines with a one-to-one ratio of active and backup virtual machines. One or more additional clusters of virtual machines have a N-to-K ratio of active and backup virtual machines where N>K. The backup virtual machines are configured to provide failover capacity for processing communications sessions in an event of a failure of one of the active virtual machines. A cluster redundancy capability indicates the ratio of the active and backup virtual machines for that cluster. A predetermined type associated with a requested communication session is determined. A cluster having a cluster redundancy capability corresponding to the predetermined type is selected. Data for the requested communication session is sent to an active virtual machine in the selected cluster.

Techniques are described for providing managed computer networks, such as for managed virtual computer networks overlaid on one or more other underlying computer networks. In some situations, the techniques include facilitating replication of a primary computing node that is actively participating in a managed computer network, such as by maintaining one or more other computing nodes in the managed computer network as replicas, and using such replica computing nodes in various manners. For example, a particular managed virtual computer network may span multiple broadcast domains of an underlying computer network, and a particular primary computing node and a corresponding remote replica computing node of the managed virtual computer network may be implemented in distinct broadcast domains of the underlying computer network, with the replica computing node being used to transparently replace the primary computing node in the virtual computer network if the primary computing node becomes unavailable.

A method for dynamically storing files/data, comprising: a) acquiring the file/data by an initial random Virtual Machine (r VM); b) shredding the file/data to a plurality of segments; c) wrapping, in a standalone state, each of the remaining segments with a unique code comprised of at least one or more destination storage locations, a pointer to a following segment in the file/data, and a timer; d) autonomously and independently roaming each segment to the destination storage location appearing in its unique code; and e) periodically, according to the timer, continuously roaming segments between storage locations until receiving a request for retrieving of the dynamically stored file/data.

The disclosed technology provides techniques, systems, and apparatus for containing and recovering from uncorrectable memory errors in distributed computing environment through migration of virtual machines and associated memory to a target host machine. An aspect of the disclosed technology includes a hypervisor or virtual machine manager that receives signaling of an uncorrectable memory error detected by a host machine. The virtual machine manager then uses information received via the signaling to identify virtual memory addresses or memory pages associated with the corrupted memory element so as to allow for containment and recovery from the error, and for live migration of the virtual machine.

Tagging application resources for snapshot capability-aware discovery is described. If an application's host determines that one of an application's resource satisfies any snapshot capability rule, the application's host associates the application resource with a snapshot capable tag. The application's host outputs an identifier of the application resource and any associated snapshot capable tag to a backup server. The application's host inputs a request from the backup server to create a snapshot of the application resource associated with the snapshot capable tag and creates the snapshot of the application resource associated with the snapshot capable tag.

Live recovery generates a new “recovery VM” that operates as an ongoing “live” production platform. A previously created non-cloud-native backup copy is the data source for the recovery VM. Live recovery restores data blocks from the backup copy on backup media directly to cloud-based virtual disk(s) assigned to the recovery VM. As a result, the cloud-based recovery VM can become fully operational in the cloud computing environment on a going-forward basis. The advantage of live recovery over a traditional restore is that live recovery provides a cloud-based VM that begins operating well before the backup copy is fully restored. This is accomplished by temporarily mounting a “temp-mounted VM” in the cloud while the backup copy is methodically restored in the background. VM reads and writes begin issuing from the temp-mounted VM and writes are retained on completion. Downtime is minimized when switching from the temp-mounted VM to the recovery VM.