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 backup. In
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
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
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
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
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 when
Op 20121002 om 12:15 schreef DAHLBOKUM Markus (FPT INDUSTRIAL):
bigsnip/
I have added the heartbeat interval on all daemons, but no change.
The _all_ deamons involved is important.
bigsnip/
Markus
I now could check if bacula fd to sd connection timed out because of the
network
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 on
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
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
handy if
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
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
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, when we
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
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. Everything
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
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.1) on
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
I have a problem with 1 client. It is a solaris zone. I don't have issues with
the other zones on the same server, so I can't believe it's a hardware error or
firewall problem. (The client is running in a DMZ-zone)
I also have used Heartbeat Interval = 60 seconds for dir, sd and fd, but the
Thank you very much!
I added Heartbeat Interval = 1 minutes to the DIR, SD and FD
configurations and it solved the problem. I also had to fix the
bacula.batch problem: http://wiki.bacula.org/doku.php?id=faq
2008/11/28 Dan Langille d...@langille.org
Silvian Cretu wrote:
Hi,
I am a bacula
Hi,
I am a bacula user for almost 2 years now. But I've encountered a problem,
recently.
Whenever I try to backup files from a specific client I get this errors:
27-Nov 11:23 director JobId 373: Fatal error: Network error with FD
during Backup: ERR=Connection timed out
27-Nov 11:23 storage JobId
Silvian Cretu wrote:
Hi,
I am a bacula user for almost 2 years now. But I've encountered a
problem, recently.
Whenever I try to backup files from a specific client I get this errors:
27-Nov 11:23 director JobId 373: Fatal error: Network error with FD during
Backup: ERR=Connection timed
Hi,
You need a keepalive. Your SonicWall is terminating the connection.
Stick the Heartbeat Interval in the bacula-fd.conf:
FileDaemon { # this is me
Name = MyServer-fd
FDport = 9102 # where we listen for the director
WorkingDirectory =
Hi Ger,
you were absolutly right. With the Heartbeat enabled the Backup was
successfully completed. Many thanks.
--
Florian Schürfeld [EMAIL PROTECTED]
---BeginMessage---
Hi,
You need a keepalive. Your SonicWall is terminating the connection.
Stick the Heartbeat Interval in the
Hi there,
when i try to backup a remote host, i get
Fatal error: Network error with FD during Backup: ERR=Connection reseted
by peer
08-Feb 07:25 bacula-dir: heidi_bkup.2007-02-08_06.24.56 Fatal error: No
Job status returned from FD.
This occures after a duration of one hour. The uplink to the
I'm getting some strange failures when I try to backup computers over an
ADSL line, everything runs ok for about 2 hours then I get:
07-Jun 22:31 my-dir: client.2006-06-07_20.30.00 Fatal error: Network error with
FD during Backup: ERR=Connection reset by peer
07-Jun 22:31 my-dir:
Hi,
Put this line in the FileDaemon part of your bacula-fd.conf file of the
client:
Heartbeat Interval = 15 seconds
Greetings,
Ger.
On Thursday 08 June 2006 15:28, Tyler Bannister wrote:
I'm getting some strange failures when I try to backup computers over an
ADSL line, everything runs
On Thursday 08 June 2006 15:39, Ger Apeldoorn wrote:
Hi,
Put this line in the FileDaemon part of your bacula-fd.conf file of the
client:
Heartbeat Interval = 15 seconds
To avoid timeouts during tape changes, you might need to add the same
directive to your bacula-sd.conf file as well.
On Thu, 8 Jun 2006, Tyler Bannister wrote:
I'm getting some strange failures when I try to backup computers over an
ADSL line, everything runs ok for about 2 hours then I get:
07-Jun 22:31 my-dir: client.2006-06-07_20.30.00 Fatal error: Network error
with FD during Backup: ERR=Connection
On Thu, 8 Jun 2006, Kern Sibbald wrote:
On Thursday 08 June 2006 15:39, Ger Apeldoorn wrote:
Hi,
Put this line in the FileDaemon part of your bacula-fd.conf file of the
client:
Heartbeat Interval = 15 seconds
To avoid timeouts during tape changes, you might need to add the same
Thanks Ger, that seems to have fixed the 2 hour timeout problem I was
having, but I got this error instead:
08-Jun 16:19 my-dir: client.2006-06-08_11.10.54 Warning: Unexpected
Client Job message: ÿÿÿúJmsg Job=client.2006-06-08_11.10.54 type=8
level=1149797124 client-fd: Could not stat
I see the following error while trying to backup a couple servers. All my
other clients work fine.
frigg is my bacula server and web is the server which I am trying to
backup
I can see that it is backing up files, but after a while it just stops.
I have also tried setting the following.
I have a problem backing up through the FireWall.
All seems to run find for about an hour theI get the above error.
I have the FW 'no activity' set we over an hour.
The only other difference between these and the good backups is the FW switch
in a only a 10/10.
If I just backup a subset of
Sorry for the dupe, but after Kens message -
The machines on the DMZ are running RH ent3 with Bacula 1.38.2
Bacula server is also running RH ent3. Storage is disk.
On the lan side Bacula is backing up 17 linux and windows boxes with no
problems.
I have a problem backing up through the
34 matches
Mail list logo
