Frequently Asked Questions
Question: Is it possible to migrate with an on-prem local S3 storage?
Answer: On-prem local S3 storage migration is supported as of release 2024.R2.1.
Question: Is it possible to load all data in the blob storage, deploy the new OS on the existing server and then download the data from blob again?
Answer: Since the new server will run on a new Operating System, it is not possible to truly “install over”. To avoid downtime, TrendMiner recommends preparing the new server in advance of the migration, and therefore does not recommend this approach. However, it is technically possible to avoid having 2 servers/VMs online in parallel by following this high-level procedure:
Upgrade the current system to 2024.R2 and perform the remote backup
Turn off the existing server (if it's a VM: do not delete it!)
Create a new server with at least the minimum system requirements and power it on
Install TrendMiner 2024.R2 on the new server
Restore the remote backup on the new server
Validate the setup
This way, the systems will not run simultaneously side-by-side, reducing the temporary increased overall system resources required. However, note that during this transition period, TrendMiner will be unavailable to end users.
Warning
Please note that if you opt to delete the existing VM, and something goes wrong with the remote backup (e.g. some data gets corrupted during upload), there is no fallback scenario possible and all work will be lost! Therefore, TrendMiner strongly discourages this option.
Question: Can we reuse the same IP and hostname for the new VM?
Answer: Yes, but it comes with a number of clear drawbacks that you should take into account:
You can only set up the new VM when the old one is powered off
You can't do a dry-run without downtime
You can only validate while the production system is down
Question: For the new virtual appliance deployment is it possible to start with system resources (CPUs, RAM, SSD) below the minimum requirements?
Answer: No, installations should always meet the minimal system requirements. To avoid incurring additional costs, it is possible to deploy and configure the new virtual machine but keep it powered off until you are ready to continue the migration.
The only exception to this rule is when the old CentOS/RHEL7 appliance is upgraded to 2024.R2.1. In this case the minimal system requirements for the 2024.R2 release do not apply since active usage of the CentOS/RHEL7 2024.R2 is not supported. This upgrade should only be executed with the goal to immediately migrate to the new AlmaLinux/RHEL9 server.
Question: with the local backup & restore option, what exactly will not be included? Are there best practices on how to handle this?
Answer: The local backup solution only takes a backup of the database, while the remote backup solution will include all components of the Trendminer installation. The remote backup solution can be used as a real disaster recovery solution also. Additional work/configuration for the local backup solution compared to the remote backup solution includes:
Re-indexing all tags (including the preparation work like extraction of a list of indexed tags and some other manual actions)
Manual reconfiguration of custom specific configuration like memory and timeout setting overrides with the help of TrendMiner support
Manual reconfiguration of the 'simultaneous index operations' setting
For MLHub customers: manually copying over the PMML models
Detailed migration instructions can be found here: Migration Process