Security Compliance

Reserve RAM in Hyper-V for SEM

Security Event Manager (formerly Log & Event Manager) requires memory (RAM) reservations. SEM requires ALL of the allocated memory to be reserved in the Microsoft Hyper-V environment.

First published date

10/16/2018 6:50 PM

Last published date

5/14/2019 2:04 PM

Overview

Security Event Manager (formerly Log & Event Manager) best practice requires memory (RAM) reservations. SEM best practices require ALL of the used memory to be reserved in the hypervisor at a minimum while the best practice recommendation would be for the full allocated amount to be reserved.

Product section

Security Event Manager

Resolution

In the example above, 48GB of memory has been allocated to SEM. We have enabled Dynamic Memory and set 48GB as the minimum, in this case, SEM will not use any more than 48GB.

Note: The Maximum memory value will be ignored.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.