On Tuesday 13 June 2006 22:23, Arno Lehmann wrote:
> Hi,
>
> On 6/13/2006 5:54 PM, Maik Derstappen wrote:
> > If an backupjob is aborted because of temporary network error.
> > It could be nice, if bacula can continues the aborted Jobs.
>
> Yes, indeed.
>
> > Because in the case of an remote backup, it saves many times and trafics
> > on big jobs.
> >
> > is it possible to do that?
>
> No. I suppose a major rewrite of Baculas comunication layer would be
> necessary for that...
It is unlikely something that I personally will do in any case, because a
couple of the basic premises on which Bacula was designed was that IP very
rarely makes final delivery errors, so we can rely on the underlying OS to
ensure correct delivery (don't reinvent the wheel), and that Internet
connections will be extremely reliable.
I have found both of these to be true. I never get dropped connections here
for anything I am doing, and if users experience dropped lines, IMO, they
probably have either an ethnet card problem or should do some serious talking
to their ISP.
>
> You might try to use a VPN connection - AFAIK, using a VPN, a broken
> underlying connection does not automatically mean the VPN link breaks, too.
One more good reason to let the experts (VPN writers) do their work, and
Bacula will just worry about keeping track of the data.
--
Best regards,
Kern
(">
/\
V_V
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
