From: Ana E. M. A. <emi...@gm...> - 2014-10-24 22:27:26
|
Maybe this could be usefull. But I'm still trying to understand why are you using disk drives directly in archive device configuration. You have PB backups. I suppose you have storage arrays with other fault tolerance levels like raid, multipath, etc.. This way, until you have a disk failure that make your ärchive device" unavailable for bacula, you will have enough time to take the necessary actions to avoid this. I also think that backup software cannot be aware of hardware faliures. Instead this is a problem that has to be treated in another fault tolerance level. Sorry If I am misunderstooding the problem here. Best regards, Ana On Fri, Oct 24, 2014 at 2:57 PM, Alan Brown <aj...@ms...> wrote: > On 24/10/14 18:02, Bryn Hughes wrote: > > On 14-10-24 09:32 AM, Alan Brown wrote: > >> (Why would you want to disable a drive? If it's offline because it > >> failed its cleaning cycle, as a f'instance) > > So what you need is a feature request to be able to disable a drive via > > bconsole.... Not to be able to dynamically reload the SD configuration. > > When the drive is replaced, its by-id changes, which has a ripple effect > across the configuration (This is one of the reasons I use symlinks from > "bacula ID" to the by-id, which in turn links to the real device.) > > _BOTH_ features are useful (and there are tickets in bacula enterprise > for them already) > > > > > > > > Bryn > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Bacula-users mailing list > > Bac...@li... > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bacula-users mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-users > |