Hello guys,
I need to make sure that a given baucla file daemon is unable to do a
restore job, because of security precautions.
Is there a way to do that by configuration option or if there's not, could
you point an easy way to modify the bacula-fd source and disable the FD
from accepting restore
Hello,
This is my situation:
I have Bacula-dir (Bacula 5.2.6) with about 200 clients. Also the major
part of my clients are sharing same catalog (MyCatalog), and I have
added 2 more clients with dedicated catalogs.
All of my clients are using File as a media type, and also all of them
have de
ing multiple
catalogs, if you have clients with very big filesets, containing huge
number of files, and ofcourse if performance is to be considered.
Regards
On Fri, 22 Mar 2013 10:23:35 +0100
Dimitrij Hilt wrote:
> Hi Bugbear,
>
> Am 22.03.2013 09:11, schrieb Bugbear:
> [...]
&
Hi Uwe,
>
> We recently switched to running multiple catalogs and have seen
> similar strange issues, however not while restoring but more often
> when running backups.
Could you give some more info about your problems ? I want to be
prepared before migrating everything to bacula :)
> I'm won
Hello,
Can someone tell me, when Bacula is doing a BACKUP job, where(or how)
the StorageId value (which is added in Media table) is taken from ?
Thanks,
Regards
--
Minimize network downtime and maximize team effectivenes
Hello,
> >
> There is a special table for that:
>
> bacula=# \d storage
>Table "public.storage"
>Column| Type | Modifiers
> -+-+-
> storageid | in
Hi there,
I have some problems with bacula auto-labeling / using/ recycling my
volumes. So for example, I have volumes in my Inc-Pool , with
LabelFormat="${Client}-${Hour}".
Properties of the Inc-Pool { ... Recycle=Yes; AutoPrune=yes;
VolumeRetention=1hours; LabelFormat=${Client}-${Hour}; Use
