Hi All,
We are currently on 10.1 and need to migrate the local database to a “per DMA” cluster/server pair.
On 10.1 does anyone know the best way to do the migration on a per DMA basis rather than the whole DMS?
As this question has now been open for a long time and there has been no further reaction from you, I will now close it. If you still want more information about this, could you post a new question?
Hi Ryan,
You will need to upgrade first the system to a higher version of DM, before you will be able to run the migration. I would recommend going to the latest main release version before performing such action, to ensure you have all fixes available (e.g. RN37684). After that, you can follow the procedure from our docs (below link), where it is also explained you can do one agent at a time.
More info can be found in our docs: Migrating the general database to a DMS Cassandra cluster | DataMiner Docs
Hi Michiel,
I was under the impression we could move to a separate database pair for each DMA in 10.1? Is this not the case?
We are unable to upgrade due to server resource issues.
These are the available DB architecture options you have:
https://docs.dataminer.services/user-guide/Advanced_Functionality/Databases/Databases_about.html
If you want to keep your data on prem, then the advised method is currently ‘Dedicated clustered storage’ (https://docs.dataminer.services/user-guide/Advanced_Functionality/Databases/Supported_system_data_storage_architectures/Dedicated_clustered_storage.html). This is one Cassandra cluster for the whole DMS (all agents within your DM cluster) and one OpenSearch cluster for the whole DMS.
This way you only have one Cassandra and one OpenSearch cluster you have to scale for the whole DMS instead of all individually.
Hi Michiel
We are wanting to use the storage per dma without indexing for now, and then we will be going to a DMS clustered with elastic search DB. But due to some issues we have to break the databases out to then upgrade.
Is there any documentation on the Storage per DMA without indexing migration and do you know what version of Cassandra it needs to be for 10.1?
What do you mean by breaking the databases out? Scaling them or moving them to a separate machine? If you want to keep running Cassandra on the machine where DM is located (Windows), then the highest version of Cassandra you can go to is 3.11.x. Cassandra stopped supporting Windows from 4.x. If you have issues with load on your cluster, maybe have a look what is putting load on the system. In most cases, you can reduce the load significantly by reducing the number of alarms or information events generated and making sure you only enable real-time trending on parameters that are really needed.
I see that this question has been inactive for some time. Do you still need help with this? If you have found the information you needed in the answer and comments below, could you select the answer to indicate that this question is resolved?