How Job Merging Works

Product version: 10.8

Last modified: 2 November 2022

Question

How does job merging work?

Answer

The job merging feature allows you to merge jobs of the same type. The resulting job does not require a full backup (or copy of the backups in case of a backup copy job) if it was already created in the original jobs. Job merging requires a source job and a target job. During the merge, the following occurs:

  • The workloads/backup objects are copied from the source job to the target job. If the source job uses Policy view and the target job uses Hosts & Clusters/VMs & Templates/Jobs & Groups/Backup Repositories view, the workloads from the source job are copied over to the target job.

  • The settings configured on the Destination, Networks, and Re-IP steps of the target job creation process are used after the merge.

  • The target job’s retention and schedule settings are used after the merge.

  • In case the recovery points created by the source job before the merge have expiration dates, the expiration dates are maintained after the merge.

  • The settings configured on the Options step of the target job creation process are used after the merge with a few exceptions:

    • App-aware mode: If the app-aware mode was enabled for the source job and disabled for the target job (or vice versa), it will be enabled for the merged job. Note that these settings are enabled only for those items for which it was enabled in the source and target jobs.

    • Full Backup settings: These settings are only displayed after the merge if either the source or target job was using a repository with Incremental with full backups data storage type selected.

    • Truncate Exchange logs: If this option was enabled for the source job and disabled for the target job (or vice versa), it will be enabled for the merged job.

    • Truncate SQL logs: If this option was enabled for the source job and disabled for the target job (or vice versa), it will be enabled for the merged job.

    • Transporter settings: If the target job Transporter selection settings cannot be applied to the source job objects, the merge fails.

  • Once the job merge is done successfully, the source job is removed automatically.