Logrotate: Rotating non-log files?

Posted on

Logrotate: Rotating non-log files? – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about linux, log-files, logrotate, , .

I have a backup script that compresses various files and directories and creates .tgz archives. Files are named, e.g.

...
backup_2010-10-28.tar.gz
backup_2010-10-29.tar.gz
backup_2010-10-30.tar.gz
backup_2010-10-31.tar.gz
backup_2010-11-01.tar.gz

I want to manage these files so only the last 5 backups are kept, with older files being deleted.

Can I use logrotate to do this? They aren’t log files and are already compressed. They’re in /root and not in /var/log – can I still use it?

Thanks

Solution :

Logrotate rotates files, so the answer is yes – probably, and if no sufficient permissions then place them in /backup or something. Check what group and user the rotated logs have :-).

There’s options for compression in logrotate, så if “compress” is NOT configured – well then it won’t try. Also in your case, “rotate 5” option.

Take a look in /etc/logrotate.d (or where ever it’s stored in your system)

Without a change to your process, logrotate on its own will not do what you’re looking for here. The key problem here is that, while logrotate can take wildcards, it will not treat the files as one if you do so and will instead attempt to rotate all of them individually, which is definitely NOT what you want.

You can, however, make it work the way you describe as long as the most recent backup is created without a date stamp. If you backup process creates /root/backup.tar.gz for instance, you could use the following logrotate configuration:

/root/backup.tar.gz {
    rotate 5
    nocompress
    dateext
    dateformat _%Y-%m-%d
    extension .tar.gz
    missingok
}

The quick rundown of the options here:

  • rotate 5 — keep 5 rotations before deleting
  • nocompress — do not compress the files after rotating
  • dateext — use the date as the rotation extension instead of incrementing numbers
  • dateformat _%Y-%m-%d — set the date extension format you want to use
  • extension .tar.gz — make the .tar.gz come after the rotation extension
  • missingok — if the file we want to rotate isn’t there, don’t worry about it and move on (the default is to throw an error)

Hope this helps!

You don’t have to use logrotate to do it. Just use a command like this:

ls -1 /root/backup_* | sort -r | tail -n +6 | xargs rm > /dev/null 2>&1

This command will leave the most recent 5 files and remove the remaining (if any). You can use it in a cron job.

I just had the same situation. Logrotate sounds pretty cool but it didn’t work for me at 100% because it mismatch data and file names.

So, to avoid confusion, I decided to incorporate the following line to execute after created my current backup in order to keep the last 5 backups.

My logs are i.e.:

  • tbl-bcx-20180308_010501.tar.bz2
  • tbl-bcx-20180307_010501.tar.bz2
  • tbl-bcx-20180306_010501.tar.bz2

New line into my backup-script (based on a comment above)

  • find /BCX/dumpsql/ -type f | sort -r | tail -n +6 | xargs rm

Regards,

Leave a Reply

Your email address will not be published.