>>>>> On Sat, 13 Feb 2010 20:31:27 +0100, hontvari at flyordie.com said: > > There is an example configuration in the Automated Disk Backup section > of the documentation, see here: > > http://www.bacula.org/5.0.x-manuals/en/main/main/Automated_Disk_Backup.html > > The BackupCatalog job refers to the Default pool, which is not defined > anywhere. How this should be corrected? > Of course I can add back the default pool which is included in the > default configuration. But as I understand that would result in an > infinite long volume on the disk. This seems to contradict the main > story of the section, which says that infinite volumes on a disk is a > bad thing. On the other hand if I modify the configuration to use the > same three pools which are used by the regular jobs, then that again > contradicts the explanation, which assume only one job in the > calculations in quite a few places.
The catalog backup always contains the whole database, so there should be no need to keep old copies of it. Therefore, a pool with two volumes that recycle frequently might work best, without using much more disk space. __Martin ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
