Hi folks, I need to reduce the number of volumes in a pool from 3 full backups to just 2 (each client has its own pools for incr. and full backups with the appropriate number of volumes; MaxVolJobs is set to 1 naturally).
I updated the Maximum volumes parameter in the pool definition (bacula-dir.conf, changed it from 3 to 2) and did an update pools from resource after restarting bacula. However the update command output still has "MaxVols" at 3 instead of the new value, "2". I also tried updating the pool table (hehe :)) manually using an update statement in mysql, but after a short while the "MaxVols" paramater for the pool in question changed back to "3" instead of "2". I'm 100% certain bacula uses the updated configuration (I checked for stray bacula processes after etc/bacula stop). It would be great if someone could shed some light on this. Maybe I need to delete the oldest volumes from the pool first? However I don't see how that should affect the MaxVols parameter of the pool definition. Details: CentOS 6 bacula 9.2.1 compiled from source MariaDB backend All the best & bye for now, Uwe -- Uwe Schürkamp | email: <uwe.schuerk...@nionex.net> _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
