Hi all,
We have a Virtual Veeam Server in Azure with 16GB Ram. I noticed that the Server stops responding and shuts down.
The log files show that we have a RAM issue. My question, is there a workaround for this issue, cause we cant add more ram in Azure.
Recommendations are highly appreciated, thanks
EventID 2004 Microsoft-Windows-Resource-Exhaustion-Detector
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Veeam.Archiver.Proxy.exe (916) consumed 19371589632 bytes, MsMpEng.exe (3588) consumed 192774144 bytes, and Veeam.Archiver.Service.exe (2064) consumed 164884480 bytes.
-
- Influencer
- Posts: 16
- Liked: never
- Joined: Sep 01, 2020 7:52 am
- Full Name: Stephen Künzle
- Contact:
-
- Product Manager
- Posts: 8220
- Liked: 1333 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: EventID 2004 Microsoft-Windows-Resource-Exhaustion-Detector
@dontlikemondays
How many users / jobs and so on are you running? 16GB is not a lot for the VBO server, but depending on the size of the organization, it should be enough.
How many users / jobs and so on are you running? 16GB is not a lot for the VBO server, but depending on the size of the organization, it should be enough.
-
- Influencer
- Posts: 16
- Liked: never
- Joined: Sep 01, 2020 7:52 am
- Full Name: Stephen Künzle
- Contact:
Re: EventID 2004 Microsoft-Windows-Resource-Exhaustion-Detector
4 Jobs, 1200 Users, 8 Backup Accounts
Maybe thats the hint i was looking for, i can tune the jobs
Maybe thats the hint i was looking for, i can tune the jobs
-
- Product Manager
- Posts: 5901
- Liked: 1235 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: EventID 2004 Microsoft-Windows-Resource-Exhaustion-Detector
You can always find more information in the best practices guide.
GitHub: https://github.com/nielsengelen
Who is online
Users browsing this forum: StephanG and 21 guests