Hello Alan,
Yes your suggested change would be a reasonable feature to add. I cannot
work on that right at the moment, so please submit a feature request.
Best regards,
Kern
On 10/28/2017 11:39 PM, Alan Brown wrote:
On 28/10/17 18:16, Kern Sibbald wrote:
Hello Bill,
By the way, I have
On 28/10/17 18:16, Kern Sibbald wrote:
>
> Hello Bill,
>
> By the way, I have just committed another patch for the problem of
> marking all volumes read-only. If you have time please test the
> latest code in the repo, I think it should correct the last note you
> put into your bug #2329.
>
> The
Yes, nice summary ("In other words") at the end :-)
On 10/28/2017 07:35 PM, Bill Arlofski wrote:
On 10/28/2017 11:16 AM, Kern Sibbald wrote:
Hello Bill,
By the way, I have just committed another patch for the problem of marking all
volumes read-only. If you have time please test the latest
On 10/28/17 14:16, Phil Stracchino wrote:
> On 10/28/17 13:41, Phil Stracchino wrote:
>> On 10/28/17 12:10, Phil Stracchino wrote:
>>> I will definitely download and test.
>>
>> Clean build on Solaris 11.3 amd64 and all three Gentoo Linux systems.
>
> Identified a tape-spanning file from my last
On 10/28/17 13:41, Phil Stracchino wrote:
> On 10/28/17 12:10, Phil Stracchino wrote:
>> I will definitely download and test.
>
> Clean build on Solaris 11.3 amd64 and all three Gentoo Linux systems.
Identified a tape-spanning file from my last full backup, and attempting
test restore now.
--
On 10/28/17 12:10, Phil Stracchino wrote:
> I will definitely download and test.
Clean build on Solaris 11.3 amd64 and all three Gentoo Linux systems.
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.8485
Mobile:
On 10/28/2017 11:16 AM, Kern Sibbald wrote:
> Hello Bill,
>
> By the way, I have just committed another patch for the problem of marking all
> volumes read-only. If you have time please test the latest code in the repo,
> I think it should correct the last note you put into your bug #2329.
OK!
Hello Bill,
By the way, I have just committed another patch for the problem
of marking all volumes read-only. If you have time please test
the latest code in the repo, I think it should correct the last
note you put into your bug #2329.
The case you cite
On 10/28/2017 10:10 AM, Phil Stracchino wrote:
> On 10/28/17 04:15, Kern Sibbald wrote:
>> Hello,
>>
>> Thanks for the feedback. Can you confirm that your Bacula signs on with
>> version 9.0.5? If so, it means that some recent patches that I have
>> made for this problem (3-4 bug reports)
On 10/28/17 04:15, Kern Sibbald wrote:
> Hello,
>
> Thanks for the feedback. Can you confirm that your Bacula signs on with
> version 9.0.5? If so, it means that some recent patches that I have
> made for this problem (3-4 bug reports) solve the problem :-)
I will definitely download and
Yes bconsole reports it is version 9.0.5 dated Oct 23 2017.
I left a restore and made it wait a few hours between tape changes and
it patiently waited and continued on without issue so far.
On 10/28/2017 04:15 AM, Kern Sibbald wrote:
> Hello,
>
> Thanks for the feedback. Can you confirm that
Bootstrap = "/var/lib/bacula/XXX-ZZZ.bsr"
Priority = 31
Storage = LTO-5HH
Pool = LTO-5HH-Pool
Schedule = "WeeklyCycle"
Max Wait Time = 5d
}
I hope this does the trick for you, too.
Best,
Christian
-----Original-Nachricht-----
Betreff: Re: [Bacula-users] Issue resto
Hello,
Thanks for the feedback. Can you confirm that your Bacula signs on with
version 9.0.5? If so, it means that some recent patches that I have
made for this problem (3-4 bug reports) solve the problem :-)
Best regards,
Kern
PS: I have many other backports and other work to do to
Try pulling down the latest git version of bacula 9.0.x .. I pulled it
down and so far it politely asked for the next tape and patiently waited
for it to be loaded.
On 09/25/2017 12:59 AM, Phil Stracchino wrote:
> On 09/24/17 20:24, Andrew Ryder wrote:
>> Hello,
>>
>> I'm having an issue after
Am 05.10.2017 um 16:11 schrieb Phil Stracchino:
> I didn't realize that you were using an autochanger
> rather than a single drive.
Last week I wrote about my intention for an autochanger test - after
going to the Bacula 9.0.x. versions recently.
--
Ralf Brnkmann
Am 04.10.2017 um 15:44 schrieb Phil Stracchino:
On 10/04/17 04:13, Ralf Brinkmann wrote:
Thanks Phil,
I found two files in two different jobs that both span the same two
LTO-6 cassettes.
The two restore jobs for a single file each did require two cassettes
and did work without any error
On 09/29/17 13:54, Phil Stracchino wrote:
> On 09/29/17 02:14, Ralf Brinkmann wrote:
>> Has someone a Mysql query for on an autochanger test to pickup files
>> that crosses tape boundary?
>
> HThat's a good question. Let me think about that one for a
> few minutes.
There isn't a
On 09/29/17 02:14, Ralf Brinkmann wrote:
> Has someone a Mysql query for on an autochanger test to pickup files
> that crosses tape boundary?
HThat's a good question. Let me think about that one for a
few minutes.
--
Phil Stracchino
Babylon Communications
On 09/24/17 20:24, Andrew Ryder wrote:
> Hello,
>
> I'm having an issue after upgrading from version 7 to version 9 where if
> I'm restoring from a job that spans more than one tape the job fails as
> soon as bacula hits the end of the first tape. Is there a new
> configuration option or
Thanks. I'll have to keep a lookout whenever the next update comes out
to see if it gets patched then.
On 09/28/2017 09:31 AM, Phil Stracchino wrote:
On 09/24/17 20:24, Andrew Ryder wrote:
Hello,
I'm having an issue after upgrading from version 7 to version 9 where if
I'm restoring from a
On 09/24/17 20:24, Andrew Ryder wrote:
> Hello,
>
> I'm having an issue after upgrading from version 7 to version 9 where if
> I'm restoring from a job that spans more than one tape the job fails as
> soon as bacula hits the end of the first tape. Is there a new
> configuration option or
21 matches
Mail list logo
