Hello James,
thank you for your quick answer.
Am Montag Mai 29 2006 14:29 schrieb James P. Kinney III:
> On Mon, 2006-05-29 at 11:16 +0200, Thomas Sturm wrote:
> > Almost everytime I load another set of tapes into the Autoloader, I get
> > the behaviour that they will not be loaded automatically when a tape is
> > needed. When I do a "*update slots scan storage=Autoloader" everything
> > works fine ... ... until the next time I need those tapes again ...
> >
> > Waht goes wrong there ?
>
> It seems to me it is working as designed. The update slots is needed
> after any change in the autoloader slot so the SD knows what tapes (and
> pools, etc) are available. If tapes are removed and new ones inserted,
> eject and load command have no information passed about which tapes are
> now in the slots.
You are right, without update slots the the SD doesn't know about which tapes
are inserted. But has the SD to know? - When the backup starts it "knows"
about which Slot (in this case 8) to load. I think, this should be enough.
When the tape is loaded, it could read the label. There is no need to ask ME
to load the Tape in slot 8. Am I right?
>
> > Please have a look at the details below.
> > Thanks for any hint.
> >
> > Thomas
> >
> >
> > To: bacula-users@lists.sourceforge.net
> >
> > Linux bacula 2.4.25_pre7-gss-r3 #8 Mo Mär 7 09:53:29 CET 2005 i686
> > Intel(R) Pentium(R) 4 CPU 1.80GHz GenuineIntel GNU/Linux
> > 1000 OK: bacula-dir Version: 1.38.9 (02 May 2006)
> >
> > Volume Mi_1-s8 is in slot 8 of the changer.
> > I have startet a backup-job:
> > 24-Mai 11:22 bacula-sd: Please mount Volume "Di_1-s8" on Storage Device
> > "VS160" (/dev/st0) for Job post.2006-05-24_11.22.03
> >
> > *mount
> > 24-Mai 11:22 bacula-sd: 3301 Issuing autochanger "loaded drive 0"
> > command. 24-Mai 11:22 bacula-sd: 3302 Autochanger "loaded drive 0",
> > result: nothing loaded.
> > 24-Mai 11:22 bacula-sd: Please mount Volume "Di_1-s8" on Storage Device
> > "VS160" (/dev/st0) for Job post.2006-05-24_11.22.03
> >
> > *list media pool=Mo-Do
> > +---------+------------+-----------+----------------+----------+---------
> >---- -
> >
> > | mediaid | volumename | volstatus | volbytes | volfiles |
> > | volretention recycle | slot | inchanger | mediatype | lastwritten
> > | |
> >
> > +---------+------------+-----------+----------------+----------+---------
> >---- -
> >
> > | 9 | Mi_1-s8 | Recycle | 1 | 0 |
> > | 172,800 1 | 8 | 0 | DLT8000 | 2006-05-11 10:15:52 |
> >
> > ... .... ... ... ... ... ... ...
> > ...
> >
> > | 74 | Di_1-s8 | Append | 20,046,594,290 | 26 |
> > | 172,800 1 | 8 | 0 | DLT8000 | 2006-05-24 00:12:54 |
> >
> > +---------+------------+-----------+----------------+----------+---------
> >---- -
> >
> > This behaviour will not appear, when I do an
> > *update slots scan storage=Autoloader
> > before.
> > Is there a problem with the database (postgresql 7.4.5)
> >
> > >From bacula-dir.conf:
> >
> > Pool {
> > Name = Mo-Do
> > Pool Type = Backup
> > Recycle = yes
> > Recycle Current Volume = yes
> > AutoPrune = yes
> > Volume Retention = 2d
> > Volume Use Duration = 2d
> > Accept Any Volume = yes
> > }
> >
> > Best regards
> > Thomas
> >
> >
> > _______________________________________________
> > Bacula-users mailing list
> > Bacula-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
