Moving Exchange Server Inhouse

[SG-VTM]

Greetings,

We are looking to move our exchange server inhouse. It currently resides in a colo unit.  It is set in a VM so current plan is taking current backup of VM, turning it off, then migrating it within our network.  All current Exchange configuration will stay the same but will have new IP addresses.  What are the implications to our Enterprise Vault environment that we need to be aware before migrating?

Thank you in advance!

SG

[ChrisLangevin]

If all that is changing is the IP address, then so long as DNS properly returns the new IP address for the existing name, EV should not care one whit. EV knows your Exchange server's name and some of its AD DNs, but not its IP.

--Chris

[SG-VTM]

Thanks for your response, Chris!

It sounds like it will get automatically picked up or do we have to add or edit the IP Address manually?

Thank you again!

Sam

[GertjanA · Accepted solution]

Hi Sam,

As Chris says, EV targets the Exchange server based on name. If the name stays the same, EV will connect (as long as DNS obviously is properly updated to reflect the new ip-address for the Exchange server).

What you can do:

Set tasks in report mode, restart. Set backup mode. Move exchange servers. When online again, restart EV services, or reboot server. When up and running again, run the provisioning task. If EV can't connect to Exchange, you 'll see here it fails. When ok, clear backup mode, then remove report mode.

[SG-VTM]

Perfect, thank you again Chris and GertjanA for the information!

Best Regards!

Sam