5.5

To apply changes that you make to advanced settings to virtual machines that you have already protected,
you must reconfigure protection for those virtual machines individually. You can also remove the protection
from the virtual machine by removing it from a protection group, and then reconfigure protection by
adding it back in the protection group.
Change Local Site Settings
SRM monitors consumption of resources on the SRM Server host, and it raises an alarm if a resource
threshold is reached. You can change the thresholds and the way that SRM raises the alarms.
Procedure
1 Click Sites in the SRM interface, right-click the site on which to change settings, and select Advanced
Settings.
2 Click localSiteStatus.
3 Change the settings as needed.
Option Action
Change the interval at which SRM
checks the CPU usage, disk space,
and free memory at the local site
Type a new value in the localSiteStatus.checkInterval text box.
Change the name of the local site
Type a new value in the localSiteStatus.displayName text box.
Change the timeout during which
SRM waits between raising alarms
about CPU usage, disk space, and
free memory at the local site
Type a new value in the localSiteStatus.eventFrequency text box.
Change the percentage of CPU
usage that causes SRM to raise a
high CPU usage event
Type a new value in the localSiteStatus.maxCpuUsage text box.
Change the percentage of free disk
space that causes SRM to raise a
low disk space event
Type a new value in the localSiteStatus.minDiskSpace text box.
Change the amount of free memory
that causes SRM to raise a low
memory event
Type a new value in the localSiteStatus.minMemory text box.
4 Click OK to save your changes.
Change Logging Settings
You can change the levels of logging that SRM provides for the SRM Server components.
SRM Server operates log rotation. When you restart SRM Server, or when a log file becomes large,
SRM Server creates a new log file and writes subsequent log messages to the new log file. When SRM Server
creates new log files, it compresses the old log files to save space.
You might reduce the logging levels for some SRM Server components because log files become too large
too quickly. You might increase logging levels for certain components to help diagnose problems. The list of
available logging levels is the same for all SRM Server components.
none
Turns off logging.
quiet
Records minimal log entries.
panic
Records only panic log entries. Panic messages occur in cases of complete
failure.
Chapter 9 Advanced SRM Configuration
VMware, Inc. 83