Hi all
I'm working on a Bacula setup, and I have a few questions.
My plan is to setup one pretty well spec'ed up dedicated director (bunch of
RAM, mirrored drives and mirrored SSDs for the indices on PostgreSQL). This
will be placed on a central private network. Servers that are to be backuped
On 10/06/10 13:04, Roy Sigurd Karlsbakk wrote:
Hi all
I'm working on a Bacula setup, and I have a few questions.
My plan is to setup one pretty well spec'ed up dedicated director
(bunch of RAM, mirrored drives and mirrored SSDs for the indices on
PostgreSQL). This will be placed on a
Now, I understand only the director needs access to the database,
the
FDs will be contacted by the director, and the SDs will be contacted
by the respective FDs. On some Linux distros, the SD or FD comes as
separate pre-built packages, but on some of the other platforms,
these need to
On 10/06/10 13:40, Roy Sigurd Karlsbakk wrote:
Another question, then. Will tools like bscan need to run locally on
the SD with access to the database to be useful? If so, what would be
a preferred setup for the environment described? I will be able to
reach the database (on the director
Is there a way to ./configure so that only fd gets configured
and/or built? I'm working on including other clients to my
bacula server and these clients need the source rebuilt, but
since they are not the bacula server they only need fd.
Mike
On Fri, 06 Jul 2007, tomasz dereszynski might have said:
mikee wrote:
Is there a way to ./configure so that only fd gets configured
and/or built? I'm working on including other clients to my
bacula server and these clients need the source rebuilt, but
since they are not the bacula server
mikee wrote:
Is there a way to ./configure so that only fd gets configured
and/or built? I'm working on including other clients to my
bacula server and these clients need the source rebuilt, but
since they are not the bacula server they only need fd.
there is not bad idea to read
