Hi, 23.07.2007 20:57,, Doytchin Spiridonov wrote:: > Hello,
... > What are our future tests: > 1. we will do the same (concurrent jobs) but w.o using GZIP > 2. if it happens again we will set max jobs to 1 so every job is run > alone. Because when testing AFAIR we didn't get errors when we run > just one full backup job. This always happen when we do several at > once (but I am not 100% sure, thats why we will test this) > 3. if it still happens we will run it with normal kernel (so to exclude > the Xen influence) > 4. last we will try w/o LVM (which would be harder) Try using spooling, perhaps as the next thing to do. If the volumes get mixed up, enabling spooling should allow reliable restores again, as only one job will write to each volume at any time. I know that spooling and writing to disk volumes sounds like nonsens, when you try to maximize throughput, but it might be related to your problems... Arno > Regards > P.S. sorry for my English :) Don't worry, I'm quite sure everyone understood your mail! -- 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
