Kern Sibbald wrote:
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.
hi, thanks for your answers.
but what i mean, is that i want to restart an aborted Job. And Bacula
do than the rest of this backup. That is a good feature, for big
remotebackup's.
for example:
An big Remote-Backup of 5GB data, runs for many hour's.
If then an temp-error crash's the backup on 90% of required backuptime,
i can restart this job and bacula need now a short time to finish the
rest of 10%.
And thanks for tip. I try an VPN-Connection to reduce the error
probability.
greetings Maik
|
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
