Veeam Support Knowledge Base
Name of Backups Entry Does Not Match Job Name

Name of Backups Entry Does Not Match Job Name

KB ID:	2174
Product:	Veeam Backup & Replication \| 12 \| 12.1 \| 12.2 \| 12.3 \| 12.3.1 \| 12.3.2
Published:	2016-10-06
Last Modified:	2024-03-04

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

Oops! Something went wrong.

Please, try again later.

Challenge

The name of the backup job has been changed, causing entries found under the Backups node to no longer match their associated job.

In the example screenshot above, the job was first run with the name "Backup Job 1," and after the initial run, the job was renamed to "DC Backup." The Backups entry remains named "Backup Job 1," despite the name of the backup job changing.

Cause

When a job name is changed, the associated backupset entry within the Backups section is not updated.

Solution

Expected Behavior

It is entirely expected behavior that backup sets, files, and folders will not match the job's name if it is renamed. It is not necessary to make any changes.

The procedures documented in this KB are optional and performed only for aesthetic reasons.

Update Backup Set Name

This procedure may be used to update the entry that is present under the Backups Specifically Backup > Disk or Backups > Object Storage.node for backupsets created by the following types of jobsThe list is restricted to these job types because they all have a map backup option.:

VMware Backup
Hyper-V Backup
Windows Agent Backup
Linux Agent Backup Backup
Object Storage Backup
File Backup
Backup Copy

Procedure

Ensure that the job is Stopped and Disabled.
Use the Detach from job feature to disconnect the backups from the job.

Edit the job, use the Map backup button to reconnect the backups to the job, then click Finish.

After the mapping is completed, the entry within the Backups section will move from the Orphaned section back to its original section and have the job's name.

More Information

Note Regarding Previously Documented Procedure

Before the update of this article in 2024 to document the detach and map method, this article described a process wherein the user would "Remove from Configuration," modify folder names, rescan the repository, and then remap the backup files to the job. While still supported, this procedure has been discontinued and is no longer recommended. Removing and rescanning causes the backup files to be assigned new identifiers in the Veeam Backup & Replication configuration database. These new identifiers cause those restore points to be seen as new backup data by all tape and cloud storage offload jobs, resulting in those restore points being written to tape or offloaded to the cloud storage again.

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

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

Product

Topic

Description

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

I would like to receive a follow-up email regarding my feedback

Verify your email to continue your product download

We've sent a verification code to:

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!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.