Nagios Support Forum

I had just expanded my / to 40G just a month ago from whatever the default size was in the ova file (I think it was 10, maybe 20).
I'm at 100% use and can't use the GUI.

Help!

Additional info:

Ran:
du -a / | sort -n -r | head -n 10

And here are the results

36664880 /
30504072 /store
30504068 /store/backups
29897992 /store/backups/nagiosxi
3082472 /usr
1532196 /usr/local
1387452 /var
1311220 /usr/local/nagios
976396 /var/lib
894612 /usr/local/nagios/share

Hey,

Do you store your backups locally? Not a good idea. Rsync or ftp them to remote storage.

Grtz

I'm with WillemDH, if you have the scheduled backups setup for local it can fill a drive quickly, especially if it is only 40GB. The fact that the bulk of the storage is being taken up in /store/backups/nagiosxi leads me to this conclusion

The default ova is only 10GB in size, and should be expanded to match the amount of things you are going to be monitoring.
http://assets.nagios.com/downloads/nagi ... ements.pdf

40GB would be the recommended minimum, but that is not taking into account storing backups on the server

The only backups I wanted are the config backups and I thought those were SMALL and I set it to only keep 5 copies. I grab those using TSM nightly.
What would these backups be and how do I disable it, or am I misunderstanding the backups/process?

Config backups are found in the snapshots. The full backups include the rrds, xi dir, etc, while the snapshots just include the nagios program and object configs. The snapshots should be located in the nom directory:

ok... I want to keep my backups local since I have TSM backing up that folder.
What I would like to do is setup a job that runs and does something like the following command every day to clean up the old folders in the backup location: Can anyone advise me on the right process to get this running as a cron job or whatever you Linux people call it
<I'm such a linux newb, but I'M TRYING>

BTW: the find "action" of -delete doesn't work since I'm deleting non-empty directories (unless you have words of wisdom there so I can get rid of the "-exec" part)

If you have upgraded to 2014, you could use our scheduled backup component to do this, specifying a max number of backups to preserve at any given time.

The following has been configured the entire time, is this what you mean or am I missing something still? Because I still ended up with 28G of backup directories in addition to the tar.gz files.

How big is each backup? If they are around 4GB each, ~28GB would make sense. Have you considered decreasing the max number of backups to preserve?