 |
I don't think this is really major so changed it to minor as its more annoying then an enormous problem. How things currently work the Migrate/Copy Job e.g. not the selection one more or less copies all info from the original Job of which its a going to be a Copy or Migration. So in that sense its works as designed. The set_jcr_defaults() function clones the original Job into a so called mig_jcr which performs the Copy or Migrate and is controlled by an other JCR which is called the cjcr (e.g. Controlling JCR). You could try the following patch and see if that reliefs the problem. diff --git a/src/dird/migrate.c b/src/dird/migrate.c index a421d5c..f90fb87 100644 --- a/src/dird/migrate.c +++ b/src/dird/migrate.c @@ -1171,6 +1171,12 @@ bool do_migration_init(JCR *jcr) */ mig_jcr->IgnoreDuplicateJobChecking = true; + /* + * Copy some overwrites back from the Control Job to the migration and copy job. + */ + mig_jcr->spool_data = jcr->spool_data; + mig_jcr->spool_size = jcr->spool_size; + if (!setup_job(mig_jcr, true)) { Jmsg(jcr, M_FATAL, 0, _("setup job failed.\n")); return false; |
|
|
Thanks Marco, I've patched the sources. I'm currently doing a Full Backup of the whole company data so I will get back with the results when it is over. O. |
|
|
Fix committed to bareos bareos-15.2 branch with changesetid 5894. |
- Anonymous
