Author: mikewilt <bacula-forum AT backupcentral DOT com>
Date: Thu, 07 Jul 2011 10:53:03 -0700
Thanks to Graham Keeling for the solution- having storage type "File" for both storage locations was messing it up. I changed them to "File1" and "File2" and the problem went away. Now, rather than h
Author: mikewilt <bacula-forum AT backupcentral DOT com>
Date: Sat, 25 Jun 2011 13:13:39 -0700
I have set up two similar installations at home and at church. They both have the same problem. Both are running under Linux: Linux version 2.6.26-2-686 (Debian 2.6.26-26lenny1) (dannf AT debian DOT
Mike, The only thing I can conjecture due to the lack of disclosure of the seemingly closely-held details is that you are the common denominator in both church and home setups. Hence, you have done s
Author: mikewilt <bacula-forum AT backupcentral DOT com>
Date: Sun, 26 Jun 2011 15:08:34 -0700
I have a little more information. I have two storage locations configured, both set up to automatically label and recycle. The problem seems to come because it goes looking for a volume that was auto
Author: Radosaw Korzeniewski <radoslaw AT korzeniewski DOT net>
Date: Mon, 27 Jun 2011 00:19:35 +0200
Hello, 2011/6/27 mikewilt <bacula-forum AT backupcentral DOT com> I have a little more information. I have two storage locations configured, both set up to automatically label and recycle. The prob
Author: mikewilt <bacula-forum AT backupcentral DOT com>
Date: Sun, 26 Jun 2011 19:10:19 -0700
Media Type = File Same for both storage daemons. Mike +-- +-- -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application perform
Author: Graham Keeling <graham AT equiinet DOT com>
Date: Mon, 27 Jun 2011 08:21:39 +0100
I found out by experience that bacula gets confused if you have the same media type on different storages. It may work better if you set the media types different to each other. -- All of the data ge
I'd just like to add that it is also possible that your disk volumes aren't the problem, but your db server is either filling up the filesystem it lives on, or filling up filesystem where it holds te