HyperV WinAPI: Backup and Restore Strategies

Enterprise

Bacula Enterprise Only

This solution is only available for Bacula Enterprise. For subscription inquiries, please reach out to sales@baculasystems.com.

Standalone Mode

In this mode, each host hypervisor runs a bacula client and the hyper-V WinAPI plugin. Only the VM’s running on a given node can be backed up, by creating a consistent VM image via a snapshot. If the VM’s are migrated into another node, the respective VM backup will be promoted to full.

Cluster Mode

Note

The Hyper-V WinAPI Plugin exclusively supports local VMs. Therefore, remote VMs are automatically migrated to the local node, backed up, and then migrated back to their original node. For more information, refer to the Backup section.

Backup remains seamless in a Failover Cluster setup, regardless of the hosting node for the VM(s) during backup. As long as the user possesses the appropriate credentials on all nodes, the VMs within the cluster will undergo filtering via include/exclude criteria. Remote VMs will be automatically Migrated to the local node, backed up, then restored to it’s original node. Hyper-V does not permit VM migration between nodes during backup operations.

See also

Previous articles:

• HyperV WinAPI: Scope

• HyperV WinAPI: Features

Next articles:

• HyperV WinAPI: Installation

• HyperV WinAPI: Configuration

• HyperV WinAPI: Operations

• HyperV WinAPI: Limitations

• HyperV WinAPI: Troubleshooting

Go back to: Hyper-V WinAPI Plugin.