On Mon, Dec 05, 2016 at 03:18:45PM +0800, Gi Dot wrote: > Hello, > > I have this problem with one of my client experiencing pruning of a volume > that is taking too long (and in the end I ended up recycling it manually by > updating the volume status). I have googled up on this and from what I > understand it is mostly due to the database indexing (to be honest I don't > entirely understand this part). > > My question is, is there any downside or side effect if I were to include a > script that looks up for Used volume and update it to Recycle before the > backup runs for the day. I am using this script on another client and > things are going fine over there, but I'm just worried if there is any > impact in a long run. > > If anyone would be so kind to explain to me what exactly it means by > pruning; as in what bacula does when it runs pruning on a volume, it is > much appreciated as well. I have read somewhere that bacula removes the > jobs associated with the volume from the catalog. >
Hello Gidot, some more info could be useful to help you in analyzing your setup further. - Hardware specs of the director (assuming all components run on a single machine) - Which database are you using for the catalog? - Amount of RAM available to the DB / backend storage (disks, ssds?) - Catalog size (file table rows) - Bacula version What exactly do you mean by "too long"? Does bacula encounter a timeout during the pruning from a database error? All the best, 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
