V12 - Naming convention for backup files .vbk .vib

[Vodochnik]

Hello,

i have found some "old" topic (2 years old) vmware-vsphere-f24/when-is-m-w-or-y-add ... 75182.html

Now I'm switching from 9.5U3 to 12 and OMG, filename looks like this: H DFS Server.450738af-de5f-468f-a2e3-60b4f09dD2023-05-03T210126_A17F.vbk
What does this ugly GUID mean? Any chance to move it to the end of filename or get rid completely?

Thanks!

[Mildur]

Hi John

The new naming convention was introduced with Veeam Backup & Replication v11 if I remember correctly.
This ID is received from the Hypervisor. It identifies for which VM this file was created. In your case it must be a HyperV VM.
We cannot remove the GUID from the filename. If you have multiple environments and named the VMs identically, it will lead to issues because of the file name.

May I know what the issue is with the current naming? What use case could we solve by removing the GUID or moving it to the end?

Best,
Fabian

[Vodochnik]

@Mildur
Hi Fabian, thanks for your explanation.

It's all about Übersichtlichkeit, I mean such extensive naming is hard to read.
Moreover, I create file2tape jobs with a script and I notify "filename - size" in description.
And such long names exceeds the limit of 1024 chars for description field quite fast.
Thanks god PS can RegExp so I'm able to cleanup the names to VMName - Date.vbk

Code: Select all

    $vbk.Name -match '(.*?)\.(.*?)(?-i)D(.*?)_(.*?)\.'
    $shortname = $matches[1] + "." + $matches[3] + ".vbk"

Thanks again!