migrate epo and DB server

[Dwee]

hey, just want to ask what is the best choice to move or migrate our epo and DB servers ?

we have epo cluster installation type, with separate DB server, and we just have new DC running up,

The condition that all system that move to new DC will be:

1. changed their IP, hostnames,

2. all VM's will be cloned from old DC to new DC,

question:

A. can we just replicate the epo and DB server ? or any other way ?

B. if point A can be done what happen to the clients communication to epo ?

C. we want all the client (up to date and the deprecated clients) also still showing up on epo

[cdinet]

https://kcm.trellix.com/corporate/index?page=content&id=KB68427 is KB for moving the database to a new server.

This doc is for restoring epo to a new server in a cluster environment.

https://docs.trellix.com/bundle/epolicy-orchestrator-5.10.0-installation-guide/page/GUID-9FF7A875-B4...

If you are just moving vm's to a new environment rather than restoring them to a different system, then there are a couple of considerations.

1. You would need to point epo to the new IP/host name of sql server using core/config db connection page.

2. When the host name of sql server changes, you must also make sure to change it within sql.  See the following Microsoft article.
https://learn.microsoft.com/en-us/sql/database-engine/install-windows/rename-a-computer-that-hosts-a...

3. When you change the host name and IP both of the epo server, you will either have to do some dns redirection to point systems to the new IP, or reinstall the agents.

[Dwee]

Thanks for your reply,

what is the best choice ? between moving the vm's or restoring on different vm's ?

for your consideration we have vm's like epo, db, TIE servers vms, and appliance like : ATD,

and for the note, the user wants to also keep the obsolete or deprecated (last com more than 6 months old),

with the new DC used different IP and hostname but still same Domain as the old DC, 

[cdinet]

That is kind of a toss-up.  With moving the vm's, you retain the install and just have to update settings, but with restoring, you could run into restore issues.  So really that is entirely up to you, but either way, definitely have full backups of databases and file systems for the servers.  Without some good dns redirection, you may have to reinstall agents.  When moving sql server also, you will need to run some scripts to update the sql servername within sql.  See https://learn.microsoft.com/en-us/sql/database-engine/install-windows/rename-a-computer-that-hosts-a...

[Dwee]

yes so were kinda stressed out, 

the OP: 1. restore the epo and the DB to a new server at new DC,

2. replicate the epo and DB Vm's,

those are the points that i want to ask you which one that have less /minor risk and also that we have to retain the deprecated system also,

*backup epo and db always on my list weekly*

[cdinet]

Both options will retain deprecated systems, as they would still reside in the database tables.  The less risk would be to move the vm's, as there is no reinstall of anything that would fail, but either method should work.

[Dwee]

hello again sorry,

just want to make sure more, the less risk that you mentioned @cdinet before which one is it ? the replicate ones ? so about deprecated system solved (as you mentioned that all in DB tables), but how about the different in IP address, hostnames that being used later on at the new DC ?? the only one remain same was the domain, 

[cdinet]

I am not totally clear on your question, but if you migrate the entire vm to the new environment, all your existing systems, policies, etc. remain the same.  If clients get a new IP, they will send that new ip information on their next communication interval.  If epo server name and IP change, then you may have to re-deploy agents unless you can use dns redirection to point the systems to the new name/ip.  If the name on the sql server itself changes, you will also need to run through this to update the server name on the sql server instance.

https://learn.microsoft.com/en-us/sql/database-engine/install-windows/rename-a-computer-that-hosts-a...

[Dwee]

If we just copy  and restore the full *.BAK file from old db server to new vm installed SQL DB server on new DC and test the operational still using the existing epo that still on old DC, do i still need to do this "https://learn.microsoft.com/en-us/sql/database-engine/install-windows/rename-a-computer-that-hosts-a...",??

i have done this db migration task before, the changes only from express on the same server as epo move to new sql db server standard version with changes in  IP and hostname, i just reconfig on core/config url and the port setting on sql , 

i'm confused on epo  migration part itself,

[cdinet]

You only do that if the server that sql is installed on has a server name change.  If you are just restoring a database to an existing sql server on a functional sql server, that is not necessary.