>>>>> On Wed, 11 Jan 2012 14:21:52 -0500, Honia A said:
>
> I'm backing up a handful number of Unix boxes, they all get backed up very
> quickly but we can't access them due to the BackupCatalog job being very
> slow. When I read online, I see people said it's because of the database
> size getting larger and larger.
>
> I cancel the backup catalog job and all the servers become accessible. This
> is the configuration for catalog:
>
> # This is the backup of the catalog
> FileSet {
> Name = "Catalog"
> Include {
> Options {
> signature = MD5
> }
> File = "/var/lib/bacula/bacula.sql"
> }
> }
>
> All backups finish around 5 AM but all the servers remain inaccessible until
> 8:30 or so. The last job running is that backup job so I thought the process
> getting slower and slower everyday might have something to do with the size
> of th ebacula.sql file.
The bacula.sql you showed in your first email was written at 05:23, so it
seems unlikely that Bacula was doing anything at 8:30.
Please post the log output from the BackupCatalog job.
Also, can you describe exactly what you mean by inaccessible?
__Martin
------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
