On 9/2/2011 10:50 AM, John Drescher wrote: >> I'm wondering if anyone else here has experienced this problem >> and/or has any pointers to a work around. While things can be set up to >> automatically restart the storage daemon if it dies, the main problem is >> that any backups Bacula was in the middle of doing end with an error and >> have to be manually rescheduled/run or just wait until the next time >> their job comes up to run. >> > I have 5 to 10 clients that are not connected when the backup is > scheduled each night with 5.0.3 and I have not experienced this issue > 1 time since I installed 5.0.3 last year.
I concur. I have laptops that are fairly regularly not connected when scheduled and have never seen a hard crash of of the 5.0.3 SD on x86_64 Centos 5.4 (or, more recently, Centos 6.0). ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
