11 Jul 2023 01:25 PM - edited 11 Jul 2023 01:27 PM
Hi,
I have a problem when trying to restore a cluster from a backup. I have machines that are identical in terms of software and hardware. I'm following the step by step instructions: https://www.dynatrace.com/support/help/shortlink/managed-cluster-restore#restore-from-backup
In step 3 I get an error when starting Casandra.
Solved! Go to Solution.
11 Jul 2023 01:40 PM
Hi Radek,
How many nodes you have? are they on the same subnet. if no, what is the latency between subnets.
BR,
Islam
11 Jul 2023 01:47 PM
I can confirm this is a network issue. The gossip - is the protocol used in Cassandra to negotiate the connection details between nodes. Make sure you've ensured proper network connection to the nodes you configured in step 2 - --cluster-nodes
11 Jul 2023 02:08 PM
Hi Radek,
Yes, I have verified all the requirements. For now, this environment has only one node because it's a test environment and we are testing the backup procedure before running it on the production environment.
11 Jul 2023 03:33 PM
Hm.. so if that's only a single node... there should be no networking issue as there's no one to gossip with 😉
11 Jul 2023 05:52 PM
The development environment at the client looks like this:
1. The old DT server from which the backup was created
2. The network resource on which this backup is created (sub-mounted to two hosts).
3. The new DT server to which we make a restore from the backup.
Server 1 when starting the new one after the restore is done is disabled. Everything seems to be correct hence I'm surprised by this error. I will have another try tomorrow - let you know! 😊
18 Jul 2023 12:58 PM
Ok, the matter turned out to be simpler than I thought 😁
What was missing was specifying the --seed-ip variable when running the restore command.
btw. Casandra error message is highly specific in this case.
Radek