Abstract: A host server hosting one or more virtual machines can back up host volumes and the one or more virtual machines installed thereon in an application-consistent manner. In one implementation, a host-level requestor instructs a host-level writer to identify which virtual machines qualify for application-consistent backups. The host-level requestor then instructs the host-level writer to initiate virtual machine backups through guest-level requesters in each appropriately-configured virtual machine, wherein the virtual machines create application-consistent backups within the virtual machine volumes. The host-level requester then initiates snapshots of the server volumes on the host-level. The virtual machine-level snapshots can thus be retrieved from within the host-level snapshots of the server volumes.

Abstract: A host server hosting one or more virtual machines can back up host volumes and the one or more virtual machines installed thereon in an application-consistent manner. In one implementation, a host-level requestor instructs a host-level writer to identify which virtual machines qualify for application-consistent backups. The host-level requestor then instructs the host-level writer to initiate virtual machine backups through guest-level requesters in each appropriately-configured virtual machine, wherein the virtual machines create application-consistent backups within the virtual machine volumes. The host-level requester then initiates snapshots of the server volumes on the host-level. The virtual machine-level snapshots can thus be retrieved from within the host-level snapshots of the server volumes.

Abstract: A virtual machine may be discovered through a directory service or via an agent that is installed on the host operating system that is running the virtual machine. If the agent is installed on the virtual machine, the agent monitors changes to a set of protected volumes on the virtual machine. If the agent is installed on the host, the agent monitors changes to the protected volumes, which may contain one or more virtual servers on the host. Periodically, these changes from the host or the virtual server are sent to a data protection server. The data protection server updates its replicas of protected volumes with the sent changes. Versions of files on a data protection server corresponding to a volume of a virtual server may be restored to the virtual machine, to another machine, or may be viewed from the data protection server.

Abstract: Migration mechanisms are disclosed herein that smartly transfer data among virtual machines, minimizing the down time of migration of such machines but maximizing the consistent state of data stored thereon. Specifically, data can be classified into three types: low volatility data (such as hard disk data), high volatility data (such a random access memory data), and immutable data (such as read only data). This data can be migrated from a source virtual machine to a target virtual machine by sending the immutable data along with the low volatility data first—before the source virtual machine has stopped itself for the migration process. Then, after the source virtual machine has stopped, high volatility data and (again) low volatility data can be sent from the source to the target. In this latter case, only differences between the low volatility data may be sent (or alternatively, new low volatility data may be sent).

Abstract: A host server hosting one or more virtual machines can back up host volumes and the one or more virtual machines installed thereon in an application-consistent manner. In one implementation, a host-level requestor instructs a host-level writer to identify which virtual machines qualify for application-consistent backups. The host-level requestor then instructs the host-level writer to initiate virtual machine backups through guest-level requesters in each appropriately-configured virtual machine, wherein the virtual machines create application-consistent backups within the virtual machine volumes. The host-level requester then initiates snapshots of the server volumes on the host-level. The virtual machine-level snapshots can thus be retrieved from within the host-level snapshots of the server volumes.

Abstract: Methods and systems for updating a virtual machine image. The virtual machine image may be stored as a collection of one or more virtual hard disk files. The virtual machine image is rendered to file-system data. Rendering the virtual machine image to file-system data may comprise mounting the virtual machine image's virtual hard disk drives. An analysis engine is invoked to scan the exposed file-system data to determine the update status of software constructs of the virtual machine image and data indicative of the scanning may be stored. The virtual machine image may be updated while inactive or may be deployed and activated in a protected environment for updating.

Abstract: Methods and systems for scanning a virtual machine image. The virtual machine image may be stored as a collection of one or more virtual hard disk files. The virtual machine image may be stored by taking the virtual machine off-line or may be stored by taking a checkpoint of the virtual machine while the virtual machine is on-line. The virtual machine image is rendered to file-system data. Rendering the virtual machine image to file-system data may comprise mounting the virtual machine image's virtual hard disk drives. An anti-malware engine is invoked to scan the exposed file-system data, and data indicative of the scanning may be stored.

