Virtual Memory completely used with scheduled backups


My last scheduled backups couldn’t be done successfuly, and I see my virutal memory is 100% used

Output free -m
total used free shared buff/cache available
Mem: 31942 2850 312 524 28779 28112
Swap: 1021 1021 0

glances warn that :

High CPU I/O waiting
(ongoing) - CPU_IOWAIT (9.7)
(0:00:09) - CRITICAL on CPU_IOWAIT (Min:7.9 Mean:9.9 Max:11.5): mysqld, clamd, systemd-journald
(0:00:12) - CRITICAL on CPU_IOWAIT (Min:7.5 Mean:8.5 Max:9.3): mysqld, clamd, systemd-journald
(ongoing) - MEMSWAP (100.0): mysqld, clamd, systemd-journald

What can I do to resolve this problem ?
The size of the backup (all my virtual servers) is 192Gb

Thanks in advance :slight_smile:

Finally my scheduled backup have done in 11 hours, 19:48 minutes. Habitually that take 2 hours.

I’m reading 32gb total memory and 1gb swap. I like that ratio but I think you had an out-of-memory problem, not a swapping problem. It’s been 12 hours since your initial post so is the server more relaxed now?

yes the server is now better fine

free -m
total used free shared buff/cache available
Mem: 31942 2936 429 602 28576 27950
Swap: 1021 436 585

No warning or critical alert detected on glances

But still 28 gb memory in buff/cache, this is a problem ?

Thank you

Something won’t let go of memory which could be a problem during or after your next backup. One reason for having plenty of memory is surplus elbow room.

Maybe this is helpful:

I tend to agree with the ‘zero-swap’ opinions, especially for high memory systems like yours. Not that getting rid of swap will free up memory, it’s just one less thing to worry about.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.