Name of Backup Object, Files, or Folder Differs from Job

KB ID: 2174
Product: Veeam Backup & Replication | 9.5 | 10 | 11
Published: 2016-10-06
Last Modified: 2021-10-19
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.

Challenge

The name of the backup object listed under [Backups] > [Disk] is different from the name of the associated job. 

OR

The name of backup files or folders is different from the name of the associated job.

Cause

When a job is renamed its associated backup object, files, and folders are not renamed. 

When a backup is mapped to a job with a different name, the backup object is renamed, but the associated files and folders are not renamed. 

If a new backup set is created, but the folder containing the original backup set is not moved, deleted, or renamed, new backup files will be stored in a folder named <job name>_1.

Solution

It is not necessary to make any changes. However, it is possible to rename the folder containing backup files, and to change the name of the backup object to match the job, if desired. 

  1. Under [Backups] > [Disk], right-click the backup object with the outdated name, and select Remove from Configuration.

    User-added image



  2. (Optional) Rename the folder containing the backup files.
    Note:
    • Rename only the folder. Manually renaming backup files is not supported.
    • If the backup files are on a SOBR, rename the folder on all extents, making sure the new folder names match on all extents.
    • Folder names cannot contain spaces and must be limited to:
      Alphanumeric characters: a-z A-Z 0-9
      Special characters: _-.+=@^
       
  3. Rescan the repository where the backup files are located.

    User-added image


  4. If your backup files are encrypted, you will need to specify the password under [Backups] > [Encrypted]. If your backup files are not encrypted, skip this step.

  5. The backup chain will now appear under [Backups] > [Imported]

  6. Edit the backup or backup copy job. On the Storage tab, click Map backup and select the existing backup chain.

    User-added image



  7. After clicking Finish in the job settings wizard, the backup object will be found under [Backups] > [Disk] and the name will change to match the job.

More information

Spaces and certain other characters in job names will be replaced with underscores in file and folder names.

Some backup files are never renamed, whereas others are renamed automatically during each job session. Automatic rename can only be prevented for reverse incremental backups configured as described in KB1076.
Click here to send feedback regarding this KB, or suggest content for a new KB.
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.