Hello, I made an adjustment that causes catalog backups to be 'bzip2' compressed. 'bacula.sql' compresses 75% and while I generally disklike compression for backups, this file is backed-up every day and eats quite a bit of disk space (50% of the typical total in our case).
The adjustment is not generalized in any way, but could be helpful in creating a more complete catalog backup compression option. Of particular importance is a perl5 bug I tripped over that requires one to use 'if' when checking the outcome of the dump step rather than a 'die'. It appears that someone ran into this issue earlier but did not delve sufficiently deep to figure it out, instead invoking the SQL dump with a perl 'exec' rather than 'system' as a way to work around it. However 'exec' won't suffice when a second compress step is included. The perl5 bug report is at https://bugzilla.redhat.com/show_bug.cgi?id=771257 and was also reported to the upstream perl bug mailing list. Changes attached below. In 'bacula-dir.conf' the catalog FileSet needs File = "/w/bacula/bacula.sql" changed to File = "/w/bacula/bacula.sql.bz2" Regards,
make_catalog_backup.pl
Description: Binary data
delete_catalog_backup
Description: Binary data
------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev
_______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
