Replicated elements | DataMiner Docs clearly states, "The source and replication DMA must use the same DataMiner version.” This is repeated in: Is replication supported across different major DataMiner versions? - DataMiner Dojo.
A strict interpretation of this rule will pose severe operational challenges in the scenario where a central DMS replicates elements from tens of different DataMiner Probes. Coordinating the upgrades of all those DataMiner Systems (Central + Probes) simultaneously will be very difficult.
I’d like to understand how strict this requirement of running the same DataMiner version is and the technical reasons behind it. This answer from Bert sheds some light on the method used to receive element updates Max number of replication elements? - DataMiner Dojo.
I would expect few, if any, changes between DataMiner iterations. At what point does having different DataMiner versions break the element replication?
Please elaborate.
Thank you very much.
Hi Miguel,
The requirement that "The source and replication DMA must use the same DataMiner version" is rooted in the technical details of how the replication mechanism works. In the background, the replication process primarily relies on element subscriptions communicated via SLNet calls between the source and replication agents.
Given that changes in DataMiner releases can potentially alter how these SLNet calls are structured or processed, using different versions could lead to inconsistencies or unexpected behaviors. Therefore, it is always advised and preferred to run the same DataMiner version across all systems involved to avoid such issues.
While we are aware that some users have been successfully using element replication across different DataMiner versions, we cannot guarantee that all functionalities will work as expected when systems are running on different releases.
I hope this clarifies the reasoning behind the version alignment requirement.