Hi Dojo,
I’m looking for the best way to move my current setup, which is 1 server containing 3 disks (1x DataMiner, 1x Cassandra, 1x Elastic), to a cloud solution of 3 servers/VMs.
I found some articles where you can move the local Cassandra/Elastic DB to a remote server, but I would like to have a procedure where I don’t need to install everything on a cloud VM with 3 disks and move the databases afterwards.
Hi Jens,
Here I personally would opt for 3 cloud server instances:
- 1x Windows Server OS –> to host your DataMiner node
- 1x Linux OS –> to host your Cassandra node
- 1x Linux OS –> to host your Elasticsearch node
A high level procedure to migrate this setup would be:
- Prepare all your cloud based instances so that they are operational with the correct OS installed.
- Install the correct version of the 3 applications (DataMiner, Cassandra and Elasticsearch) on their new dedicated cloud instance.
- Take a Cassandra snapshot (see more details here ) and restore the snapshot on the new cloud based instance.
- Take a Elasticsearch snapshot (see more details here ) and restore the snapshot on the new cloud based instance.
- Reconfigure your on – prem. DataMiner node to point towards the new Cassandra and Elasticsearch instance running in the cloud and validate proper functionality of the system afterwards.
- Take a configuration backup of your local DataMiner node and restore this configuration backup on the new cloud based DataMiner node, after this you should have successfully completed your cloud migration.
Alternatively you can also opt to host your Cassandra and Elasticsearch instance as a managed service (SAAS) provided by your cloud provider.
For example:
- AWS Opensearch (Elasticsearch)
- AWS Keyspaces (Cassandra)
- AZURE Elastic Cloud (Elasticsearch)
- AZURE Cosmos DB (Cassandra)
I personally don’t yet have experience with deploying a DataMiner system against these SAAS services but I do believe that this direction is the route for the future.
IMPORTANT: the supported versions of Cassandra and Elasticsearch for DataMiner Software are:
- Cassandra: 3.7 & 3.11
- Elasticsearch: 6.8
This is regardless of whether your deploy against a SAAS based instance VS a standard based instance.
Indeed Jens, I don’t foresee any issue with that.
Hi Jeroen, Thank you for the detailed explanation. Much appreciated!
Something I forgot to mention is that I want to use the on-prem server for development purposes. I guess that I can easily reconfigure the DB connections back to the local disks afterwards?