Today I created an issue restoring multiple VM's from backup(actually to create a temporary test environment)
I've used the option "Restore to a new location, or with different settings" . The restore location was a different geographical location , different vcenter datacenter, different ESX server and different storage.
The restore started and it went fine. The VM's where restored to the new ESX servers. But then I saw that the original VM's where powered of and deleted. No warning, nothing.
I've done similar things multiple times already, and never had problems. It's worth noting that the other times I did this I probably rename the VM's, and this time I didn't. However, having the same VM name on another Vmware Datacenter is absolutely fine in Vmware vpshere.
Now: I've logged a support case(# 01256668) for this . Long story short: this is "by design".
It's not needed for VMware(same name different datacenter is perfectly fine), it's not needed for the storage(filename issues) as it is on different storage, it's not needed for ESX. Actually the name is not important, at all, in my opinion as all the VM's are referenced by GUID. SO There is absolutely NO technical reason to delete the original VM. I'n my opinion there is no logic in this as well.
Now if Veeam still thinks it's the right thing to do, then a WARNING should be very helpful. Also in the manual there is no indication that it's going to delete the original when selecting a NEW location: http://helpcenter.veeam.com/backup/80/v ... overy.html
I think this is so stupid that I question the person handling this case telling the truth. That's why I created this thread.
- So it's not possible to restore VM's to another separate location without destroying production, UNLESS you do not forget to give every single VM in the job another name?
- Is it logical that the name being the same(although perfectly fine in Vmware) should be the only reason to delete the original with any further user interaction.
- Do you think, as I am, that this "design" is flawed(or at least need refinement such as a big warning and/or a proper manual mention)?