Limitations to HyperBack tasks for Hyper-V cluster environment

Summary

When installing ActiveImage Protector 2022 on a Hyper-V cluster node and setting up HyperBack tasks for clustered virtual machines, note the following limitations if a virtual machine disk moves to a different node during failover.

* This issue was fixed in AIP 2022 (7.0.0.8643) and later versions. This limitation is no more applicable.

Creating HyperBack tasks for four virtual machines in this situation successfully completes.

During failover, the task for a green-checked virtual machine successfully finishes.

Workaround

1)  Create a new virtual machine for HyperAgent. Install ActiveImage Protector using the HyperAgent key and configure HyperBack settings.

2) Install ActiveImage Protector on an existing virtual machine. Use the HyperAgent key and set up HyperBack configurations. 

3) Install ActiveImage Protector on a machine not in Hyper-V cluster-configured nodes. Use the HyperAgent key to install AIP and configure HyperBack settings.

4)  Install ActiveImage Protector on the relevant virtual machines and set up scheduled backup tasks for each.

Target Product

- ActiveImage Protector 2022 (6.5.0.7616) or earlier

16557926086809