As a follow-up, these suggestions helped me quite a bit, trimming the database
size down from 324 GB (90% of the filesystem) to 263 GB (73% of the filesystem).
Thanks!
James
On Mar 16, 2017, at 3:29 AM, Mikhail Krasnobaev
mailto:mi...@ya.ru>> wrote:
Good day,
do you run any maintenance jobs
Hi Kern,
If 100 is a large number of jobs, I have a relatively small number (23). I
don’t have any “former” clients that I’m not backing up anymore. One thing I
*do* know is that I have an absolute ton of tiny little files, though I’m
pretty sure that most of them stick around. According to
On Thursday 2017-03-16 15:31:37 Kern Sibbald wrote:
> Hello,
>
> I recently took a look at my catalog a bit more in detail when an
> upgrade of my backup server from 14.04 to 16.04 failed (I have 6
> systems where the upgrade totally failed and left me with a broken
> system), and so I reloaded th
Hello,
I recently took a look at my catalog a bit more in detail when an
upgrade of my backup server from 14.04 to 16.04 failed (I have 6
systems where the upgrade totally failed and left me with a broken
system), and so I reloaded the Bacula catalog from scratch an
> On Mar 16, 2017, at 3:29 AM, Mikhail Krasnobaev wrote:
>
>> 15.03.2017, 19:57, "James Chamberlain" :
>>
>> Hi all,
>>
>> I’m getting a touch concerned about the size of my Bacula database, and was
>> wondering what I can do to prune it, compress it, or otherwise keep it at a
>> manageable
> On Mar 15, 2017, at 10:17 PM, Josip Deanovic
> wrote:
>
> On Wednesday 2017-03-15 12:57:33 James Chamberlain wrote:
>> Hi all,
>>
>> I’m getting a touch concerned about the size of my Bacula database, and
>> was wondering what I can do to prune it, compress it, or otherwise keep
>> it at a m
On Wednesday 2017-03-15 12:57:33 James Chamberlain wrote:
> Hi all,
>
> I’m getting a touch concerned about the size of my Bacula database, and
> was wondering what I can do to prune it, compress it, or otherwise keep
> it at a manageable size. The database itself currently stands at 324
> GB, an
