Is it possible to relocate a Enterprise Manager Collector to a new server?
I assume it's possible to relocate the smartstor data and configuration after a Collector installation. Does one need to consider deleting the existing collector after the relocation from the PostgreSQL database ts_entity table?
Community: Please respond to Stuart as well with your suggesttions.
Long term answer. I am working with Tech Info on a migration section
>Is it possible to relocate a Enterprise Manager Collector to a new server?
Yes . It is often done
>I assume it's possible to relocate the smartstor data and configuration after a Collector installation.
Yes Copy before restarting EM on new server
I assume you are also making changes to the clusters section of IntroscopeEnterpriseManager.properties
>Does one need to consider deleting the existing collector after the relocation from the PostgreSQL database ts_entity table?
I thought there was am dsiabled field in that table. But not seeing it. So yes to be safe. Of course, please first backup teh database
Further to Hal's advice:
- The MOM IntroscopeEnterpriseManager.properties file has the Collector details so you would need to update that with new Collector hostname and IP Address. Also the same for the MOM loadbalancing.xml if you have customised it from the default and it has the Collector hostname/ip/regex in it.
- For the ts_entity table, shutdown the entire cluster, backup the APM DB (cemdb) and then delete all rows from the ts_entity table. Then restart the cluster to get a clean set of EMs added to the ts_entity table after each EM connects to the database after startup.
If you are installing the EM on a different host, then the MOM Introscope Enterprise Manager properties file has to be updated. Also add the new server IP address to the postgres pg_hba.conf file.
If you are copying an EM directory and then moving it to a different host, then you will need to do a few things in addition to the MOM properties file and adding the new server IP address to the postgres pg_hba.conf file.
There is a file <em home>/config/internal/server/tess.internal.properties that needs to be deleted before you start the EM. If you have started the copied EM, then, you need to shutdown all of the enterprise managers (EMs), delete the tess.internal.properties files on all EMs then delete all rows in the ts_entity table.
In the copy, also you might want to delete the data directories (data and traces), remove all the logs and for good measure, delete all of the caches
Delete the <em_home>/work/Jetty* directories
Delete the <em_home>/product/EnterpriseManager/configurations (only the org.* directories and the .settings leaving the config.ini file)
If you are moving an EM directory to a new host, it is sort of the same as the copy but you don't delete the data directories and in the MOM property file and postgres pg_hba.conf you replace the original IP address with the new address.
And to be just over and safe, create a new enterprise manager directory in your source control system for the new host, and store all of the end-user modified files. I would also suggest source controlling your changes to the MOM properties files and the postgres pg_hba.conf.
Hope this helps,
Yes what Billy Cole notes about the <em home>/config/internal/server/tess.internal.properties file is relevant if you have copied an EM installation to another instance and are starting both the original EM and the copied EM. That is because that file contains a property "entity.guid" which must be unique across EMs for CEM to function correctly (the file is automatically created at startup if it does not exist)
Thanks for the updated details.
Hallett_German, there really really needs to be migration documentation.....
Thanks everyone for the reply's, successfully relocated two collectors to a new host last night.
Great, perfect collaboration, thank you all.