Pool not deleted from catalog

[Rui Loureiro]

Hi Marcin,

I notice that when I remove a Pool from the director configuration, the Pool remains in the catalog. Is this normal behavior? To solve the problem I had to go to bconsole, run the reload command and run the delete pool command.

Best Regards,

Rui

[Marcin Haba]

On Thu, 10 Oct 2024 at 12:44, Rui Loureiro <ruilou...@gmail.com> wrote:
>
> Hi Marcin,
>
> I notice that when I remove a Pool from the director configuration, the Pool remains in the catalog. Is this normal behavior? To solve the problem I had to go to bconsole, run the reload command and run the delete pool command.

Hi Rui,

Bacularis does not support the 'delete pool=XXX' command yet. This is
a function that can be added. At the moment I added it to my feature
list to implement in Bacularis. Thanks!

The situation with the catalog records is different for different
resources. The general Bacularis approach in case orphaned records in
the catalog is to not list them. Bacularis displays only resources
that exist in the Bacula configuration. Normally to remove the
orphaned records from db we use the Bacula 'dbcheck' tool however not
for pools :-) For storage records the situation is even more different
because we don't have any native Bacula command or tool to remove
them.

Best regards,
Marcin Haba (gani)

[Rui Loureiro]

HI Marcin,

You may check if the number of volumes in the pool it's equal to zero. In general, pools with no volumes and no resource in the director are orphaned pools.

Best Regards,

Rui

[Marcin Haba]

On Thu, 10 Oct 2024 at 15:20, Rui Loureiro <ruilou...@gmail.com> wrote:
>
> HI Marcin,
>
> You may check if the number of volumes in the pool it's equal to zero. In general, pools with no volumes and no resource in the director are orphaned pools.

Hi Rui,

Sure. Thanks.