One of our production servers (a SQL Server host) was "cloned" to make a secondary test environment. The source server is a virtual machine (VMWare vSphere environment) joined to a domain and with a static IP address.
When the cloned VM was powered on, the virtual network adapter was enabled. The computer name was not changed. Neither was the IP address. Somehow, those two servers with the same DNS name and IP address co-existed on the same domain for several days--maybe as much as a week.
Each server was running identical SQL Agent backup jobs. Backup jobs for exactly one of the two servers would fail every time. The email alert I received referenced the DNS name of the server, so I don't know which server "won". I now have up to a week of db backups that are inconsistent at best, and possibly worthless. I have to compare data from both servers and try to determine if sql transactions intended for the source and transactions intended for the clone were applied to both servers or one server. If it was one server, was it consistently the same server? I fear there may be a "cross-contamination" mess to clean up.
Whether it's carelessness or ignorance, people make mistakes. I can accept this. So let's assume it might happen again. I know how to fix the problem. But how do I detect it?
Note: I am not looking for instructions or advice on how to clone a VM. I am not the one given that task. I'm wondering if there is a way to quickly (or immediately) detect when two computers/workstations/VM's have the same DNS name and/or IP address.
Dave MasonSeminole County, FL