On Monday 04 September 2006 14:04, Alan Brown wrote: > On Mon, 4 Sep 2006, Kern Sibbald wrote: > > >> (Kern, I'll file this in bugs shortly) > > > > Probably not worth the effort. See my responses below. > > > > Bacula 1.38.11 and below do not permit doing a update slots at the same > > time a drive is in use. > > Which is one reason update slots may have been required to be run against > drive 1 instead of drive 0 > > > I've eliminated that restriction in 1.39.20 -- > > thanks to input from Eric. > > Thanks > > The other reason for running update slots against drive 1 is that up to > now "update slots" on the changer device only unloads drive 0, no matter > which drive is specified
In 1.30.20+ update slots doesn't unload any drive unless, of course, you do a scan. > > >> 2: Running "update slots" against a drive instead of the changer results > >> in all the tapes in the changer being linked to that drive instead of the > >> changer: > > > > Bacula allows you to directly access the drive. If you do so, it is at your > > own risk. I don't recommend it. If you don't put a direct access to a drive > > in your bacula-dir.conf, you won't have this problem. > > > I know the risk is there, but I believe that a lot of the problem can be > mitigated by noticing the drives are associated with the changer and > making sure that the database entries go against the changer rather than > the individual drives within it. Perhaps, but it has been that way since 1.38.0, so at the moment while I am trying to get 1.39.x out the door, modifying behavior of Bacula that has existed for over a year is very low on my priority list. > > > Note that this was happening due to the need to update slots following a > tape change while drive0 was in use by a running backup. With 1.38, you cannot do an update slots by any means if the drive is in use, so what you did is not a solution. > > > > Well, access only the Autochanger. I can add a few more words to the manual, > > but it should already be documented (more or less). I consider this a > > configuration error. > > Under normal circumstances I would only access the changer, however full > backups take several days and tapes may need to be changed out several > times while one or other drives are in use - and one can't unmount a drive > while a backup is actively using it. Well, until you upgrade to 1.39, you cannot do an update slots while jobs are running using the autochanger. It wasn't even a feature -- it was something that Bacula attempted to prohibit (at least that is what I intended). The bug if you will is that it somehow continued despite the problems, and the error message are mostly nonsense. So, I have fixed the bug (hopefully) in 1.39. > > AB > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
