#1 Global Leader in Data Resilience

How to Clone a Job and Map Existing Backups to Clone

KB ID: 2015
Product: Veeam Backup & Replication | 12 | 12.1 | 12.2
Published: 2015-03-13
Last Modified: 2024-08-16
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Feature License Requirement

Consider the following:

  • Starting in Veeam Backup & Replication 12.1 (build 12.1.0.2131), the job cloning functionality is available for all types of licenses.
  • Prior to Veeam Backup & Replication 12.1 (build 12.1.0.2131), the job cloning functionality required an Enterprise or Enterprise Plus edition when using a legacy socket-based license.

Purpose

This article documents the procedure for cloning a backup job and then remapping the existing backups from the original job to the cloned job.

Cause

This method is often used to isolate an issue or to work around a problem within the database related to the original job.

Note: A backup set can only be mapped to one job at a time.

Solution

To clone a job and map the existing files to the new clone job, follow the steps below:

Part 1: Clone the Job

  1. Right-click the job to be cloned.
  2. From the context menu, select Clone.
Clone Job
  1. (Optional) Rename the original job and rename the clone to have the old job's name.

Part 2: Map the backups from the original job to the cloned job.

  1. Edit the clone job.
  2. On the Storage tab, click Map backup.
Map button
  1. Select the appropriate set of backups.
Select backups to map
  1. Select yes when prompted with a notification stating:
    Selected backup is already in use by the following job: ‘<old job name’.
    Do you want to map it to this job instead?
    
confirm map
  1. Click Finish to commit changes to the job.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.