Hello DA development,
Currently, For apache website log rotation, I mean those files (/var/log/httpd/domains/*.log) will be rotated to /home/xxx/domains/yyy.com/logs/Mar-2015.tar.gz (or Mar-2015.tar.gz.1, or Mar-2015.tar.gz.2, or Mar-2015.tar.gz.3, ...)
May I request that those log filename follow CentOS 6 logrotate format,
e.g.
/home/xxx/domains/yyy.com/logs/yyy.com-20150324.tar.gz
/home/xxx/domains/yyy.com/logs/yyy.com-20150323.tar.gz
/home/xxx/domains/yyy.com/logs/yyy.com-20150322.tar.gz
It is because for some VIP customers, they may want to keep the website logs for longer period (e.g. 30 days or even more)
In existing filename format, as the filename changed during rotation, it will make system incremental/rsync backups more workload (if 30 days x 30 copies) = 900 tar.gz
If filename by date, then, the incremental backup used storage will be less much.
Thank you very much for your kind attention.
Regards
Currently, For apache website log rotation, I mean those files (/var/log/httpd/domains/*.log) will be rotated to /home/xxx/domains/yyy.com/logs/Mar-2015.tar.gz (or Mar-2015.tar.gz.1, or Mar-2015.tar.gz.2, or Mar-2015.tar.gz.3, ...)
May I request that those log filename follow CentOS 6 logrotate format,
e.g.
/home/xxx/domains/yyy.com/logs/yyy.com-20150324.tar.gz
/home/xxx/domains/yyy.com/logs/yyy.com-20150323.tar.gz
/home/xxx/domains/yyy.com/logs/yyy.com-20150322.tar.gz
It is because for some VIP customers, they may want to keep the website logs for longer period (e.g. 30 days or even more)
In existing filename format, as the filename changed during rotation, it will make system incremental/rsync backups more workload (if 30 days x 30 copies) = 900 tar.gz
If filename by date, then, the incremental backup used storage will be less much.
Thank you very much for your kind attention.
Regards