 |
The file /var/lib/bareos/bareos.sql is only used by Sqlite. Are you aware, that Sqlite is more intended for test environments. We do advice against using it in production. Therefore I do not see the need to make the file path configurable. |
|
|
Thank you for your reply. We use MySQL as Bareos database. The problem comes when backuping MySQL with : /usr/lib/bareos/scripts/make_catalog_backup This script creates a file named "bareos.sql" in WORKING_DIR which is "/var/lib/bareos". This file can be very large and in our architecture /var is not large enough, but /home is. So we would like to be able to specify an alternative path. Either with a configuration file or with a command line argument. |
|
|
Now I see. I have been confused by the summary. Also, the file /var/lib/bareos/bareos.sql is the catalog dump. The Sqlite DB would be /var/lib/bareos/bareos.db. |
|
|
I tend not to extend the behavior of make_catalog_backup. The make_catalog_backup script is just a convenient and robust way to create Bareos catalog backups. However, it is not the only method. If you got space constraints, you can use the MySQL python plugin or bpipe to backup your database without consuming extra local disk space at all, see http://doc.bareos.org/master/html/bareos-manual-main-reference.html#BackupOfAMySQLDatabase If you don't have strict space constraints on your backup media, you better not use incremental MySQL backup, as offered by the Percona xtrabackup plugin. Otherwise a Disaster Recovery of the Bareos server will be harder. If you disagree, you may bring this issue to the bareos-users mailing list, to find out if more users would like to see this feature. |
- Anonymous
