Job and backup chain renaming behavior

[jplace]

Hello,

I want to confirm the behavior of VBR with respect to the renaming of jobs and their subsequent presentation in the Backups > Disk tab.

For context, the particular job in question is an agent backup of a few large drives on a server. Hourly incrementals with weekly synthetic fulls, 2 week retention. I renamed the job but the old name still persists in the Backups > Disk tab and the backup chain file names. As I understand, at least initially, this is intentional behavior.

Will the backup in Backups > Disk rename itself once the old backup chain falls off due to retention? (or when the next synthetic full happens?) If not, is there any way to rename the backup as it presents in the Disk tab, aside from making a whole new job? I'm not really worried about the file name so much as the way it shows in the GUI.

Thanks!

[david.domask]

Hi Joey,

For updating how the backup name looks in the UI under Backups > Disk, you can use the method described in this KB article: https://www.veeam.com/kb2174

Basically, just detach the backups as the article shows, change the job name, and remap it.

As far as I'm aware the name under Backups > Disk won't change unless we "forget" the old backup first; as the article mentions, the old way of doing this caused issues, but detaching from the job and remapping is much better and convenient.

[jplace]

Just tried this and it works perfectly. Thank you for the tip and the article! Had not yet came across that in my Googling journey

Cheers,