Hi,
25.11.2009 14:20, Sascha Retzki wrote:
> Hello List,
>
> I've got a best practice question. When a Job is started it changes to
> Status=Running and the FD tries to connect to the SD. Let's assume this
> fails due to network outages, or in my case I configured an IP for the
> SD which is not accessible from the Client.
I suggest to first upgrade... the versions you're running are really
old, and espcially regarding the different max ... time settings, much
has been improved in between.
Furthermore, it's unlikely anybody has a 2.2.8 reference installation
available any more :-)
Cheers,
Arno
> What happens is the Job sits in Status=Running and no Data is
> transfered. On canceling the Job, I see things like:
> 25-Nov 11:25 bacula-dir JobId 27: Start Backup JobId 27,
> Job=bacula-test.2009-11-25_11.25.40
> 25-Nov 11:25 bacula-dir JobId 27: Created new Volume "bacula-test-0017"
> in catalog.
> 25-Nov 11:25 bacula-dir JobId 27: Using Device "bacula-test-file"
> 25-Nov 11:34 bacula-test-fd JobId 27: Fatal error: Failed to connect to
> Storage daemon: 192.168.1.xxx:9103
> 25-Nov 11:31 bacula-test-fd JobId 27: Warning: bsock.c:123 Could not
> connect to Storage daemon on 192.168.1.xxx:9103. ERR=Connection timed out
> Retrying ...
> 25-Nov 11:34 bacula-dir JobId 27: Fatal error: Socket error on Storage
> command: ERR=No data available
> 25-Nov 11:34 bacula-dir JobId 27: Bacula bacula-dir 2.2.8 (26Jan08):
> 25-Nov-2009 11:34:59
> Build OS: x86_64-pc-linux-gnu debian lenny/sid
> JobId: 27
> Job: bacula-test.2009-11-25_11.25.40
> Backup Level: Full
> Client: "bacula-test-fd" 2.4.4 (28Dec08)
> i486-pc-linux-gnu,debian,5.0
> FileSet: "bacula-test-fileset" 2009-11-25 11:25:10
> Pool: "bacula-test-pool" (From Job resource)
> Storage: "bacula-test-sd" (From Pool resource)
> Scheduled time: 25-Nov-2009 11:24:58
> Start time: 25-Nov-2009 11:25:12
> End time: 25-Nov-2009 11:34:59
> Elapsed time: 9 mins 47 secs
> Priority: 10
> FD Files Written: 0
> SD Files Written: 0
> FD Bytes Written: 0 (0 B)
> SD Bytes Written: 0 (0 B)
> Rate: 0.0 KB/s
> Software Compression: None
> VSS: no
> Storage Encryption: no
> Volume name(s):
> Volume Session Id: 2
> Volume Session Time: 1259081276
> Last Volume Bytes: 0 (0 B)
> Non-fatal FD errors: 0
> SD Errors: 0
> FD termination status:
> SD termination status: Waiting on FD
> Termination: Backup Canceled
>
>
>
> I've already set the following timeouts in my bacula-dir.conf:
> Director {
> ...
> FD Connect Timeout = 5
> SD Connect Timeout = 1
> ...
> }
> (I had "n" postfixed to the numbers because I somewhere read it means
> minutes, so originally I had XD Connect Timeout = 5n, but it doesnt work
> either way)
>
>
> Okay so I want it to timeout so it triggers a log message like it does
> when I cancel the job. I want the people who're responsible for these
> backup to come to the office in the morning and see their daily backup
> job succeeded or failed. I don't actually care if it cancels or not, at
> least if all the other jobs are succeeding regardlessly ;-)
>
>
> Soo, give me your best practice advice, or tell me if I just did
> something wrong with teh configuration and I am on the wrong track!
>
>
> Thanks in advance, Sascha
>
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
