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 <https://docs.bareos.org/bareos-24/TasksAndConcepts/MigrationAndCopy.html> 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 -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bareos-users/4acfb6fd-094c-42f9-933a-bde9923463c0n%40googlegroups.com.
