I walked in to a very disorganized configuration/setup of Exchange have a question regarding a migration to a new Exchange server. Here is my scenario:
- I have a DAG with 3 nodes (however, there are 5 Exchange servers in total, and there does not need to be)
- Exchange logs and databases (for active and passive nodes) are on a drive (LUN) that is attached to a SAN
- 3rd Node is our office in China (which will be evicted soon, leaving only my active and passive nodes)
- There is a server (we'll call it EXC02) that is part of the Exchange forest, but does not show up in my EMC. However, if
this server is down, our China office is affected for some reason???
- EXC01 is my Active Node, and EXC03 is my passive node. There are database copies maintained on both these servers.
What I want to do:
- Move primary Exchange server from EXC01 to a new EXC01 (already built, but not yet on the network)
- There are currently 16 databases for just one office, so I want to consolidate those databases into about 4 and move them off the SAN on to the new EXC01 box. However, I would like to minimize impact by doing this (was thinking building 4 databases on new server, then performing local move requests of users to that box? Or should I just dismount the databases and move the database path location to the new server? One is much more impactful than the other). Also, would I have to bring down the primary Exchange server to bring up the new one?
- Create a new certificate that fixes the issues with the current certificate in the subject alternative names.
I'm moving the company to a new Exchange server because of this setup. I'd like to just rebuild the setup with 2 Exchange servers (keeping the existing passive node). We are also going to a hybrid deployment of Office 365. I've got the ADFS and all the things I need for this in place. That being said, is it still necessary to keep the DAG? Or can I just get away from that altogether? I'd really be interested in hearing suggestions. Thanks!!