Abstract: A virtual machine may be discovered through a directory service or via an agent that is installed on the host operating system that is running the virtual machine. If the agent is installed on the virtual machine, the agent monitors changes to a set of protected volumes on the virtual machine. If the agent is installed on the host, the agent monitors changes to the protected volumes, which may contain one or more virtual servers on the host. Periodically, these changes from the host or the virtual server are sent to a data protection server. The data protection server updates its replicas of protected volumes with the sent changes. Versions of files on a data protection server corresponding to a volume of a virtual server may be restored to the virtual machine, to another machine, or may be viewed from the data protection server.

Abstract: A method and system for backing up and restoring data of virtual machines. A virtual machine may be discovered through a directory service or via an agent that is installed on the host operating system that is running the virtual machine. If the agent is installed on the virtual machine, the agent monitors changes to a set of protected volumes on the virtual machine. If the agent is installed on the host, the agent monitors changes to the protected volumes, which may contain one or more virtual servers on the host. Periodically, these changes from the host or the virtual server are sent to a data protection server. The data protection server updates its replicas of protected volumes with the sent changes. Versions of files on a data protection server corresponding to a volume of a virtual server may be restored to the virtual machine, to another machine, or may be viewed from the data protection server.

Abstract: A backup administrator can backup files from a production server on any of a plurality of different bases. In particular, some files can be replicated on a changed-byte basis. In other cases, files can be backed up by replicating updated copies of the entire file, or even byte blocks of the file. Determinations as to how a replication agent will back up a certain file or set of files can be made by a backup administrator, automatically through a predefined logic, or dynamically based on defined criteria. Corresponding agents at the production server can then flag these files as indicated. Thus, at a later point, when the DPM server requests the updates of each file, the production server can either send over copies of the changed file bytes, entire copies of the changed file itself, or even changed blocks of a file, as appropriate.

Abstract: Physical (or prior virtual) machine volumes can be converted to virtual machines at a virtual machine host while the physical machines are running. In one implementation, a volume shadow copy service can be used to create an application (and/or file system)-consistent snapshot of one or more physical machine volumes while the one or more volumes are running. The snapshot data can then be transferred to a mounted virtual hard disk file (dynamic or fixed) at a virtual machine host. Operational information (e.g., boot record, system registry, drivers, devices, configuration preferences, etc.) associated with the virtual hard disk file and the operating system(s) within the virtual machine can then be modified as appropriate to ensure that the corresponding virtual machine is bootable and functional at the virtual machine host. The virtual hard disk file can then be un-mounted, and used as a new virtual machine.

Abstract: A method and system for backing up and restoring data of production servers. A mapping that maps volumes of production servers to volumes of a data protection server is maintained on the data protection server. When volumes of the data protection server are backed up, the mapping may be stored on the archive media together with the data of the volumes. Later, during a restore, the mapping is read from the archive media. The mapping allows the data to be restored to the data protection server or directly to the production servers.

Abstract: Methods and systems for updating a virtual machine image. The virtual machine image may be stored as a collection of one or more virtual hard disk files. The virtual machine image is rendered to file-system data. Rendering the virtual machine image to file-system data may comprise mounting the virtual machine image's virtual hard disk drives. An analysis engine is invoked to scan the exposed file-system data to determine the update status of software constructs of the virtual machine image and data indicative of the scanning may be stored. The virtual machine image may be updated while inactive or may be deployed and activated in a protected environment for updating.

Abstract: Migration mechanisms are disclosed herein that smartly transfer data among virtual machines, minimizing the down time of migration of such machines but maximizing the consistent state of data stored thereon. Specifically, data can be classified into three types: low volatility data (such as hard disk data), high volatility data (such a random access memory data), and immutable data (such as read only data). This data can be migrated from a source virtual machine to a target virtual machine by sending the immutable data along with the low volatility data first—before the source virtual machine has stopped itself for the migration process. Then, after the source virtual machine has stopped, high volatility data and (again) low volatility data can be sent from the source to the target. In this latter case, only differences between the low volatility data may be sent (or alternatively, new low volatility data may be sent).

Abstract: Methods and systems for scanning a virtual machine image. The virtual machine image may be stored as a collection of one or more virtual hard disk files. The virtual machine image may be stored by taking the virtual machine off-line or may be stored by taking a checkpoint of the virtual machine while the virtual machine is on-line. The virtual machine image is rendered to file-system data. Rendering the virtual machine image to file-system data may comprise mounting the virtual machine image's virtual hard disk drives. An anti-malware engine is invoked to scan the exposed file-system data, and data indicative of the scanning may be stored.