Hello,
It happens that some clients on the network get removed and as such do
not need to be backed up anymore. Now I would like to know what is the
procedure on the bacula director in order to remove properly and
entirely a bacula client?
I checked the official documentation but could not find
om multiple jobs,
> unless "use volume once = true".
>
> Kind regards,
> Rolf
>
> On January 15, 2018 2:10:00 PM UTC, John Naggets <hostingnugg...@gmail.com>
> wrote:
>>
>> Hello,
>>
>> It happens that some clients on the network ge
cannot say 100% how to do this but I suspect that with a small shell
> script, you can delete each of the JobIds associated with the client.
>
> Best regards,
>
> Kern
>
>
>
> On 19.01.2018 21:14, John Naggets wrote:
>>
>> Kern, that's exactly what I would like t
e
> joining the jobs, media, and clients tables should let you get to the list
> of volumes that contain backup-data of the specified client.
>
> Do keep in mind that volume files can contain data from multiple jobs,
> unless "use volume once = true".
>
> Kind regards,
&
jobs, volumes, pools, and if I am not
>>> mistaken jobids. If you have a single job that handles multiple clients,
>>> then the delete job will not be useful. I do not normally delete clients, so
>>> I cannot say 100% how to do this but I suspect that with a small she
='${FDHOSTNAME}';" bacula
> dbcheck -b -f -y -c /etc/bacula/bacula-dir.conf
>
> So we're just deleting the client, and then let bacula get the database
> back into a consistent state.
>
> Depending on your load and requirements that might not be feasible for
> you, of course.
