Dear community,

I've configured my backup settings in System Center to run a weekly full backup including local database. My DMS exists out of a single failover pair which is running DataMiner SW version 10.2.0 CU3.

Upon backup execution we notice a failure whenever the procedure tries to take a backup of the local database.

failure details:

[08/23/2022 15:49:51][INFO][Program.cs:32] Beginning backup...
[08/23/2022 15:49:52][INFO][CassandraConnection.cs:47] Connecting with Cassandra on Ip: 10.13.138.151,10.13.138.150 with user: root
[08/23/2022 15:49:57][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:02][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:07][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:12][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:17][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:22][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:27][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:33][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:38][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:43][INFO][CassandraConnection.cs:66] Retrying to connect with Cassandra.
[08/23/2022 15:50:43][INFO][CassandraConnection.cs:72] Could not connect to Cassandra: No host name could be resolved, attempted: 10.13.138.151,10.13.138.150
[08/23/2022 15:50:43][ERROR][Program.cs:43] Cassandra.NoHostAvailableException: No host name could be resolved, attempted: 10.13.138.151,10.13.138.150
at Cassandra.Cluster.<AddHosts>d__35.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Cassandra.Tasks.TaskHelper.WaitToComplete(Task task, Int32 timeout)
at Cassandra.Cluster..ctor(IEnumerable`1 contactPoints, Configuration configuration)
at Cassandra.Cluster.BuildFrom(IInitializer initializer, ICollection`1 hostNames)
at SLDataGateway.Backup.Cassandra.Utils.CassandraConnection.CreateCassandraConnection()
at SLDataGateway.Backup.Cassandra.Utils.CassandraConnection..ctor(ConfigurationManager configurationManager, ILogger logger)
at SLDataGateway.Backup.Cassandra.Operations.Backup..ctor(ILogger logger, ProgramOptions options, Nodetool nodetool, IPackageFactory packageFactory, CassandraConfig cassandraConfig, ConfigurationManager configurationManager)
at SLDataGateway.Backup.Cassandra.Operations.OperationFactory.CreateInstance(ProgramOptions options, ILogger logger)
at SLDataGateway.Backup.Cassandra.Program.Main(String[] args)

I'm suspecting that the system was forced to leverage the new cassandra architecture even though everything is running according to the legacy hardware architecture where DataMiner as well as the Cassandra and Elastic node are hosted on the same server.

If this would be true, it means that we can no longer issue regular DataMiner backups including the local database even though everything is running locally and my "Cassandra cluster" exists only out of 2 nodes (as its a failover pair.)

Is this expected behavior? This system is running on dedicated hardware (not virtualized) so full system backups are definitely still a project requirement.