Hyper-V Virtual Machine showing not protected after the virtual server live migrated to another host

Dear All,
We have a 4 nodes hyper-v cluster with virtual servers. Now the Backup plans are based on the server function group we created by ourselves. But, once a server is migrated to another Hyper-v Host, it will shows the status as "Not Protected", we understand this is due to the migration which make the system think there is a new virtual server join in the hosting node.
The purpose of our own created server group by function is that we don't want to backup all the server every day, or every week, we need to backup them by their function, some of the server need to be everyday, some of the server only once a month is ok (because there is no data change on it.)
But during the operation, we found it is difficult to manage the backup like this, because each time a virtual server is migrated to a new node, it will be recognized as a new virtual server to that host node, the status will be come "Not protected".
What option do we have?
Thanks,

- Log in to post comments

Hi,
The issue with loss of protection status for VM after migration across Hyper-V cluster should be fixed in the latest Acronis Backup 12.5 Update 4. The root cause of it is in the process of passing control over VM between different agents where this process was not inheriting the protection status of the VM (internal bug ID: ABR-214266). If you still see this behavior with Update 4, then it should be investigated with our support team involved as there could be some other cause.
Thank you.
- Log in to post comments

Dear Vasily,
I uploaded the version number of my Acronis Backup Server, is it the newest one?
Attachment | Size |
---|---|
504474-169829.PNG | 3.98 KB |
- Log in to post comments

Hi Jason,
Yes, it is the correct version for Update 4, so the issue should be some new one (could be related to environment specifics) which needs further investigation. Please contact our support team for proper analysis. Remember to capture Acronis system reports from both management server and the backup agents (at least source + target agent which correspond the Hyper-V hosts the VM was migrated between).
Thank you.
- Log in to post comments

Hi Vasily,
I used another method for this situation now, just backup the whole cluster with the same backup policy, as long as the server is in the cluster, then it is fine.
thanks,
- Log in to post comments