Von: DAHLBOKUM Markus (FPT INDUSTRIAL)
[mailto:markus.dahlbo...@fptindustrial.com]
Gesendet: Dienstag, 9. Oktober 2012 10:18
An: bacula-users@lists.sourceforge.net
Betreff: Re: [Bacula-users] Network error with FD during Backup:
ERR=Connection reset by peer
>My job cancels exactly 15 min after
On 2012-10-09 08:33, Durand Toto wrote:
> Hi all,
>
> I have an issue when changing between tapes, which provides the
> following message:
>
> > Error: Re-read last block at EOT failed.
> ERR=block.c:1029 Read zero
> > bytes at 818:0 on device "LTO5" (/dev/nst0).
>
> I tried btape
> *test
Zitat von "Masopust, Christian" :
> Hi Andreas,
>
> why is the "won't fix" for bug 1940 a problem? When you look at
> Kern's eyplanation
> about why
>
>> Why won't we fix it? Well, it is useless to try to backup Windows
>> without VSS
>> enabled as you will miss locked files, ... In otherwo
Zitat von Dan Langille :
> On 2012-10-09 06:12, lst_ho...@kwsoft.de wrote:
>> Hello
>>
>> when evaluating a new backup solution for our company we have focused
>> at Bacula mostly because of some nice features like data spooling,
>> broad client support and so on, but the "killer-feature" in our
On 2012-10-09 06:12, lst_ho...@kwsoft.de wrote:
> Hello
>
> when evaluating a new backup solution for our company we have focused
> at Bacula mostly because of some nice features like data spooling,
> broad client support and so on, but the "killer-feature" in our case
> was the data encryption wit
Hi Andreas,
why is the "won't fix" for bug 1940 a problem? When you look at Kern's
eyplanation
about why
> Why won't we fix it? Well, it is useless to try to backup Windows without VSS
> enabled as you will miss locked files, ... In otherwords you get garbage
> depending
> on what your sys
Hello
when evaluating a new backup solution for our company we have focused
at Bacula mostly because of some nice features like data spooling,
broad client support and so on, but the "killer-feature" in our case
was the data encryption with its straight forward design.
Unfortunately we now h
>My job cancels exactly 15 min after entering the wait mode for a new
>tape. In the VMware settings there is an idle timeout set to 900 sec
>(i.e. 15 min).
>
>The timeout doesn't exactly fit to that kind of connection, but you
>never know.
>
>I disabled this timeout now and restarted my back