The Indexing Engine Installation asks for a backup path.
According to the help the same path is used in the whole cluser.
What is usually used for this? A local path or a network path?
If it's a single Elastic node cluster you are fine using a local path.
But when having a multi node Elastic cluster you should have a shared network path accessable by all nodes.
Hello Jeroen,
We recently have received a task regarding this issue. First of all, when setting a backup path in system center with a remote Elastic, this will most likely not do anything. (since we try to edit local yaml files which wont exist).
Secondly, after investigation it turned out that the “not begin able to save backup configurations” is most likely not linked to not being able to set a backup path, there’s most likely a diffrent root cause here.
Perhaps an investigation to this specific issue could help you further here.
Kind regards,
@Bert, In my case I’m running a DataMiner cluster which is connected to an external Elasticsearch cluster (3 nodes) running on Linux CentOS 8. I see that within module System Center –> Backup, the UI is indicating that I still need to enter a Indexing Engine Location – backup path. Without specifying something here, the GUI won’t allow me to save any backup configuration. When I add a path in here, the system warns me that it will restart the indexing services…. Is this really the case when I’m running my nodes on external Linux servers?