Hello dojo,
Imagine a customer running an older version of a Dataminer (feature) release 10.3.12.
If we wanted to upgrade this DMS to a recent main release e.g. 10.6.0 CU5.
What would be the recommended upgrade path for this system?
My proposal would be to do first upgrades on the feature release track up to 10.5.x and then a last upgrade to the latest main release 10.6:
10.3.12 => 10.4.12
10.4.12 => 10.5.12
=> Broker Gateway Migration
10.5.12 => 10.6.0 CU5
There might be some .NET versions to install on the servers as well while going through this.
Does this upgrade path seem ok? Any steps forgotten or steps that could be skipped?
Thanks a lot!
Hi Koen,
This upgrade path looks fine. Let me just add a few considerations and key points you should keep in mind:
Revised Upgrade Path:
10.3.12 → 10.4.12
10.4.12 → 10.5.12 [CU2] ← CU2 specifically, not bare 10.5.12
[Install ASP.NET Core Runtime 10 Hosting Bundle on ALL DMAs]
[Run BPA: "Verify NATS Migration Prerequisites" + "Check Deprecated DLL Usage"]
[Run prerequisite-only.dmupgrade package to validate readiness]
BrokerGateway Migration (NATSMigration.dmupgrade)
10.5.12 [CU2] → 10.6.0 [CU5]
Key Points
BrokerGateway Migration
- Mandatory before 10.6 -the upgrade is blocked if not done.
- The docs explicitly say: "Avoid migrating DataMiner Systems using a DataMiner version lower than 10.5.0 [CU11] / 10.5.12 [CU2]". So bare 10.5.12 is not sufficient -you need CU2.
- Use the automatic .dmupgrade package (manual migration is discouraged).
.NET / Prerequisites on the servers
Step Required
Before migration ASP.NET Core Runtime 10 Hosting Bundle on all DMAs (automatic migration fails without it)
For 10.6 ASP.NET 8.0 + 10.0 Hosting Bundles (covered by migration prereq check)
All steps Visual C++ Redistributable ≥ 14.44.35211.0 -otherwise an unexpected reboot can be triggered
Known Issues to Watch
- VerifyGRPCConnection prerequisite (KI, from 10.5.10+): The upgrade to 10.5.12 will run this check. If ConnectionSettings.txt, SLNet.exe.config, or DMS.xml redirects have been customized, the upgrade will be blocked. Check these before upgrading to 10.5.12.
- VerifyClusterPort prerequisite (KI, from 10.2.4+): For 2-node/Failover setups, restart the NATS + NAS services before each upgrade hop if this fails.
- DataMinerMessageBroker.API.dll < v3.0.0: If any protocol scripts reference this DLL with a version older than 3.0.0, update and remove the old DLL from ProtocolScripts before migration -on 10.5.12 this actively blocks the migration.
General Best Practices
- Take a VM snapshot (or DataMiner backup) before each hop.
- Upload-only first in System Center to run prerequisite checks before the maintenance window.
- TLS 1.2 + cipher suites (TLS_ECDHE_RSA_WITH_AES_128/256_GCM_SHA256/384) must be enabled - required for BrokerGateway's TLS communication.
If there's a DMZ or Failover setup, post-migration actions are needed (reconnect DMZ to dataminer.services, etc.).