Hello,
it seems we've finally found the source of the strange behaviour we were
experiencing with bacula-fw on Windows.
The powershell scripts which was supposed to return the list of files for
backup terminated with errors when it was run under system account (in
which bacula-fd is run) and
Alan,
I understand. I've been meaning to get started with learning Postgres
for several years, but there always seems to be something more urgent
that takes my attention away. At the moment, it's storage system
failures, which is kinda a big deal, so for now I'll have to be content
with the
On 04/24/2014 11:37 AM, Lloyd Brown wrote:
Alan,
I understand. I've been meaning to get started with learning Postgres
for several years, but there always seems to be something more urgent
that takes my attention away. At the moment, it's storage system
failures, which is kinda a big
On 24/04/14 17:37, Lloyd Brown wrote:
Alan,
I understand. I've been meaning to get started with learning Postgres
for several years, but there always seems to be something more urgent
that takes my attention away.
If you're using RH/Debian/Ubuntu then you can get it running fairly
quickly
I am doing some testing with Bacula 7 and amongst other things am
looking at the prune expired and truncate console commands.
I have added the following runscript to the BackupCatalog job
RunScript {
RunsWhen=Before
RunsOnClient=No
Console = prune expired volume yes
On 2014-04-25 07:59, Brady, Mike wrote:
I am doing some testing with Bacula 7 and amongst other things am
looking at the prune expired and truncate console commands.
I have added the following runscript to the BackupCatalog job
RunScript {
RunsWhen=Before
RunsOnClient=No
My best guess is that the output from
powershell forms a directive something like:
File = D:\Thunderbird Profile\hfkeo6lv.default\Extensions
...
as seen by the Bacula parser, which is absolutely not going to
work because it has spaces in it.
On 04/22/2014 03:30 PM, Martin Simmons wrote:
On Tue, 22 Apr 2014 12:38:13 +0200, Kern Sibbald said:
In general yes, it is much more stable, because it is build by
Bacula Systems (usually me) with the correct libraries and delivered
to paying customers. With other versions you get they may or
On 04/23/2014 11:00 AM, le dahut wrote:
Sorry to insist but am I the only one who've noticed that ?
How can I solve this problem ?
I am not sure those commands are used internally by Bacula anymore. They
were originally written to support writing to CD drives, which is no
longer implemented.
The --with-mysql option permits
specifying where the MySQL is installed, and doing so should allow
it to compile.
On 04/23/2014 01:55 PM, marcel.van.gereste...@steltix.com wrote:
Hi
I am trying to install
I second what Alan says ... I waited a long time too and it was a bit
harder to get PostgreSQL work with Bacula (permissions and such all of
which are documented in the manual), but I definitely would not go back.
PostgreSQL 9.1 or later is particularly good with Bacula.
Best regards,
Kern
On
On 04/24/2014 03:06 PM, Tom Brandsk
wrote:
Hello,
it seems we've finally found the source of the strange
behaviour we were experiencing with bacula-fw on
On 04/24/2014 10:37 PM, Brady, Mike wrote:
On 2014-04-25 07:59, Brady, Mike wrote:
I am doing some testing with Bacula 7 and amongst other things am
looking at the prune expired and truncate console commands.
I have added the following runscript to the BackupCatalog job
RunScript {
On 2014-04-25 09:17, Kern Sibbald wrote:
On 04/24/2014 10:37 PM, Brady, Mike wrote:
On 2014-04-25 07:59, Brady, Mike wrote:
I am doing some testing with Bacula 7 and amongst other things am
looking at the prune expired and truncate console commands.
I have added the following runscript to
14 matches
Mail list logo
