Dealing with node failure about actordb HOT 1 OPEN

Once you have the replacement ready (new hardware/vm), create a backup from an existing node. Put the backup lmdb file in the data directory. It is easiest to start the new node with the same vm.args/app.config as the old node. If you do so it will start working straight away. This works if you can keep the same node name and IP/domain.

If you don't have the same IP/domain. Start actordb on the new node (with the lmdb file and correct vm.args/app.config), then run SQL UPDATE statement through actordb_console (connected to one of the old unchanged nodes) to change the name to the new node.

from actordb.