2x bug reports

[Wallachuck]

Bug #1
If you re-purpose a previously backed up server from VMware to Hyper-V it cannot be backed up.
Workaround: Delete the Veeam configuration database and set up the backup system again.

Bug #2
The email alert subject for the following alert types:
a) [Warning] Potential malware activity detected
b) [Success] Scale-out Backup Repository
cannot be edit to prepend the server hostname the same way you can edit the subject for backup jobs.
Workaround: Modify the subject in the mailflow rules on the email server.

Thank you

[david.domask]

Hi Wallachuck,

1. Can you elaborate a bit more on the process you did there and the issue you had? Was there a Support Case already? If so, please share the case number. Deleting the Veeam Configuration Database is not a needed solution for something like this, so I suspect something else is happening, but from your description it's not clear what process led to the failed backups, and the behavior should be reviewed.

2. Not a bug, but a known feature request. Right now there is not a means to customize the subject, that's correct, but it is a known request.

[Wallachuck]

Hi David,

Thanks for that.

For Bug #1
Start with a physical server and install VMware on it with some VMs then run some backup jobs with Veeam
Then format the VMware server and install Windows Server 2022 with Hyper-V on it. New hostname, new IP.
Convert the old VM's in the VMware backups to Hyper-V format and copy them to the Hyper-V server and run them.
Point Veeam at the re-provisioned physical Hyper-v server and it will fail to backup with error: "On-host proxy requires upgrade before it can be used" even if you uninstall/re-install the proxy apps from add-remove programs.
Quick fix: Delete the configuration data base and start again.
Hope that helps. I assume there is something in the configuration database like a MAC or serial number that makes it think it's still a Vmware server. It's probably a very rare occurrence to re-provision a physical server from VMware to Hyper-v but there may be more companies doing in future this due to the VMware price increases since Broadcom took over.


For Bug #2
That would be a great feature to add. Thank you.

[david.domask]

Hi Wallachuck,

Thank you for explaining the situation in more details. While I have an idea what would need to be checked if this were an active case, depending on the specific steps taken when adding the repurposed server may introduce this. Very likely it is matching on BIOS UUID and depending on a few factors, I could imagine this behavior.

The good news is that a new configuration database is _NOT_ required for this situation, Veeam Support should be able to identify such issues pretty quickly. So should anyone find this moving forward, I would strongly recommend Open a Support Case; in all likelihood, this can be resolved without recreating the Configuration Database.