After much back and forth, support/AI could only suggest to reduce the repository machine swappiness value or increase swap space.
We increased swap however this again spiked to 90% in the last couple of days - our opinion is neither of these should really need to be completed following a v12-v13 upgrade, as this would be masking the underlying problem even if it did resolve the issue.
Luckily this is not impacting backup jobs, purely alerting - but there is an inherent issue in the v13 codebase here (Veeam support/AI agreed it was Veeam processes causing the swap spike).
Our opinion stands - hold off upgrading v13 for environments with RHEL hardened repositories!
We increased swap however this again spiked to 90% in the last couple of days - our opinion is neither of these should really need to be completed following a v12-v13 upgrade, as this would be masking the underlying problem even if it did resolve the issue.
Luckily this is not impacting backup jobs, purely alerting - but there is an inherent issue in the v13 codebase here (Veeam support/AI agreed it was Veeam processes causing the swap spike).
Our opinion stands - hold off upgrading v13 for environments with RHEL hardened repositories!
Statistics: Posted by lharmer — Apr 24, 2026 8:18 am
