Memory Overcommitment and Backup-Induced VM Downtime

Memory Overcommitment and Backup-Induced VM Downtime

emilyjohnson63	February 3, 2025, 10:44 am \| Post: 3
Group: Member Post Group: Newbie Posts: 1 Status:	It sounds like even though the VMs aren't using all 10GB normally, the hypervisor (Virtualizor in this case) is still reserving or allocating that full amount to them, just in case. When the backups kick in and they do need it, the host is scrambling to find enough RAM to give them all their allocated amounts at the same time, which is why they're crashing. Clearing cache won't help because it's not about cached data, it's about the reserved RAM. You've basically over-promised RAM that the host doesn't physically have when everyone needs it at once. You probably need to either reduce the overcommitted RAM allocation for each VM (maybe 6GB or 8GB instead of 10GB) or stagger the backups so they don't all run at the same time. That way the host has enough RAM to go around. It might also be worth checking if Virtualizor has any settings related to memory ballooning or dynamic memory allocation – those might help, but no guarantees.
IP: --

Users viewing this topic
	1 guests, 0 users.