1 (edited by JoeVr 2015-04-24 16:37:15)

Topic: [SOLVED]about backup_mysql.sh

==== Required information ====
- iRedMail version: 0.9.0
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MYSQL
- Web server (Apache or Nginx): Apache2
- Linux/BSD distribution name and version: Ubutu Server LTS
- Related log if you're reporting an issue:
====

It is not a bug, but more a question: is there a specific reason why the backup script leave, in the daily backup directory, both the full sized and bziped files ?
I mean what is the point of using a compressor to save space and then keeping both .sql and bzip2 files ?

an example:

ls mysql/2015/04/20/ -la
total 800
drwxr-xr-x  2 root root   4096 apr 20 03:30 .
drwxr-xr-x 13 root root   4096 apr 24 03:30 ..
-rw-r--r--  1 root root    933 apr 20 03:30 2015-04-20-03:30:01.log
-rw-r--r--  1 root root   3364 apr 20 03:30 amavisd-2015-04-20-03:30:01.sql.bz2
-rw-r--r--  1 root root   4146 apr 20 03:30 cluebringer-2015-04-20-03:30:01.sql.bz2
-rw-r--r--  1 root root  25908 apr 20 03:30 iredadmin-2015-04-20-03:30:01.sql
-rw-r--r--  1 root root   3054 apr 20 03:30 iredadmin-2015-04-20-03:30:01.sql.bz2
-rw-r--r--  1 root root 543521 apr 20 03:30 mysql-2015-04-20-03:30:01.sql
-rw-r--r--  1 root root 105099 apr 20 03:30 mysql-2015-04-20-03:30:01.sql.bz2
-rw-r--r--  1 root root  50710 apr 20 03:30 roundcubemail-2015-04-20-03:30:01.sql
-rw-r--r--  1 root root   8614 apr 20 03:30 roundcubemail-2015-04-20-03:30:01.sql.bz2
-rw-r--r--  1 root root  34412 apr 20 03:30 vmail-2015-04-20-03:30:01.sql
-rw-r--r--  1 root root   6217 apr 20 03:30 vmail-2015-04-20-03:30:01.sql.bz2

For me it is a nonsens: if the backup script wants to save space so the script should delete .sql file  otherwise, if not, why wastin time, space and processors cycles compressing them ?

I know: I can simply modify the script, thing that I'll do, to take adavange of the 7z compressor, but I'm also courious smile

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: [SOLVED]about backup_mysql.sh

It's caused by duplicate database names defined in backup_mysql.sh, variable 'DATABASES='. Please remove duplicate names and it should be fine.

3

Re: [SOLVED]about backup_mysql.sh

ZhangHuangbin wrote:

It's caused by duplicate database names defined in backup_mysql.sh, variable 'DATABASES='. Please remove duplicate names and it should be fine.

Deleted duplicates and tested: everything ok.. thanks a lot !!