Just to clarify, Adai, when you say "currently whatever you see," do you mean what I currently just pointed out, namely, the "chargeback," "autosupport," and "cpu," can be turned off? If so, we have a growing list of the following that can be disabled when we separate out DPM from DFM/PA:
agentMonInterval
ccMonInterval
envMonInterval
hostMonInterval
SANHostMonInterval
srMonInterval
userQuotaMonInterval
autosupportMonInterval
cpuBusyThresholdInterval
cpuMonInterval
Here are some more that I think could be turned off:
aggrFullThresholdInterval
qtreeFullThresholdInterval
volFullThresholdInterval
Since these would be monitored on another server, why would we need to have 2 monitoring "copies"? Does DPM use these in any way? To my knowledge, these threshold values are for event generation only and have nothing to do with informing DPM of volume, qtree, or aggregate utilization. If I were to guess, when creating a dataset, DPM makes ZAPI calls to the filer to get its usage numbers before making its conformance calculations.
licenseMonInterval
ndmpMonInterval
Now, I know that the NMC, and thus DPM, uses ZAPI calls to get license and ndmp status information and not from the polling that DFM does, so I don't see that these are necessary as well.
cfMonInterval
clusterMonInterval
These, again, don't seem to have anything to do with DPM.
perfAdvisorPollInterval
perfAdvThreshViolationMonInterval
I would guess that if you disabled Performance Advisor, these would either disappear, or would automatically be disabled, at least in practice and thus would not need to be bothered with, but you never know.
I know you dealt with this sort of thing in the thread: http://communites.netapp.com/messages/55322 . You gave an excellent list of options to trun off for a dedicated Performance Advisor server. What I'm looking for is the same thing except for a dedicated DPM server.
Thanks alot for your help Adai!