none
SCOM Virtual RMS Server

    Question

  • Does anyone use their RMS server as a VM Machine? if so what are the specs you used? Processor allocation, memory, harddisk space, etc?
    Paul Arbogast
    Friday, July 15, 2011 8:49 PM

Answers

  • Here are the specs i have.
    RMS:
    2vCPU
    6GB Memory
    MS: 2vCPU
    6GB Memory

    Around 600 agents. Running with out any issue.

    hope this helps.  


    Orhan Taskin
    • Marked as answer by parbogast Monday, July 18, 2011 3:16 PM
    Saturday, July 16, 2011 4:25 AM
  • It's possible to get acceptable performance out of your virtualized RMS, but in general it's not a great virtualization candidate.  If you must go this route, there are a couple things to keep in mind.

    1. Ensure you have a dedicated, non-shared disk attached to the RMS where you can locate the Health Service State directory.  There is a jet database hosted in this directory that has the IO characteristics of an OLTP database, so we need to support a high volume of transactions on this disk.  This is a common bottleneck in many environments, and isn't a very well documented recommendation.

    2. Ensure the CPU priority is set accordingly.  If the VMHost isn't able to allocate CPU to the RMS when the RMS needs it, you may wind up sufficating the RMS and other issues will likely surface.

    3. Usually NIC isn't a bottleneck from my experience, but virtualizing the RMS could potentially bubble up some network utilization issues.  Similar to #2 above, make sure the RMS doesn't suffer from narrowed network access.


    HTH, Jonathan Almquist - MSFT
    Saturday, July 16, 2011 2:56 PM

All replies

  • We've run ours on VmWare for some time now.  2 vCPU (HP DL480 Blades are our ESX hosts), 4 GB RAM, 40 GB drive.  Typically runs at about 60% utilized on the proc/memory.  Granted, we only have 50 or so agents reporting to it, while most report to a management server.  You'll have to take your agent count into consideration more than anthing (and your console connections), especially if it is the only SCOM server in your enviornment.
    Friday, July 15, 2011 9:00 PM
  • Here are the specs i have.
    RMS:
    2vCPU
    6GB Memory
    MS: 2vCPU
    6GB Memory

    Around 600 agents. Running with out any issue.

    hope this helps.  


    Orhan Taskin
    • Marked as answer by parbogast Monday, July 18, 2011 3:16 PM
    Saturday, July 16, 2011 4:25 AM
  • It's possible to get acceptable performance out of your virtualized RMS, but in general it's not a great virtualization candidate.  If you must go this route, there are a couple things to keep in mind.

    1. Ensure you have a dedicated, non-shared disk attached to the RMS where you can locate the Health Service State directory.  There is a jet database hosted in this directory that has the IO characteristics of an OLTP database, so we need to support a high volume of transactions on this disk.  This is a common bottleneck in many environments, and isn't a very well documented recommendation.

    2. Ensure the CPU priority is set accordingly.  If the VMHost isn't able to allocate CPU to the RMS when the RMS needs it, you may wind up sufficating the RMS and other issues will likely surface.

    3. Usually NIC isn't a bottleneck from my experience, but virtualizing the RMS could potentially bubble up some network utilization issues.  Similar to #2 above, make sure the RMS doesn't suffer from narrowed network access.


    HTH, Jonathan Almquist - MSFT
    Saturday, July 16, 2011 2:56 PM