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
>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
Von: DAHLBOKUM Markus (FPT INDUSTRIAL)
[mailto:markus.dahlbo...@fptindustrial.com]
Gesendet: Donnerstag, 4. Oktober 2012 10:06
An: bacula-users@lists.sourceforge.net
Betreff: Re: [Bacula-users] Network error with FD during Backup:
ERR=Connection reset by peer
Hi Tom,
Thank you for your
Von: Josh Fisher [mailto:jfis...@pvct.com]
Gesendet: Freitag, 5. Oktober 2012 18:50
An: bacula-users@lists.sourceforge.net
Betreff: Re: [Bacula-users] Network error with FD during Backup:
ERR=Connection reset by peer
On 10/4/2012 4:05 AM, DAHLBOKUM Markus (FPT INDUSTRIAL) wrote:
Hi
On 10/4/2012 4:05 AM, DAHLBOKUM Markus (FPT INDUSTRIAL) wrote:
Hi Tom,
Thank you for your answer.
>The heartbeats are only setup when a job with a client is initiated.
>So, there should be no activity when no job is running. When you
>initiate a job with the client, the director sets up a c
> Yesterday I waited for the job to finish the first tape and then wait
> for me to insert the next one.
>
> I opened wireshark to see if there is a heartbeat during waiting -
> and there was none. During the job the heartbeat was active.
>
>> From what you wrote the heartbeat should be active whe
Hi Tom,
Thank you for your answer.
>The heartbeats are only setup when a job with a client is initiated.
>So, there should be no activity when no job is running. When you
>initiate a job with the client, the director sets up a connection with
>the client telling the client what storage da
> I now could check if bacula fd to sd connection timed out because of
> the network switches. This was not the case. My job still cancels.
My experience is that the heartbeat setting has not helped us with our
"Connection Reset by Peer" issues that occur occasionally. Something
more is going
Op 20121002 om 12:15 schreef DAHLBOKUM Markus (FPT INDUSTRIAL):
> > I have added the heartbeat interval on all daemons, but no change.
The _all_ deamons involved is important.
> > Markus
>
>
> I now could check if bacula fd to sd connection timed out because of the
> network switches. T
>
> >I did a couple of installations and I never faced with this error
>
> >before. Anyway, never say never again.
>
> >In the first scenario we were backing up to tape for a few years and
>
> >then migrated to a disc based solution. Everything worked like a charm.
>
> >This particular pro
> There are Job options to reschedule jobs on error:
>
> Reschedule On Error = yes
> Reschedule Interval = 30 minutes
> Reschedule Times = 18
>
> The above will reschedule the job 30 minutes after the failure and
it'll try and
> do that 18 times before finally giving up. These options come in
ha
On 9/27/2012 4:15 AM, DAHLBOKUM Markus (FPT INDUSTRIAL) wrote:
>
> >I did a couple of installations and I never faced with this error
>
> >before. Anyway, never say never again.
>
> >In the first scenario we were backing up to tape for a few years and
>
> >then migrated to a disc based solution. E
> Tom: How did you restart the job. Did you have a script or do you do it
> by hand?
There are Job options to reschedule jobs on error:
Reschedule On Error = yes
Reschedule Interval = 30 minutes
Reschedule Times = 18
The above will reschedule the job 30 minutes after the failure and it'll
try a
>I did a couple of installations and I never faced with this error
>before. Anyway, never say never again.
>In the first scenario we were backing up to tape for a few years and
>then migrated to a disc based solution. Everything worked like a charm.
>This particular problem occurred first, whe
> > 2012-09-19 22:58:45 bacula-dir JobId 13962: Start Backup JobId
13962,
> Job=nina_systemstate.2012-09-19_21.50.01_31
> > 2012-09-19 22:58:46 bacula-dir JobId 13962: Using Device
> "FileStorageLocal"
> > 2012-09-19 23:02:41 nina-fd JobId 13962: DIR and FD clocks differ
by 233
> seconds, FD
> The transfer rate is very low in the first server log. Perhaps there
> truly is a problem with a NIC in this hypervisor, or cable, switch,
etc.
There is a second server on this host, which is being backuped too,
without any problems, either in backup or general network performance.
But I will c
> 2012-09-19 22:58:45 bacula-dir JobId 13962: Start Backup JobId 13962,
> Job=nina_systemstate.2012-09-19_21.50.01_31
> 2012-09-19 22:58:46 bacula-dir JobId 13962: Using Device "FileStorageLocal"
> 2012-09-19 23:02:41 nina-fd JobId 13962: DIR and FD clocks differ by 233
> seconds, FD autom
On 9/26/2012 7:45 AM, Michael Neuendorf wrote:
> Hello there,
>
> I have a problem while backing up two windows servers in two different
> installations. The scenarios are almost equal:
>
> - Bacula-dir (v5.0.1) on Ubuntu 10.04.3 virtualized with VMware vSphere 5
> Hypervisor
> - Bacula-sd (v5.0
Hello there,
I have a problem while backing up two windows servers in two different
installations. The scenarios are almost equal:
- Bacula-dir (v5.0.1) on Ubuntu 10.04.3 virtualized with VMware vSphere 5
Hypervisor
- Bacula-sd (v5.0.1) on same server with file storage on a NAS, mounted via
iS
19 matches
Mail list logo
