Creation and configuration of the new TrendMiner server
The first step in the OS migration process is to set up a new TrendMiner appliance based on the new RHEL9/AlmaLinux 9 OS.
TrendMiner still provides the same deployment options as before and also the installation process is similar as before. All info and a comparison of the different deployment options can be found in our installation guide.
Also the instructions on how to install a new TrendMiner appliance can be found in this installation guide.
Before starting the installation of the new server, please carefully read the following important notes:
The new TrendMiner server does not have to use the same deployment method as the current one. This means it is possible to switch to virtual appliance, single node or SaaS deployment after the OS migration without additional complications.
For existing SaaS customers and customers who switch to a SaaS contract after the OS migration, the migration will be executed by TrendMiner as part of the SaaS agreement.
Technically it is possible to reuse the existing server and migrate 'in place' but this approach is not advised and therefore not documented (also mentioned in our migration FAQs).
The recommended approach is to set up a new Alma/RHEL9 based server next to the existing CentOS/RHEL7 server. This way the new server can be prepared and tested without downtime for the users and without urgency. When going for this approach consider the following:
The host name is not relevant for the correct functioning of TrendMiner but it is important that the "TrendMiner server name" (FQDN) is set to the URL which users will browse to when using TrendMiner. Typically a DNS record gets created on the TrendMiner IP.
The SSL certificate is also based on this DNS name. You can freely choose any server_name as you'd like, however we do not recommend using the same name as the old server since the two domains will interfere with each other. E.g.:
Old CentOS/RHEL7 vm host: tm-test01, DNS record/server_name: test.trendminer.com
New Alma/RHEL9 vm host: tm-test02, DNS record/server_name: test-new.trendminer.com
On the new Alma VM upload an SSL certificate which includes both of the server names as subject alternative names. That means that SSL works on https://test-new.trendminer.com, but after swapping the DNS it will also already work on https://test.trendminer.com and there is no need to request new certificates after the switch.
After performing the OS migration switch the DNS records, such that users can still browse to test.trendminer.com but in the backend they would really be on the new Alma/RHEL9 server.
At the same time the DNS entry is updated also update the "TrendMiner server name" field in Edge Manager to reflect the DNS swap.
.
For the 2024.R2 the system requirements will change. Please make sure to set up the new server following the new system requirements:
Resource
Minimum
Minimum with Embedded Notebooks & Machine Learning Model functionality
Recommended
Important notes
vCPU
16
+ 1 core per 4 active kernels (per user) + 1 core per 8 notebook tiles (per user per dashboard)
16
For servers with high indexing activity, the available CPU's should at least match the configured simultaneous indexing threads.
RAM
64GB
+ 1GB per active kernel (per user) + 256MB per notebook tile (per user per dashboard)
96GB
As of version 2024.R3.0 an additional 32GB of RAM will be required. We would strongly encourage to already provision this additional memory when setting up the new server.
Disk space
SSD, 500GB, 250MB/s
SSD, 500GB, 250MB/s
SSD, 500GB, 250MB/s
Slow disks may heavily impact the user experience or lead to failures. We would strongly suggest to double check the disk speed using the Linux commands provided here: Prepare the Installation
Important
On top of the above requirements TrendMiner requires the memory to be scaled along with the CPUs at a ratio of at least 1-2 and preferably 1-4. In practice this would result in 128GB RAM for a server with 32 CPUs and 256GB RAM for a server with 64 CPUs
For the final step of the OS migration the current and the new server will need to run on exactly the same TrendMiner version, including the patch number, e.g. 2024.R2.1-14.
If the new server was installed with TrendMiner version 2024.R2.1-06 and the current production server is upgraded with a newer 2024.R2.1-14 it will not be possible to restore the backup from the old server on to the new server until the new server is upgraded to 2024.R2.1-14.
Since a backup will be restored on the new server not all configuration steps from the installation guide are required for the OS migration. The following config steps can be omitted:
Uploading a license: the old license will be transferred automatically to the new server.
Connectivity and access management: configured data sources will be migrated automatically to the new server or can be updated as a post-migration step if needed.
Connector/Plant Integration installation: after the migration it will be possible (and advised) to connect to the already installed connector(s).
User management: configured IDPs will be migrated automatically to the new server or can be updated as a post-migration step if needed.
All other configuration steps (SSL configuration, NTP configuration, ... ) should be executed following the installation guide.
Tip
For the SSL configuration of the new server we recommend uploading an SSL certificate which includes both of the server names (old and new) as subject alternative names such that the same certificate is valid before and after the DNS switch.
After the installation, validate that all services are running. Go to ‘Services’ page under DASHBOARD in EdgeManager and confirm all services show a green status.
For the new server at least the same amount of disk space should be reserved. In case the disk was running full on the old server we would suggest to take this opportunity to add additional disk space on the new server.
In case your current installation has custom K3S IP addresses configured, these custom IP addresses need to be configured again manually BEFORE the installation of the TrendMiner software (as also instruction in the installation guide). If in doubt, please contact TrendMiner support.