Why does Bacula (Bareos) create a full backup for each type of backup?

Question

Backup

Greetings!
Installed, configured Bareos (Bacula fork), manually launched a FULL backup.
Today it's time to make an incremental backup, and she began to create a new full one, in the log:

2016-04-29 17:25:21 MainServer-dir JobId 3: No prior Full backup Job record found.
2016-04-29 17:25:21 MainServer-dir JobId 3: No prior or suitable Full backup found in catalog. Doing FULL backup.

Although the full backup completed successfully before that.
The same goes for differential backup.
Is this how it should be or am I setting something up wrong?
It's a pity to give 30% of the space for dead weight...
Job setup for the client:

Job {
  Name = "Backup Desig INC"
  Client = Desig
  FileSet = "desigFileSet"
  Type = Backup
  Messages = Standard
  Level = Incremental
  Pool = Incremental
  Storage = MainStorage
  Schedule = "EveryDayAt5PM"
}

Job {
  Name = "Backup Desig DIFF"
  Client = Desig
  FileSet = "desigFileSet"
  Type = Backup
  Messages = Standard
  Level = Differential
  Pool = Differential
  Storage = MainStorage
  Schedule = "EveryWeekAt5PM"
}

Job {
  Name = "Backup Desig FULL"
  Client = Desig
  FileSet = "desigFileSet"
  Type = Backup
  Messages = Standard
  Level = Full
  Pool = Full
  Storage = MainStorage
}

Answer 1

In general, I don’t know if you found a solution, I found it.
The bottom line is that each of the Jobs is an independent unit that creates a separate counter for itself in the directory. I.e

Job {
  Name = "Backup Desig DIFF"
...
}

Knows nothing about what he did

Job {
  Name = "Backup Desig FULL"
...
}

Even despite the fact that they use a common Volume. The essence of the backup is that we must describe for one Job how and where it will make backups of different types. Here's what I came up with

Job {
  Name = BareosConfBackup
  Client = gazer-fd
  Type = Backup
  Level = Incremental
  Pool = IncBareBup
  Full Backup Pool = FullBareBup                 # Раз
  Differential Backup Pool = DiffBareBup     # Два
  Incremental Backup Pool = IncBareBup     # Три
  File Set = BConfig
  Schedule = WeeklyCycle
  Priority = 10
  Write Bootstrap = "/var/lib/bareos/%c.bsr"
  Messages = Standard
}

Schedule {
  Name = WeeklyCycle
  Run = Level = Full 1st sun at 23:00                        # Раз
  Run = Level = Differential 2nd-5th sun at 23:00     # Два
  Run = Level = Incremental mon-sat at 23:00          # Три
}

We get that this task, every first Monday of each month makes a full backup, from the second to the fifth Monday it does Diff, and every week from Monday to Saturday it does Incr
And to run this task in the console with a certain level, you need to run it like this
something like that.

Answer 2

No prior Full backup Job record found.
Probably, the previous Full Backup was rotated. This is not a good situation, it means that if something does not work out, there is no full backup. I advise you to try Restore immediately after creating a full backup, to make sure that everything is ok, and then look for where it disappears.