[Bacula-users] MaxWaitTime and auto cancel a job waiting for a tape?

Setting Max Wait Time to 7 minutes didn't work! I've had the same issue Job canceled just after started. Any other alternatives? +-- |This was sent by jalil1...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.

[Bacula-users] MaxWaitTime and auto cancel a job waiting for a tape?

bconsole cancel command cancels jobs manually using jobid! I need to cancel it automatically and immediately when it requires a tape, and no tape or not the expected tape is in the drive? +-- |This was sent by jalil1...@gmail.c

[Bacula-users] MaxWaitTime and auto cancel a job waiting for a tape?

Will "Maximum Open Wait" do the trick? +-- |This was sent by jalil1...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--

[Bacula-users] MaxWaitTime and auto cancel a job waiting for a tape?

So how to auto cancel a job waiting for a tape? +-- |This was sent by jalil1...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ---

[Bacula-users] MaxWaitTime and auto cancel a job waiting for a tape?

I read in this link http://marc.info/?l=bacula-bugs&m=127548196026667 that The current definition of MaxWaitTime take the following status in account: JS_WaitFD JS_WaitSD JS_WaitMedia JS_WaitMount JS_WaitStoreRes JS_WaitJobRes JS_WaitClientRes JS_WaitMaxJobs JS

[Bacula-users] Why "Wrote label to prelabeled Volume..."?

Why Bareos/Bacula write label while I've already labeled it? "Wrote label to prelabeled Volume "Volume01" on device "Device01" (/dev/nst0)" +-- |This was sent by jalil1...@gmail.com via Backup Central. |Forward SPAM to ab...@back

[Bacula-users] Upgrade from Incremental to Full issue?

Got it! The incremental backup is based on the full backup executed with: - The same Job name. (in my case I have different jobs: Job1 and Job2) - The same Client name. - The same FileSet (any change to the definition of the FileSet such as adding or deleting a file in the Include or Exclude sec

[Bacula-users] Upgrade from Incremental to Full issue?

I have Job1 : Client1 Storage1 Schedule1 (Tue at 21:00) Pool1 (Volume1) Fileset1 Full Job2 : Client1 Storage1 Schedule2 (Wed at 22:00) Pool2 (Volume2) Fileset1 Incremental I run Job1 manually successfully on Volume1 (Full). But when running Job2 I got: No

[Bacula-users] Prevent sending "This command can be DANGEROUS!!!" email?

My Message contains: mail = myem...@mydomain.com = all, !skipped operator = myem...@mydomain.com = mount console = all, !skipped, !saved When I run a job that contains: RunScript { Console = "purge volume=Volume5-Thu" RunsWhen = Before FailJobOnError = Yes RunsOnC

[Bacula-users] Prevent auto upgrade to Full? First weekday? Purge before?

1- How to prevent an Incremental job from be upgraded automatically to Full backup if no previous Full backup was done? (Cancel the job instead upgrading it) 2- Which is the First weekday regarding to the below clauses: Monday or Sunday? = sun | mon | tue | wed | thu | fri | sat w00 is no

[Bacula-users] How to define Schedules and Jobs in this case?

* 2 file daemons: fd1 and fd2 * 5 tapes and 5 pools: tape1 labeled on pool1, ..., tape5 labeled on pool5 * 5 file sets: Fileset1-Fileset4 on fd1 + Fileset5 set on fd2 * 2 weeks cycle: Sunday 1: Fileset1(Full) + Fileset2(Incremental) + Fileset3(Incremental) + Fileset4(Incremental) + Fileset5(Incr

[Bacula-users] Confused: Volume, Storage, Pool, Job

Exemple: Job { Name = Job1 Type = Backup Level = Full Client = vm-omv-fd FileSet = FileSet1 Schedule = Schedule1 Storage = Storage1 Pool = Pool1 Messages = Message1 } Pool may contain many volumes. What's the advantage of multiple volumes in a pool? Volume: is a label of a sto