Skip to main content

Out of RAM error

Thread needs solution

We're having an odd problem with our HC3 environment. Our virtual agent VM is assigned 2 cores and 8GiB assigned. Months ago we had an error about an Agent being out of RAM so we upped it to 12GiB. Hopefully that didn't cause issues with the swap file size since I know Linux goes nuts over that. And just yesterday we got the error again:
Activity 'Backing up virtual machine disks' failed. Failed to complete the operation because the process ran out of RAM.

I do have "limit to 2 concurrent backups" on for each plan and I can limit it to 1 but we also have about 400GiB of unused RAM on on that cluster so we can assign whatever we want for that agent, if that's actually the problem. The documentation strongly suggests we wouldn't need more than 8GiB.

So can this error show up if the VM it's backing up doesn't have sufficient RAM? Or if the Windows VM that Acronis Cyber Protect it installed on is out of RAM? Also, does upping the RAM on the Acronis Agent VM actually work or is it dangerous to exceed the available space of the already set up swap partition? I'm not a knowledgeable Linux person but I know Windows can handle a mismatched page file size as long as you never run out of RAM or it's expandable but no idea how Linux handles it.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Hello!

The error typically occurs when the virtual appliance or host runs out of memory, usually due to overloading.

To address this issue, please consider the following troubleshooting steps:

1. Swap Space: Linux employs swap space as virtual memory when physical RAM is exhausted. If you've significantly increased the RAM allocation for the Agent VM, ensure that the swap space is appropriately configured to accommodate this change. If necessary, you can increase the swap space. However, please note that increasing swap space may not always resolve the problem, as it's essential to identify the root cause of excessive memory usage.

2. VM RAM Allocation: Examine the RAM allocation for the virtual machines you intend to back up. If a virtual machine doesn't have sufficient RAM allocated, it can lead to memory-related issues during backup operations. Make sure that the VMs being backed up have adequate RAM for their workloads.

3. System Overloading: Attempt to reschedule the backups to a time when the host isn't in production or overloaded. Consider backing up one VM at a time and schedule the backups for different hours to alleviate the resource burden.

Please also check this KB and if the appliance has enough RAM: https://kb.acronis.com/content/68686

I also advise you to take a look over this KB, it may be related with the issue you face and this can also be the solution: https://kb.acronis.com/content/68544

If the issue persists, please raise a ticket with our support at https://kb.acronis.com/content/8153.

Best regards.

 

Thanks for the great info! I may resort to only allowing one backup at a time but since we have 1006GiB of RAM on our host with 480 used, I'm upping the Agent's RAM allocation to the "you should never need the swap partition" amount of 24GB to see if that helps (and not touching the swap file size for now because it'd require resizing it virtually then attempting to resize the partition and I only know how to do that quickly in Windows). Also, it just always seems to happen on our File Server #3 which is truly enormous and only has 12GB of RAM so I'm tweaking that to be a lot higher tonight too. I think between the two, it ought to work. I'll keep you posted.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

CEC-P wrote:

Thanks for the great info! I may resort to only allowing one backup at a time but since we have 1006GiB of RAM on our host with 480 used, I'm upping the Agent's RAM allocation to the "you should never need the swap partition" amount of 24GB to see if that helps (and not touching the swap file size for now because it'd require resizing it virtually then attempting to resize the partition and I only know how to do that quickly in Windows). Also, it just always seems to happen on our File Server #3 which is truly enormous and only has 12GB of RAM so I'm tweaking that to be a lot higher tonight too. I think between the two, it ought to work. I'll keep you posted.

Hello!

Thank you for the reply.

Feel free to update the thread, this may help the other users.

Best regards!