Skip to main content

Hi all. I can't solve the problem. There is Veeam 9.5. There is a host on winserver2012r2. Inside the host is a virtual machine on Hyper-V with WinServer2012r2. When Veeam makes a backup, the virtual machine is frozen, that is, it does not turn off, the time counter does not stop. But the user is thrown out of the server, there is no ping. On the virtual machine, the role of the Domain Controller.
1. Integration services updated
2. Transferred to a separate task at another time that is not loaded
3. Turned off the queue on the network card on the host. The virtual switch did not recreate after that

The task starts at 22.15. Below Hyper-V-VMMS Event

Error. The normal state of the workflow is essential for the functioning of the virtual machine "RUVLD6ADSM01" (virtual machine ID BC4668C5-23A4-42E0-97BA-DB09654396FC).
Intelligence. The worker process is now in normal state for VM "RUVLD6ADSM01" (VM ID BC4668C5-23A4-42E0-97BA-DB09654396FC).
Error. Metrics Service failed to manage metrics for ManagedElement="\\RU01\root\virtualization\v2:Msvm_ComputerSystem.CreationClassName="Msvm_ComputerSystem",Name="BC4668C5-23A4-42E0-97BA-DB09654396FC"" and MetricDefinition="": Generic failure. (0x80041001).
Intelligence. Disk merge "RUVLD6ADSM01" has been started in the background. (Virtual Machine ID BC4668C5-23A4-42E0-97BA-DB09654396FC)

Please tell me about the problem

Are you able to upgrade Veeam to the latest 11A release?  That may potentially fix this since 9.5 is fairly old.  Not an expert on Hyper-V but hopefully others will chime in.

Here is 11A link for info - KB4215: Release Information for Veeam Backup & Replication 11a

Download of ISO - KB4245: Release Information for Veeam Backup & Replication 11a Cumulative Patches

Be sure your instance is on U4B before upgrading if you go that route.


I agree with you, first of all, update to the latest version.

also, if its a production environment, please open a case, if you have support, its included and they will track and help you out with all the experience and based on your environment!

cheers,


Yeah, I can confirm the 9.5 is likely unsupported. Please see the lifecycle page: Veeam Product Lifecycle

 

After an upgrade; I recommend re-testing or contacting support. 


Hello friends!
Thank you for your responses.
The license was purchased for 9.5, the purchase of a new license is not planned.
Technical support has ended.
Is it possible to fix the problem in my version 9.5?


Hello friends!
Thank you for your responses.
The license was purchased for 9.5, the purchase of a new license is not planned.
Technical support has ended.
Is it possible to fix the problem in my version 9.5?

You could try with the community edition (free capabilities) in newer versions. Or use the Agent in the guest VM.


Hello friends!
Thank you for your responses.
The license was purchased for 9.5, the purchase of a new license is not planned.
Technical support has ended.
Is it possible to fix the problem in my version 9.5?

You could try with the community edition (free capabilities) in newer versions. Or use the Agent in the guest VM.

or 30 day trial version of 11 , see if it resolves your issue ..if it does, justification to buy v11 licenses right there


I hope you will also be upgrading your winser2012r2 in the near future?! 


Hi!

For my problem.
1. Yesterday the scheduled task started and everything went fine, without loss of connection.
2. If you uncheck the aware-application flag, the task works correctly
3. With the help of hyper-v, I launched the creation of a control point. Connection was lost
4. After the checkpoint, I run a veeam task and it froze the virtual machine while running

5. Backup using the agent did not start

In Hyper-V-VMMS events
- The task passed without loss of communication
2 events:
 Disk merge "RUVLD6ADSM01" has been started in the background. (Virtual Machine ID BC4668C5-23A4-42E0-97BA-DB09654396FC)
 Merge disks "RUVLD6ADSM01" in the background successfully completed. (Virtual Machine ID BC4668C5-23A4-42E0-97BA-DB09654396FC)

-The task was completed with a loss of communication
4 events:
 The normal state of the workflow is essential for the functioning of the virtual machine "RUVLD6ADSM01" (virtual machine ID BC4668C5-23A4-42E0-97BA-DB09654396FC).
 The worker process is now in normal state for VM "RUVLD6ADSM01" (VM ID BC4668C5-23A4-42E0-97BA-DB09654396FC).
 The normal state of the workflow is essential for the functioning of the virtual machine "RUVLD6ADSM01" (virtual machine ID BC4668C5-23A4-42E0-97BA-DB09654396FC).
The worker process is now in the normal state for VM "RUVLD6ADSM01" (VM ID BC4668C5-23A4-42E0-97BA-DB09654396FC).

It turns out that my virtual machine is not in the correct state for backup?
Generation: 2
Version 5.0.
Integration Services all updated


I hope you will also be upgrading your winser2012r2 in the near future?! 

We do not plan


Comment