In light of everything we’ve looked at up until now, I must admit I’m struggling to exactly understand the logic of how Veeam manages MAC Address assignments during the various restore scenarios. Please correct me if I wrong in any of what follows:
A straight restore ('Restore entire VM' > 'Restore to the original location') of a VM to its original location maintains its original settings, replacing the original VM altogether, will not touch the uuid.action = "keep" line in the VM’s .vmx file, and so the original MAC Address will be used.
Similarly, restoring a VM to a new location with changed settings (' Restore entire VM' > 'Restore to a new location, or with different settings’), will also not touch the uuid.action = "keep" line in the VM’s .vmx file, and again the original MAC Address will be used?
In all of the VMs I’m talking about here, the line entry uuid.action = "keep" line in the VM’s .vmx file wasn’t either added or removed by me, but it remains unchanged by Veeam in both restore scenarios above.
So, to avoid any MAC conflicts, it looks like the only choices I currently have when using the 'Restore to a new location, or with different settings’ option are, before booting the restored VM, either to manually edit the Veeam restored VM’s VMX file to remove the uuid.action = "keep" line, or alternatively, set the network adaptor MAC address to Manual and paste in a new MAC Address?
But honestly, if I’m restoring a VM – whether using 'Restore to the original location' or 'Restore to a new location, or with different settings’ I should not really have to be concerned about MAC Address assignment and whether or not a conflict will occur. The logic of managing any MAC Address changes needed in the above two scenarios ought to be fully managed by Veeam (just as vSphere seems to take care of any MAC Address changes needed when adding a VM to the Inventory manually).
Taking all this into consideration, my thinking is that it makes no sense for Veeam to offer a 'Restore to a new location, or with different settings’ option if this will then restore a VM with the same MAC as the original, so risking a MAC Address conflict due to the fact that the original VM might still be running on the network.
I think that in the Restore Wizard, there really ought be an option to generate a new MAC address during the 'Restore to a new location, or with different settings’ process (just as VMware gives you a Copied or Moved selection choice). That, or MAC address generation should be better taken care of automatically to avoid potential conflicts for a given restore scenario.
Users browsing this forum: Google [Bot] and 1 guest