Would like to restore a virtual machine backup to existing production environment where the original VM is currently running.
This outlines resolving potential computer naming and IP address conflicts.
Would like to create a duplicate of an existing production virtual machine as it existed at a specific point in time while eliminating the name and address conflicts that will occur .
These steps will resolve the IP address and computer name conflicts that will occur from this action.
Follow the steps below if the virtual machine has already been restored to the active network segment and need to resolve the IP address and computer name conflicts
If the virtual machine is using DHCP for its IP address configuration then there will be no potential for duplicate IP addresses. If static address is used for original source virtual machine, then there will be an IP addressing conflict when the newly restored virtual machine is powered on. (this could have a negative impact on your production VM being accessible. See steps below.
Determine IP address of original production virtual machine
Configure the newly restored virtual machine with a different static IP address or use DHCP for the dynamic addressing
Verify you can ping different network components using IP addresses . on the network from the new VM.
Verify you can ping different network components using the Fully Qualified Domain Name.
To adress the naming conflict that will ocurr follow the steps below.
From the systems control panel. select SYSTEM
Change the computer name for this machine with one that is unique and not in use.
Verify this by pinging the FQDN of the machine and by issuing an NSLOOKUP (vmname) command from the command prompt.
IE...NSLOOKUP MYVMNAME followed by PING MYVMNAME
