Purging Migrated Jobs

[Leo L. Schwab]

I have two pools that hold full backups, named very creatively `FullFile` and `FullFile-Archive`.  Every so often, I launch a migration job by hand that moves full backups older than six months from `FullFile` to `FullFile-Archive`.

When I set this up, I was under the impression that, once migrated to `FullFile-Archive`, the original job(s) on `FullFile` would be purged, or otherwise marked as "don't care," allowing the volume to be purged/truncated once all jobs were migrated off it.  Indeed, the Migration and Copy docs state:

"In case of a migration, the original job is purged from the catalog database immediately after the copy is completed."

However,  the rest of that same page is careful to state that only the job's file records are purged.  Further, the page drops an oblique hint about a Job definition field named `Purge Migration Job` (default: false).  The result is that volumes in `FullFile` are not freeing up as I'd like, with several volumes containing nothing but migrated jobs.

So: To allow the volumes in `FullFile` to free up, must I add a `Purge Migration Job` field to the migration control job definition and set it to True?  Further, how can I clear all the migrated jobs off `FullFile` so that its volumes can be truncated/recycled?

Thanks,

Schwab

[Bruno Friedmann (bruno-at-bareos)]

Just to clarify your request: what's happen when your FullFile volume hit their retention, aren't they prune and purged ? Which is what (I guess for the moment) the documentation expect. A normal volume retention recycle happen.

Jobs that have `priorjobid` not equal to zero are jobs that are a copy or migration, allowing you to find the one that have not yet been migrated.