Dear DataMiner Community,

We are preparing to migrate the historical data from a production DataMiner cluster consisting of 5 main agents, each configured with a dedicated failover backup agent (1+1 redundancy model), to Skyline's STaaS. Our intention is to adhere to the standard migration procedure outlined in the official documentation: Migrating existing data to STaaS.

Current Database Architecture:

• DataMiner Installation: Hosted on the C: drive across all agents.
• Cassandra Deployment: Collocated in the DataMiner server, running on D: drive
• ElasticSearch Configuration: A single, standalone ElasticSearch node that serves all agents in the cluster for indexing and search functionalities.
• Data Scope: The migration encompasses all historical data types (e.g., trending, alarms, custom data including DOM, SRM, and Analytics), with no specific exclusions planned at this stage.

Procedure Alignment:

Given our architecture with fully segregated Cassandra nodes per agent (as opposed to a consolidated cluster-wide Cassandra deployment), we seek clarification on the following:

1. Direct Applicability: Does the standard procedure fully apply without modifications in this scenario, particularly regarding the coordination of data transfer across independent Cassandra nodes? For instance, will the migration script automatically handle ring-wide synchronization during the "Start Move to STaaS" and subsequent phases?
2. ElasticSearch: How does the shared single ElasticSearch node factor into the process??
3. Monitoring and Rollback: In a multi-agent setup, how can we best monitor progress granularly per storage type and agent?

Any insights, experiences from similar migrations, or references to additional resources would be greatly appreciated.

Thank you in advance for your expertise.