Hi Dojo,
When running DataMiner on Cassandra it is recommended to have the local DB located on a different drive than DataMiner - I can see the benefits when dealing with physical drives and the advantage of following the same approach with a VM: I guess this option would also facilitate the migration from a local DB architecture to a Cassandra cluster (*) - correct?
In terms of performance, however, is there any actual difference when the DMA is on a VM and "C:" & "D:" might be just logical drives coming from the same SSD storage?
Thanks,
A.
(* = P.S.: Is the new tool for "Cassandra to Cassandra cluster" released?
Would it allow also to move from local Windows-Based Cassandra to a Linux based Cassandra cluster?).
On the OS level we keep the logical drive as c: for Dataminer and d: for Cassandra regardless of being a VM or physical server. A valid reason to keep this practice is to sector and organise the data storage on the OS level.
The recommendation is it to keep Cassandra and DataMiner in sperate drives however if you have a DM system with the Cassandra database still on the same logical drive with DataMiner it is possible to move it straight to Cassandra on remote cluster. The operation here would in practice be similar the moving Cassandra from c: to d: however instead we move it to a remote server with Cassandra installed on it and its required configuration.
Thanks Joao, this clarifies – I understand it makes sense to separate data & app also on a VM, even if the performance could be more affected by the disk troughput associated with the virtualization and the related logical drives.