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

Welcome!
Installed, configured Bareos (Bacula fork), have launched manually the FULL backup.
Now is the time to be incremental bekapy, and she began to re-create the full, 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 a full backup was completed that successfully.
The same goes for differential backups.
This is as it should be or I something not so adjusted?
Pity 30% of the space to pay for dead weight...

Setting Job for 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
}
July 12th 19 at 16:57
2 answers
July 12th 19 at 16:59
Solution
In General, don't know if you found a solution that I found.
The point is that each of the Job - an independent unit that creates a separate counter in the directory. That is
Job {
 Name = "Backup Desig DIFF"
...
}

Knows nothing about what he did
Job {
 Name = "Backup Desig FULL"
...
}

Even despite the fact that they share a common Volume. The essence of backup is that we have one Job to describe how and where it will make backups of different types. Here's what I came
Job {
 Name = BareosConfBackup
 Client = gazer-fd
 Type = Backup
 Level = Incremental
 Pool = IncBareBup
 Full Backup Pool = FullBareBup # Times
 Differential Backup Pool = DiffBareBup # Two
 Incremental Backup Pool = IncBareBup # Three
 Set File = 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 # Again
 Run = Level = Differential 2nd-5th sun at 23:00 # Two
 Run = Level = Incremental mon-sat at 23:00 # Three
}

We find that this assignment, every first Monday of each month make a full backup, from the second to the fifth Monday makes a Diff, and every week from Monday to Saturday does Incr
And that would start the task in the console with a certain level, you need to run it so
run job=XXX level=Full #{Differential, Incremental and so on}

something like that.
Found Yes and that's the way it is. - alivia_Torphy commented on July 12th 19 at 17:02
July 12th 19 at 17:01
No prior Full backup Job record found.

Probably, the previous Full Backup atrodaties. It's not a good situation, means that to recover if that does not work - no full backup. Suggest to try a Restore immediately after creating a full backup, just to make sure everything is OK, and then look for where it disappears.

Find more questions by tags Backing upBacula