Hello,
Probably 95% of all such problems are due to configurations where the MediaType is not properly set. - If you are using any form of autochanger, each autochanger must have a *unique* MediaType. - Each Device configuration in the SD must have a unique MediaType for each different ArchiveDevice definition. Said the other way around, each ArchiveDevice definition must have its own unique MediaType. The .conf files you list are incomplete, so it is not possible to analyze them, but when I see: MediaType = File, that raises a red flag that indicates that there may be other Storage devices with the same MediaType, and if that is the case, sooner or later, you will find that Bacula is very confused. In the next Bacula version, I will probably modify the SD and possibly the Dir to require unique MediaTypes, then this problem will be resolved. I don't usually supply "support" because I don't have the time, but this particular problem interests me from the standpoint that I would like to prevent it, but with no console/job output showing the failures and incomplete DIR and SD confs I cannot do any more. Best regards, Kern On 08/05/2014 03:08 PM, Joe Rhodes wrote: I’m also running into this issue. |
------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users