Problems with generating backup of a VM

Alan Ernesto Mondragón Ramírez 5 Reputation points
2024-01-29T06:44:15.1933333+00:00

The error occurs consistently after the backup generation process takes approximately 4 hours, during which shortly after that time it fails, and within the alert details, it shows the following information: Please check for disk space exhaustion, high CPU load, disk resource usage, memory usage and swap space etc. Please retry the operation after ensuring there is no resource contention issue on the Virtual Machine. However, even after making these changes, it still doesn't work. I also found that perhaps the type of security I have could be affecting it since it is Trusted launch, but I really don't know what to do anymore. I hope you can help me

Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,170 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Saravanan Ganesan 1,745 Reputation points MVP
    2024-01-29T19:36:52.1033333+00:00

    Hi Alan ,

    Consistent errors during a 4-hour backup generation point to potential resource contention issues on the Virtual Machine (VM). Despite addressing disk space, CPU load, and memory concerns, the problem persists. Trusted launch security might be a factor. Verify if security configurations, like Trusted Launch, impact backup processes. Consider adjusting security settings, monitoring VM metrics, and consulting Azure support. Additionally, review backup policies, scheduling, and consider optimizing the backup process for efficiency. For better Support and Understanding try to connect with Azure Support team by raising a request in your Azure portal under Azure VM section . https://video2.skills-academy.com/en-us/azure/virtual-machines/ check this link to know more about Azure VM related contents or topics. Regards,
    Saravanan Ganesan.

  2. Rubens Gonçalves de Araujo 0 Reputation points
    2024-01-31T14:34:49.7866667+00:00

    Problem solved for me. Verified that this issue is generated by a configuration in the Azure VM agent. In my case Linux Debian 12.

    Change the parameter below from n to y (n is default value) in /etc/waagent.conf file extensions.enabled= y

    It's necessary to stop and start the agent service (do not use restart command).

    • systemctl stop walinuxagent.service
    • systemctl stop waagent.service
    • systemctl start walinuxagent.service
    • systemctl start waagent.service
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more