Re: [Bacula-users] Why are copy jobs creating incremental jobs?

2018-06-15 Thread Mariusz Mazur
pt., 15 cze 2018 o 13:52 Martin Simmons  napisał(a):
>
> > Yup, you're right, in the db they're all marked as copy/full and not
> > backup/incremental as the emails and director claim. Weird. (Also – does
> > not happen with all jobs, copying my catalog correctly marked it as full.)
>
> The difference with the catalog backup is probably the level Job definition in
> the config (always Full).

That's an interesting idea. I'll switch all my jobdefs to level=full
(that always gets overridden in jobs/schedules anyway) and see if that
works as a workaround.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Why are copy jobs creating incremental jobs?

2018-06-14 Thread Mariusz Mazur
czw., 14 cze 2018 o 16:56 Martin Simmons  napisał(a):

> I've noticed that too, but I think it might just be a bug in the output of
> status dir (it shows the default level for that job name from the config
> file
> instead of the actual level).  If you check the catalog with "list jobs"
> when
> you will probably find that they are full jobs.
>

Yup, you're right, in the db they're all marked as copy/full and not
backup/incremental as the emails and director claim. Weird. (Also – does
not happen with all jobs, copying my catalog correctly marked it as full.)

Anyway, seems it's a known issue: http://bugs.bacula.org/view.php?id=2286
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Why are copy jobs creating incremental jobs?

2018-06-13 Thread Mariusz Mazur
Hi, I'm running bacula 7.4.7 and have a job to occasionally copy recent
full jobs from my full pool to my tapes (Full-Poll -> Tape-Pool).

The gist of the copy job is here:

Name = CopyFull2Tape
Type = Copy
Level = Full
Pool = Full-Pool
Selection Type = SQL Query
Selection Pattern = "
select max(j.jobid) from job j, pool p where
p.name='Full-Pool' and j.poolid=p.poolid and
j.jobstatus='T' and j.type='B' and j.level='F' and j.jobbytes>0 and
starttime>now()-'3 weeks'::interval
group by j.name;"

So I'm explicitly only copying completed full jobs. And yet, the director
gives me this:

27888  Copy Full  0 0  CopyFull2Tape is waiting on max
Storage jobs
27902  Copy Full  0 0  CopyFull2Tape is running
27903  Back Incr  0 0  ca2-regular   is running
27904  Copy Full  0 0  CopyFull2Tape is waiting on max
Storage jobs
27905  Back Incr  0 0  db5-regular   is waiting
execution
27906  Copy Full  0 0  CopyFull2Tape is waiting on max
Storage jobs
27907  Back Incr  0 0  dbc1n1-cfgis waiting
execution
27908  Copy Full  0 0  CopyFull2Tape is waiting on max
Storage jobs

What are those 'Back Incr' jobs? It's confusing.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users