Hi folks,

I defined to kind of jobs for each machine I want to backup:

   - a full backup job


   - a incremental backup job

Furthermore I use different pools and volumes related to the backup type.

Full backups work fine like expected - no problems. 

Starting my first incremental backup after an already performed full backup 
creates a further full backup but using incremental pool and volumes. The 
second and all following incremental backups on the other hand really 
perform as incremental backups.

Error messages from 1st incremental backup performed as full backup:

2020-01-08 14:36:59 bareos-dir JobId 35: No prior Full backup Job record 
found.
2020-01-08 14:36:59 bareos-dir JobId 35: No prior or suitable Full backup 
found in catalog. Doing FULL backup.
But the full backup really exists, have a look:

+-------+-----------------+---------+---------------------+------+-------+----------+-------------------+-----------+
| jobid | name            | client  | starttime           | type | level | 
jobfiles | jobbytes          | jobstatus |
+-------+-----------------+---------+---------------------+------+-------+----------+-------------------+-----------+
|    34 | bareos-full-1m  | bareos  | 2020-01-08 14:29:05 | B    | F     
|   50,934 |     2,793,407,421 | T         |
|    35 | bareos-incr-1m  | bareos  | 2020-01-08 14:37:01 | B    | F     
|   50,935 |     2,802,456,353 | T         |
|    36 | bareos-incr-1m  | bareos  | 2020-01-08 14:49:59 | B    | I     
|       80 |       270,945,443 | T         |
+-------+-----------------+---------+---------------------+------+-------+----------+-------------------+-----------+

So why doesn't bareos don't find it?

Any idea what's going wrong? 

Thanks in advance,

moose

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/9c5a81ba-07f1-4f25-8db1-06a3690c1c34%40googlegroups.com.

Reply via email to