On Wed, Feb 27, 2013 at 08:11:44AM -0500, Dan Langille wrote: <snip snip> > > In bconsole, did you issue the reload command before issuing the update > command? >
Hi folks, some more observations on reducing the numbers of volumes in a pool: I changed the max volumes from 14 to 8 for a disk based incremental pool, reloaded the director config and then started manually deleting volumes using bconsole. "list pool" still showed numvols = maxvols = 14 until I manually started the "update pool from resource" command, then the volume count for both numvols and maxvols would decrease by one for each volume deleted. Now I'm asking myself is this a bug or a feature? Sure bacula tries to keep my data as long as possible (which is nice), but I'd expect the following to happen: - Bacula sees numvols > maxvols once it's starting a job (maxjobs = 1 per volume), so it deletes the oldest volume from the pool and recycles the next oldest until numvols is equal maxvols again. What really bugs me about this is that even after reloading the config and updating the pool from resource manually, "maxvols" is still on the old value and not the one found in bacula-dir.conf, so one has no indication on a database level that the pool contains more volumes that it should. All the best, Uwe -- NIONEX --- Ein Unternehmen der Bertelsmann SE & Co. KGaA ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users