Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In my company, we have lots of applications running in lots of different servers. These applications generates lots of logs, which sometimes the developers forgot to compress this logs, this way nagios alert about disk space many times. Beside the fact that I had to check if these logs are compressed and they're old than x days, I have to send these files to our backup server, which is gonna be in amazon, we choose this approach 'cause if some disk is full we just add a new disk on it.

So I have to create a good planning of logs. I wonder if you guys already pass through this problem and what you recommend me to do ? Is my approach good or bad ? Any advice would be very important to me.

share|improve this question
up vote 2 down vote accepted

A combination of logrotate, cron and rsync should do the job just fine.

share|improve this answer
  1. Configure logrotate or something similar properly for your environment.
  2. Determine if you need to keep backups of log files.
    If so, include them in your backup process like they're any other file you need to back up.

Determining "proper" configuration for log rotation and setting up backups are left as an exercise for the reader (Server Fault can't do that for you).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.