Veeam File Name

[handian.sudianto]

Hello,

Usually veeam backup will set the full name like '01.CUCM.PUBSD2023-04-22T171300_C449' and '01.CUCM.PUBSD2023-04-30T170012_6C95' for incremental.
Today i check some vm having different name like 'JKTAV01.vm-2061D2023-04-29T182711_8FC0' for full backup and 'JKTAV01.vm-2061D2023-05-04T182442_2D6C' for incremental. There are .vm in the file name, what is this? should i worried about this naming format?

[Mildur]

Hi Handian

No, you don't need to worry about. vm-2061 is an identifier from a vSphere VM.
We add those since a few versions to the backup file name.

Best,
Fabian

[handian.sudianto]

Hi Fabian,

Thanks for your confirmation

[biplob9s]

Hi Mildur,

i also find this today.
Previous File Name# XC_SERVERSD2024-11-04T001038_63C0
Present File Name# X2.vm-1026D2024-11-09T010005_FED8
with vm name. i don't want like this because there is long VM list.

can it depend on version.

[Mildur]

Hi biplob9s,

Yes, we've adopted the new naming scheme (vm-*****) for some versions now. However, it seems your concern isn't about this.

It appears your previous file name used "per-job backup files (Single file backup)", and now it's "per-machine backup files".
Since v12, "per-machine backup files" is the default, and it's mandatory for backup copy jobs. You can read more about the backup chain types here.

i don't want like this because there is long VM list.

You mentioned a concern about too many files. Could you maybe explain why it is an issue for you? Many of our large customers handle hundreds of VMs in a single backup job, resulting in thousands of files in one folder, without issues.

Best regards,
Fabian