Sorry, as usual I think I found it within minutes after sending out a request 
for help.
I should have re-read the documentation first, instead of afterward.

  Selection Type = PoolUncopiedJobs

I had left it at PoolTime and reduced the time to 1 minute.


-----Original Message-----
From: Luc Van der Veken [mailto:lucvdv AT wimionline DOT com] 
Sent: 28 October 2014 8:31
To: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] Migrate: copy or duplicate?

Sorry if this is a stupid question, but with copy instead of migrate, how do 
you keep Bacula from copying the same jobs over and over again each time a copy 
job is being run?

My original backup schema was like this:

* Full backup to disk once a month on Friday night, systems distributed about 
evenly over 1st to 4th Friday, 1 month retention.
* Differential backup the other Fridays, 1 month retention.
* Incremental every Monday to Thursday, with 1 week retention.
** Migrate full and differential backups older than 1 week to tape on Monday.
** Jobs moved to tape get retention of 3 months.  Tapes are stored off-site.

But this meant that
- I got off-site backups only after a full week,
- restores almost always required the tapes to be brought in,
so a few weeks ago, I changed the last two steps into this:

** Changed migrate into a copy job that copies full and differential backups to 
tape on Monday. No minimum age restrictions.
** Retention of jobs on disk 1 month, copies on tape 3 months.


I was used to some fluctuation in the number of tapes per week I needed with 
the first schema, but it started to look a bit ridiculous yesterday, so I 
checked the original job numbers: it was copying the same full backups to tape 
for the third time.


Doesn't bacula keep track of which jobs it has already copied and which not?
Actually this is something that had crossed my mind when I was making the 
changes, but that I dismissed because it has to keep track of those copies to 
promote them to main later, so it must "know" about them.


The job definition for the migrate job that I changed to copy:

# Migration job to move older jobs to tape
Job {
  Name = Transfer to Tape
#  Type = Migrate
  Type = Copy
  Pool = File
  Selection Type = PoolTime
  Messages = Standard
  Client = bacula-main  # required and checked for validity, but ignored at 
runtime
  Level = full          # idem
  FileSet = BaculaSet   # ditto
  Priority = 20
## only for migration jobs
#  Purge Migration Job = yes    # purge migrated jobs after successful migration
  Schedule = TransferToTapeSchedule
  Maximum Concurrent Jobs = 5
}

-----Original Message-----
From: Luc Van der Veken [mailto:lucvdv AT wimionline DOT com] 
Sent: 15 September 2014 13:22
To: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] Migrate: copy or duplicate?

From: Radosław Korzeniewski [mailto:radoslaw AT korzeniewski DOT net] 

> No. All copies goes to database as well, but they are indirectly available
> for restore and are promoted as a main backup only when original job expire.
> I could be wrong about it, but it was working as described last time I've 
> check.

Thanks, it looks like I misunderstood or misread that part of the docs.

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users