We have GVPs + T-Servers downtown, GVPs + T-Servers in a suburb east of here, various servers in a data center down by the river, and various servers in a data center in a suburb west of here. We're consolidating our data centers, so the servers in the western suburb will be moving to the river. Here's the problem: the temperature in the western data center once exceeded 120 degrees Fahrenheit for part of a day, and many of the servers that we are moving out of there fail when we try to bring them back up.
One of the servers we're moving runs: DB Server (7.2), configuration server (7.6), configuration manager (7.6), a DAP for logging (7.2), two message servers (7.1), two SCSes (7.1), and SCI (7.1). We plan on taking a VM snapshot first, setting the MAC to match the MAC on the physical server, and running with the VM copy during the move. If the physical server breaks, we'll have to stay on VM until we can rebuild the physical server on new iron.
Genesys used to be touchy about supporting VM. They once told us everything had to be upgraded to 7.5 or they wouldn't support it. We can't spend the time to do that; it's just not realistic right now.
Does anyone have advice on how to handle the move -- e.g., sizing VM, setting MAC address to match, how to check before the move that the VM copy works properly, etc., etc. All advice considered, and thanks in advance.
By the way, we've moving another server, but it just contains our custom call statistics. I'm not too worried about that one. It's the one that runs the configuration manager that concerns me.
We're also cloning our web servers from the western data center to the other data center, but that should be very safe -- the clones are on new iron. And we're copying our FlexLM from existing VM servers in the western data center to VM servers in the other data center.
