{"id":56662,"date":"2023-03-14T09:00:39","date_gmt":"2023-03-14T08:00:39","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=56662"},"modified":"2023-03-11T17:00:26","modified_gmt":"2023-03-11T16:00:26","slug":"nakivo-v10-8-how-to-merge-backup-jobs","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/nakivo-v10-8-how-to-merge-backup-jobs\/","title":{"rendered":"Nakivo v10.8: how to merge backup jobs"},"content":{"rendered":"

\"nakivo-v10-8-how-to-merge-backup<\/p>\n

One of the new cool feature provided by Nakivo Backup & Replication v10.8<\/a> is the capability to merge backup jobs<\/strong> of the same type.<\/p>\n

When two or more jobs are merged, the process doesn't require a full backup<\/strong> if already existing in the original jobs allowing to save a lot of time.<\/p>\n

 <\/p>\n

How to merge backup jobs<\/h2>\n

This feature is very useful if you want to have a better organization<\/strong> of your backup environment by removing obsolete backup jobs<\/strong> or to adopt for example a new name convention<\/strong>. This can be done now by merging a backup job<\/strong>\u00a0into an existing one without the hassle of recreating a new backup chain<\/strong> that requires time.<\/p>\n

For example you may need to re-organize some backup jobs<\/strong> belonging to a specific department because it has been renamed or merged with another one. So far the only way to achieve this goal would have been creating new backup jobs<\/strong> (then a new backup chain) with a new full backup to process<\/strong>. This means time invested by the IT staff for the new configuration, time to process the new full backups, more storage space consumption and so forth.<\/p>\n

With the new merge backup capability<\/strong>, this change can now be done quickly and it works for backup jobs of the same type<\/strong>.<\/p>\n

 <\/p>\n

How it works<\/h4>\n

When a merge operation runs, the following occurs:<\/p>\n