...
BugZero found this defect 2895 days ago.
The name of the backup job has been changed, causing entries found under the Backups node to no longer match their associated job.
When a job name is changed, the associated backupset entry within the Backups section is not updated.
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.
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.