On Tuesday 09 January 2007 11:54, Alan Brown wrote: > On Mon, 8 Jan 2007, Kern Sibbald wrote: > > > My advice to other users, remains the same: If a Job fails, the File records > > will most likely not have been inserted > > Or in other words, if spooling data+attributes is enabled, resuming a > failed job is almost guaranteed to result in an unrestorable backup set.
Yes. In addition, it has nothing to do with whether or not spooling is enabled. Your best bet is to let Bacula do it's job. If resuming is really critical, someone should submit a Feature Request, which has not been done (it is too late now). My own view on resuming is that users who are having problems with job failures should look into those causes, which are most likely comm related. You might do better to ask the hardware/software providers why they are unable to supply reliable TCP/IP connections. IMO, there is *way* too much bad hardware out there. TCP/IP has error correction in it, only very bad quality connections (WiFi) or poorly implemented hardware/firmware should experience problems. The first (bad quality connections) can be excused if it is via radio; for the second (poor hardware/firmware) there is no excuse. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
