PFM - Manager affects the entire Performance Management system when it stops.

PFM - Manager centrally manages the agent information of the PFM - RM for Microsoft SQL Server agents that are running on all nodes. It also controls notification of alarm events in the event a threshold value is exceeded during performance monitoring by PFM - RM for Microsoft SQL Server as well as execution of actions based on alarm events. Accordingly, when PFM - Manager stops, the entire Performance Management system is affected, as described in Table 3-1.

Table 3-1 Effect on PFM - RM for Microsoft SQL Server when PFM - Manager stops

Program name	Effects	Solution
PFM - RM for Microsoft SQL Server	If PFM - Manager stops while PFM - RM for Microsoft SQL Server is running, PFM - RM for Microsoft SQL Server: Continues collecting performance data. Retains alarm events for each alarm definition and retries until PFM - Manager is recovered if it cannot send the alarm events to PFM - Manager. When the number of retained alarm events exceeds 3, the oldest alarm event is overwritten. If PFM - RM for Microsoft SQL Server is stopped, all the alarm events that have been retained are deleted. Resets, when PFM - Manager is restarted, the alarm statuses that have already been reported to PFM - Manager. The alarm statuses are then initialized after checking with PFM - RM for Microsoft SQL Server. Takes a long time to stop if you attempt to stop it, because PFM - Manager cannot be notified.	Start PFM - Manager. You can continue to run any PFM - RM for Microsoft SQL Server that is currently running. Check the common log after PFM - Manager is recovered because alarms may not be reported exactly as expected. (KAVE00024-I)

Consider the effects of stopping PFM - Manager when considering how to operate Performance Management. There are times when you have to stop PFM - Manager in order to change the configuration or perform maintenance work. Hitachi recommends that you schedule maintenance work for times that will have the least impact on operations.