It does not seem to be the case.

And now came Wednesday night. During the day, the 1st setup backup (unblocked manually through mount) was canceled because of the MaxUseTime reached. So, the last job's RunAfterJob shell was not run, and the tape was not ejected. The tape was ejected by hand at 17:00 and substituted with new one. No job was on the queue after 16:00.
- 1st setup ran the job at 11:00pm. This morning I found it was still waiting for the volume.....but the correct volume was inside the LTO!!!!....I had to run mount again by hand!! WHY?!?!?
- 2nd setup ran everything fine.

This is the SD config:

Device {
  Name = QUANTUM
  Media Type = LTO
  Archive Device = /dev/rst22
  AutomaticMount = yes;
  AlwaysOpen = no;
  RemovableMedia = yes;
}

Gabriele Bulfon - Sonicle S.r.l.
Tel +39 028246016 Int. 30 - Fax +39 028243880
Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY
http://www.sonicle.com



----------------------------------------------------------------------------------

Da: Dave Dmytriw - NetCetera <[EMAIL PROTECTED]>
A: Gabriele Bulfon <[EMAIL PROTECTED]>
Cc: bacula-users@lists.sourceforge.net
Data: 26 ottobre 2005 18.57.31 CEST
Oggetto: Re: [Bacula-users] Device BLOCKED

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Gabriele,

This may be a red herring - but I have noticed - and I am not sure of
the exact circumstances - that even though you stop the bacula daemons,
there may be "orphaned" (for lack of a better word) bacula-dir
daemon(s) still running on the system.

The easiest way to find out is probably to execute

ps -ef | grep bacula

after you have stopped bacula. I have seen these orphaned processes
quite frequently.

Dave

Gabriele Bulfon wrote:
> Hello,
> thanx to your suggestions, I think I came up with a good configuration
> for my daily full backup.
> But I ran into a strange situation I don't understand.
> I have two same installations, with this new good config active since
> Monday.
>
> On Monday night:
> - 1st setup had the correct volume inserted, and backed up everything
> correctly.
> - 2nd setup had an erroneous volume inserted (the Tuesday one). Bacula
> started sending email requests to insert the correct Monday volume. I
> had 4 jobs waiting. Each job has a MaxWaitDelay of 16h. Jobs starts at
> Monday 11:00pm with 5 mins offset each. One of the jobs was still
> requesting the correct tape at Tuesday 5pm (the others were already
> marked as canceled), so I had to cancel this job manually to be sure
> that the new nightly backup was correctly run...Why?!
> I expected Bacula to cancel all jobs withing 16 hours (Tuesday 3pm).
> Also, when I ran the cancel command, I was presented the choice of the
> job, with the list of the 4 jobs, as if they were all waiting. But when
> I canceled the one I presumed to be still waiting, all of them
> disappeared, and had no more jobs waiting.
>
> Then comes Tuesday night.
> Consider that my config has AutoMount turned on, and has the last
> Catalog backup job running an external script to eject the tape.
> Obviously on Monday the 1st setup ejected the tape, the 2nd one did not
> eject the tape (because jobs were waiting and I had to manually cancel).
> Because I wanted to lower the MaxWaitDelay to 12 hours, I stopped and
> restarted the Bacula daemons on both Machine on Tuesday evening (before
> the new jobs times).
>
> On Tuesday night:
> - 1st setup ran everything fine.
> - 2nd setup did not run the new job, waiting for human intervention! I
> found the status of the storage unmounted and BLOCKED. I had to manually
> mount the device, and after few seconds I got the Bacula message stating
> that the tape was being recycled and jobs were released and started. Why?!
>
> Gabriele.
>
>
> <http://www.sonicle.com>
> Gabriele Bulfon - Sonicle S.r.l.
> Tel +39 028246016 Int. 30 - Fax +39 028243880
> Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY
> http://www.sonicle.com
>

- --
Dave Dmytriw
Principal, NetCetera Solutions Inc.
Calgary, AB
403-703-1399
[EMAIL PROTECTED]
http://www.netcetera-solutions.com
"It's about using NetWorks, Etc..."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDX7V7DcivrcMaKcIRAkJGAJ9nn7t6PRXiqre5poPHhTH/JoJY/ACcCDgO
ya16MowjktPC7sYvaPDEnI8=
=gfWA
-----END PGP SIGNATURE-----




Reply via email to