Hello,
I suspect that what Martin has said in the second to last paragraph is
correct. At the same time, Bacula really should print a reason why the
label command did not work.
Have you already posted your complete bacula-sd.conf file? If not,
please do so.
Best regards,
Kern
On 09/28/2
> On Fri, 28 Sep 2018 14:25:51 -0400, Gary Dale said:
>
> On 2018-09-28 09:32 AM, Martin Simmons wrote:
> >> On Thu, 27 Sep 2018 20:57:35 -0400, Gary Dale said:
> >> On 2018-09-27 11:05 AM, Martin Simmons wrote:
> On Wed, 26 Sep 2018 23:38:39 -0400, Gary Dale said:
> On 2018-
Hello,
pt., 28 wrz 2018 o 20:19 Gary Dale napisał(a):
> Of course I restrict the volume size. That's normal for Bacula.
>
Well, it is not normal unless you want to limit storage size allocated by
your backups where you additionally define the maximum number of volumes in
pool. In any other case
On 2018-09-28 09:32 AM, Martin Simmons wrote:
On Thu, 27 Sep 2018 20:57:35 -0400, Gary Dale said:
On 2018-09-27 11:05 AM, Martin Simmons wrote:
On Wed, 26 Sep 2018 23:38:39 -0400, Gary Dale said:
On 2018-09-26 11:33 AM, Bill Arlofski wrote:
On 09/26/2018 06:22 AM, Martin Simmons wrote:
Try
On 2018-09-28 06:13 AM, Kern Sibbald wrote:
Hello,
It should not take "I need a lot of new volumes to handle what amounts
to a full backup of 160G of data" unless you are artificially
restricting volume size. Unless I misunderstood what you wrote, you
should not have 40 volumes to store 160G
> On Thu, 27 Sep 2018 20:57:35 -0400, Gary Dale said:
>
> On 2018-09-27 11:05 AM, Martin Simmons wrote:
> >> On Wed, 26 Sep 2018 23:38:39 -0400, Gary Dale said:
> >> On 2018-09-26 11:33 AM, Bill Arlofski wrote:
> >>> On 09/26/2018 06:22 AM, Martin Simmons wrote:
> Try
>
> se
Hello,
It should not take "I need a lot of new volumes to handle what amounts
to a full backup of 160G of data" unless you are artificially
restricting volume size. Unless I misunderstood what you wrote, you
should not have 40 volumes to store 160G of data. One would be
sufficient. In fact
On 2018-09-27 11:05 AM, Martin Simmons wrote:
On Wed, 26 Sep 2018 23:38:39 -0400, Gary Dale said:
On 2018-09-26 11:33 AM, Bill Arlofski wrote:
On 09/26/2018 06:22 AM, Martin Simmons wrote:
Try
setdebug level=150 trace=1 Storage
and look for a file matching *.trace (probably in the SD's Worki
On 2018-09-27 05:10 AM, Jérôme Blion wrote:
Le 27/09/2018 à 05:38, Gary Dale a écrit :
On 2018-09-26 11:33 AM, Bill Arlofski wrote:
On 09/26/2018 06:22 AM, Martin Simmons wrote:
Try
setdebug level=150 trace=1 Storage
and look for a file matching *.trace (probably in the SD's
WorkingDirector
> On Wed, 26 Sep 2018 23:38:39 -0400, Gary Dale said:
>
> On 2018-09-26 11:33 AM, Bill Arlofski wrote:
> > On 09/26/2018 06:22 AM, Martin Simmons wrote:
> >> Try
> >>
> >> setdebug level=150 trace=1 Storage
> >>
> >> and look for a file matching *.trace (probably in the SD's
> >> WorkingDirec
Le 27/09/2018 à 05:38, Gary Dale a écrit :
On 2018-09-26 11:33 AM, Bill Arlofski wrote:
On 09/26/2018 06:22 AM, Martin Simmons wrote:
Try
setdebug level=150 trace=1 Storage
and look for a file matching *.trace (probably in the SD's
WorkingDirectory).
...and you can also add options=t to have
On 2018-09-26 11:33 AM, Bill Arlofski wrote:
On 09/26/2018 06:22 AM, Martin Simmons wrote:
Try
setdebug level=150 trace=1 Storage
and look for a file matching *.trace (probably in the SD's WorkingDirectory).
...and you can also add options=t to have timestamps in the *.trace file.
Best rega
On 09/26/2018 06:22 AM, Martin Simmons wrote:
> Try
>
> setdebug level=150 trace=1 Storage
>
> and look for a file matching *.trace (probably in the SD's WorkingDirectory).
...and you can also add options=t to have timestamps in the *.trace file.
Best regards,
Bill
--
Bill Arlofski
http://
> On Wed, 26 Sep 2018 00:06:48 -0400, Gary Dale said:
>
> On 2018-09-20 06:09 AM, Kern Sibbald wrote:
> > Hello,
> >
> > The output produced by Bacula seems unusually short. Normally Bacula
> > displays a reason for the failure.
> >
> > I recommend trying your label command again, but turn o
On 2018-09-20 06:09 AM, Kern Sibbald wrote:
Hello,
The output produced by Bacula seems unusually short. Normally Bacula
displays a reason for the failure.
I recommend trying your label command again, but turn on debug with
something link
setdebug level=150 Storage
prior to doing the labe
Hello Martin,
Yes, the variable expansion code is deprecated (destined to be removed
at some future unspecified time), but as I do not yet have a replacement
for it, I have keep to the code.
I have some ideas about how to replace the old functionality, but have
not yet implemented it as ther
Hi Kern,
Is variable expansion fully supported again now? The doc
(http://www.bacula.org/9.2.x-manuals/en/misc/Variable_Expansion.html) still
says that it was deprecated as of version 1.37, but the replacement python
scripting has been removed.
__Martin
> On Thu, 20 Sep 2018 12:09:25 +0200,
Check permissions on the disk, including SELinux or other ACLs. The
bacula-sd user must have read/write permissions.
On 9/19/2018 3:40 PM, Gary Dale wrote:
I'm running bacula 7.4.4 on a Debian/Stretch AMD64 server.
When I try to create a new disk volume for my steadily increasing
amount of d
Hello,
The output produced by Bacula seems unusually short. Normally Bacula
displays a reason for the failure.
I recommend trying your label command again, but turn on debug with
something link
setdebug level=150 Storage
prior to doing the label command. It should give you a more detaile
Le 20/09/2018 à 05:23, Gary Dale a écrit :
On 2018-09-19 05:35 PM, Jérôme Blion wrote:
Le 19/09/2018 à 21:40, Gary Dale a écrit :
I'm running bacula 7.4.4 on a Debian/Stretch AMD64 server.
When I try to create a new disk volume for my steadily increasing
amount of data needing to be backed up
On 2018-09-19 05:35 PM, Jérôme Blion wrote:
Le 19/09/2018 à 21:40, Gary Dale a écrit :
I'm running bacula 7.4.4 on a Debian/Stretch AMD64 server.
When I try to create a new disk volume for my steadily increasing
amount of data needing to be backed up, it usually fails after I
create the first
Le 19/09/2018 à 21:40, Gary Dale a écrit :
I'm running bacula 7.4.4 on a Debian/Stretch AMD64 server.
When I try to create a new disk volume for my steadily increasing
amount of data needing to be backed up, it usually fails after I
create the first new volume. There is lots of free space on t
I'm running bacula 7.4.4 on a Debian/Stretch AMD64 server.
When I try to create a new disk volume for my steadily increasing amount
of data needing to be backed up, it usually fails after I create the
first new volume. There is lots of free space on the disk, so it's not
that. Eventually I mig
23 matches
Mail list logo
