How to migrate one node in a three node exchange 2016 dag

I need to move one node of our exchange 2016 dag to a new data center. I can't seem to come up with any information on the best way to handle this. Can I just add an additional subnet to the dag prior to the move? Then change IP on the server after the move. Are there any additional steps needed?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MASEE Solution Guide - Technical Dept HeadCommented:
Hi Firstcom,
Note that a cross-subnet DAG needs some special consideration. Look at the section conserving multi-subnet DAGs
You will need a new, additional ip address for the existing DAG cluster name for the new subnet in DNS and associated with the DAG object itself in Exchange!
Please check this for detailed explanation.
FirstcomAuthor Commented:
Thanks for the response. This is already a cross-subnet dag. Our DR site is moving to a new datacenter. So I have two nodes in our main site and one node in the DR site which will be moving. In looking at the detailed explanation we don't currently have the exchange servers explicitly defined in our AD sites and services. The subnets are all present etc.
MASEE Solution Guide - Technical Dept HeadCommented:
You have to properly configure ADSites and services properly.
Suspend the database copy on the server to move.
Then move the Server physically.
Start the server and assign an IP from the new ADSite subnet.
Resume the database copy.

Even if you remove the database copy from DAG but database and log files are still on the server, when you add the  database copy back, it will start the seeding from the point where it got stopped when you removed the copy by picking up existing DB/Logs...
Mainly you need to take care of virtual directories URLs and server shows up in correct AD site once you move it (nltest /dsgetsite)
Also make sure you add the DAG IP from the new site subnet if it is not IP less DAG...
FirstcomAuthor Commented:
The move of the node went off without a hitch. These are the steps I took to complete.

1. place node in maintenance mode
2. verified that Dag networking was set to automatic. Mine was so i didn't need to do anything else. If it weren't I would have manually added the new subnet.
3. change IP on node and migrate to new datacenter. I accomplished this using Zerto so there was minimal time used to migrate.
4. after move i verified that DNS was updated with the new IP
5. check that the dag detected the new subnet and added it.
6. took node out of maintenance mode and verified the databases were replicating.
7. Done

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MASEE Solution Guide - Technical Dept HeadCommented:
Enough information to confirm answer.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Database Availability Group (DAG)

From novice to tech pro — start learning today.