Hi, 25.10.2007 12:12,, Matthias Baake wrote:: > On Wed, Oct 24, 2007 at 09:10:06PM +0200, Arno Lehmann wrote: >> Hi, >> >> your mail arrives here as an attachment, which makes it hard to >> reply... you might want to change that. >> > Sorry for that i hope this one comes correct.
Yup, now the reply worked as expected. Thanks! >>> Hello List, >>> >>> I have actually a problem when a Backup Job fails. If it fails the >>> predicted Volume gets marked as error. What i not understand is, if >>> there is a connection problem between the fd and sd the volume is >>> never used but still gets marked as error. >> The important question is why it's marked as "Error". If the volume >> can't be read correctly, that is the expected behaviour. >> > The Volume is imho not the problem (File Storage at a local hard > drive) . For example: > The Job starts and the director is connecting to the fd. This > connection times out because of Firewalling. So I think the Volume is > never going to be touched. There is no connection made from the client > to the storage daemon. For me this is a network error not a volume > error. It looks like this, right. But still it would be good to see why Bacula marks a volume as "Error". There should be a line in the job report mail or Baculas console log. >>> Is it possible to >>> manipulate the error handling in case of a connection problem? >> You can manually update the status of the volume to "Used" or "Full", >> but should first find out if the volume actually is usable. >> > I know but what i do not like is the manually ;). The problem is i > have limited the maximum number of volumes on a specific storage > device. If i get one error after another the volumes will end up all > marked as error and the whole backup session is failing. Well, Bacula marks a volume as "Error" when it decides it can't use that volume. While the logic in deciding this could be buggy, it's the only logic Bacula has :-) So, from Baculas point of view, you can't automatically decide to set a volume to be usable again. The next thing to do is to find out why the volumes are marked as "Error", I don't think you can avoid that task. Arno > Matthias > >> Arno >> >>> Sincerly >> >> 24.10.2007 12:14,, Matthias Baake wrote:: >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Bacula-users mailing list >>> Bacula-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/bacula-users >> -- >> Arno Lehmann >> IT-Service Lehmann >> www.its-lehmann.de >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users > -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
