Comprehensive data protection for all workloads
Post Reply
lharmer
Service Provider
Posts: 32
Liked: 3 times
Joined: May 05, 2016 2:09 pm
Contact:

Excessive Swap Usage - Hardened Linux Repository

Post by lharmer »

Case #08005386

Since upgrading to v13 we have seen excessive swap usage on a Linux Hardened repository.

Support has just confirmed this as a known issue:
High swap space usage on RHEL repositories with Veeam v13 is a known issue that is currently under investigation. At this time, there is no confirmed root cause or official fix.
Restarting the veeamtransport service or rebooting the server will temporarily clear swap usage; however, the issue is expected to recur until a permanent solution is released. While there is no confirmed memory leak, increased memory consumption by veeamtransport has been observed in some environments after upgrading to v13.0.1.180 or later, particularly with Linux Hardened Repositories.


Maybe hold off upgrading if you haven't already :wink:

Anyone from Veeam got eyes on when this will be fixed? Assuming it will be in the next release?
david.domask
Product Manager
Posts: 3406
Liked: 807 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: Excessive Swap Usage - Hardened Linux Repository

Post by david.domask »

Hi lharmer,

Thanks for sharing the case details, and sorry to hear about the challenges.

Reading the case, I think there was a slight misunderstanding as Support writes that the behavior has been observed, but root cause is still under investigation.

Please continue with Support on a root cause; if you have concerns about the handling of the case, use the Talk to a Manager button from the case portal to connect with Support Management. Support Management will review your case and allocate additional resources if required.
David Domask | Product Management: Principal Analyst
lharmer
Service Provider
Posts: 32
Liked: 3 times
Joined: May 05, 2016 2:09 pm
Contact:

Re: Excessive Swap Usage - Hardened Linux Repository

Post by lharmer »

Hi David,
Thanks, support advised:
At this point, that should be everything needed. Since the issue has already been identified and is currently being addressed, we will need to wait for the release of the fix.

I've offered to work with support on a root cause but seems... they don't need my help!
Post Reply

Who is online

Users browsing this forum: Google [Bot], Semrush [Bot] and 52 guests