DFM perfdata expands. How to decrease the perfdata size?

[MARIKOTAGAWA]

Hi, all.

Our server monitoring system alarmed that my DFM server's disk is reaching full.

I took a look at disk usage under  /opt/<DFM install dir> then found /perfdata consumes 48G.

$ sudo du -s -h *

48G     perfdata

How can I decrease the perfdata directory size significantly? Could you instruct me a standard steps or give a document link explains the method?

Under /perfdata, there are old files which time stamp is older than 1.5 years but those files are quite small. The total size of filers which time stamp is about 50MB.

New time stamp files consumes the space because some of them are larger than 2GB per 1 file.

I checked NMC -> Setup -> Host -> data collection -> Edit

Most objects' setting are below. As I didn't change this setting, this is the default setting. If I change this retention period to 6 months, perfdata decrease?

sample period          retention period

1 min                         1.02 year

Thank you in advance.

Mariko

[bwes]

Hi Mariko

You are correct that if you change the data collection retention that you will reduce the perfdata folder size. This can be changed in performance monitor per filer and per counter. If you look under "Data Collection" you will see what the current retention for each node and counter currently is.

Be aware also that if you have less than 10% available space where your perfdata folder is stored, that DFM will stop data collection.

Regards,

Wes

[MARIKOTAGAWA]

Hi, Wes Beckhum.

Sorry for the late reply, as I'm currently traveling.

I'll try to adjust the data retention period and see how much it will reduce the perfdata size.

Thanks.

Mariko

[kryan]

Hi Mariko,

It would help to know the DFM/UM version you are running as there is a perfdata large file bug that is resolved via automatically workaround in UM Core 5.0+.

Thanks,

Kevin

[MARIKOTAGAWA]

hi, kryan.

Sorry for the late reply. I'm currently traveling.

My DFM version is 5.1.

Best Regards,

Mariko

[saranraj456]

do you have the bug details ?

we had a similar kind of problem , one single file is showing as around 1.5GB in dfm perf data output but the actual size of the file in perfdata directory was around 17GB

lun	netapp1-ctl2	perf_9_78_881
6	8509 1.54 GB	718 MB

Saran

[kryan]

The bug I referred to was 439756, but it is not applicable to any supported version (UM 5.0+):

http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=439756

Thanks,

Kevin

[saranraj456]

I don’t how far the bug is related to my case , perf_9_78_8816 a single file occupying more than 17 GB however we haven’t done any modifications like adding or removing recently.

[saranraj456]

i wonder one thing the dfm perf data list -v output is showing a value different than the perfdata directory actual file size

Saran

[saranraj456]

DFM verison is -4.0

[kryan]

Saran,

Being on DFM 4.0 means you are both exposed to 439756 and that you need to upgrade as all versions of DFM/UM prior to 5.0 entered End Of Version Support as of 12/1/2013:

https://support.netapp.com/info/web/ECMP1147223.html

Additionally, there is a bug that prevents the command "dfm perf data list -v" from accurately representing data files larger than 4Gb (~3.98Gb).

You need to create a backup (dfm backup create) and upgrade to 5.0.2P2 or higher:

http://support.netapp.com/NOW/download/software/occore_lin/5.0.2P2/

http://support.netapp.com/NOW/download/software/occore_win/5.0.2P2/

Thanks,

Kevin