I've got an environment that includes 2 main physical sites. At each site is a separate VMware environment, each being controlled by its own virtual center server (I intend to consolidate both environments to one VC Server, but that's in the future). One of my colleagues wants ot move a virtual machine from one environment to the other. Since the virtual machine is being backed up via Galaxy (windows FS Agent and SQL Agent--we have not yet installed Virtual Agent), I thought the easiest way would be to create a new VM where we want to move the old server to, and do a full iData agent restore to the new server.
My rough plan was: do full backup of the existing machine; power it down; create a new VM with the same specs; do a full restore to the new machine, insuring name/IP was correct. Assuming that worked and clients could access the SQL database without issue, I'd then blow away the old one.
Any gotchas anyone can think of? I'm currently running Simpana 9. The 2 physical sites are on different subnets. The new virtual machine will have a new name (we name servers based on location) and differnet IP address (due to the different subnet), but should otherwise be identical, including all SQL instances.
Now, once more, I must ride with my knights, to defend what was--and the dream of what could be!
~King Arthur, "Excalibur"