I have a lot of jobs that are getting a new naming convention.
The old way to do this was remove from the job from the configuration, modify the folder name on the repository, rename the job, rescan the Repo, then map the back files to the job. I found there is an updated way to do this and is a welcome feature to save time.
To go one step further, it is not recommended to use the remove/rescan method due to the fact the files get new identifiers that cause the restore points to be seen as new data by all tape and cloud storage offload jobs.
To test it, lets create a new job.
In my case it’s called “___TEST_NAME_CHANGE” to keep it at the top of my screen.
Next, after running a job, we will click “Disk” on the left to make sure there is a backup on the Repository. It’s similar, but it’s not quite the same screen. 
Now, return to the Backup page, right click your Backup job, click edit, and lets rename it.
On the Backup Job page you can see it’s been renamed.
On the Disk page we see it has the old name still. It doesn’t update here automatically.
Right click the backup on this page, then click detach from job.
Agree to the warning letting you know the next run will be an active full and the detached backups will be found under the Orphaned node.
To verify, check the Orphaned section to see if the job is there. Notice it’s still using the old name.
Now lets go back to the Backup page one more time.
On the Backup page, right click the job and then click Storage. Here you will see the “Map backup” option
Map the job back to the detached backup. (original name)
And success. Looking at the backup under Disk we see the job as been renamed.
No rescan necessary or logging into the Veeam repository servers and manually renaming folders. This is a large time saver when you have many jobs.
My next step will be using PowerShell to do this in scale without the extra steps required.
