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
Hello Phil,
OK, thanks for the feedback.
Best regards,
Kern
On 10/28/2017 08:24 PM, Phil Stracchino wrote:
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
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
Hi Andrew, hi Phil,
I have had a similar problem with making a backup spanning mutiple drives (no
autochanger, so I need to change the tapes by hand). I Have set "some" options
to circumvent it. I didn't do to much research, which one was the critical one,
but maybe that might help you out:
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
13 matches
Mail list logo
