> On Mon, 5 Dec 2016 17:40:08 +0800, Gi Dot said:
>
> > What exactly do you mean by "too long"? Does bacula encounter a
> > timeout during the pruning from a database error?
> Like it runs overnight and still not done with it. Sample log:
> https://dpaste.de/wetb/raw
This doesn't look like a
Are you seeing any high loads on the server while pruning job is
running? It looks like the pruning job is stuck in some sort of
loop. Given your machine specs, db backend and catalog size the job
should be through in an instant.
If you're feeling adventurous you could also try mannually purging
- Hardware specs of the director (assuming all components run on a
single machine)
>> Backup runs on a database server. There's also one remote client being
backed up once a week.
- Which database are you using for the catalog?
>> PostgreSQL
- Amount of RAM available to the DB / backend storage
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
>
