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?īut 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. vmx file wasn’t either added or removed by me, but it remains unchanged by Veeam in both restore scenarios above. In all of the VMs I’m talking about here, the line entry uuid.action = "keep" line in the VM’s.
vmx file, and again 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 so the original MAC Address will be used. Please correct me if I wrong in any of what follows:Ī 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. 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.
0 kommentar(er)
