Mindbreeze InSpire G7

Synchronized Operation of a Mindbreeze InSpire Appliance

Mindbreeze InSpire G7

Preparing the infrastructure and configurationPermanent link for this heading

Synchronized operation requires some configuration and network preparations so that operation can be synchronized to a replica appliance from an existing InSpire appliance. The TCP port 2222 of the replica appliance should be accessible from the master appliance (outgoing).

Important note: Synchronization enables synchronous operation of the search functionality. Index building is handled exclusively on the master appliance and, for efficiency reasons, this information is not transferred. Therefore, a synchronized operation is no substitute for a backup.

Updating the licensePermanent link for this heading

Make sure that the master license also contains the node ID of the synchronized appliance. The node ID of the appliance can be found under the item “Configuration.” The license should be updated on the master appliance.

Preparing the connection from the indexing appliance to the replica appliancePermanent link for this heading

Configuring the master appliance (menu item system)Permanent link for this heading

Log in to the main appliance as admin, go to “System” and edit the hosts file in /inspire/etc. In the case below, the address a.b.c.d stands for the valid IP address of the appliance. Contact your network administrator to obtain the correct address for the appliance. The consumer ID in the example below is inspire-4321472b-6095-4863-b73c-5af5131e9d66

Go to /etc/sshkeys/mes and download the id_rsa.pub file.

Here you should see analog content:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAA...ji0HDZOQjsbvw== mes@inspire

Keep this entry handy for later.

Configuring the replica appliance (menu item system)Permanent link for this heading

First, go to the standby appliance that you want to add. Log on to the system, go to menu item “System,” and switch to “File Upload.” Then navigate to /etc/sshkeys/mes and edit the file authorized_keys.

Configuring indices and the client service (master appliance)Permanent link for this heading

Index/Query Service settings (per index)Permanent link for this heading

Make the following changes to transfer the query services:

Activate the standby node ID under “Query Services,” enable the Sync option, and set an incoming path. We recommend that you place the index directory name under a /data directory, e.g. for the index “web-test,” use /data/incoming/web-test.

You also need to set the property “External URL” of the respective index to “https://localhost:<Query Port>” as shown below.

Client service settingsPermanent link for this heading

Go to “Additional Client Services Nodes” and enable the standby node.

Make sure that all query services are aggregated:

Manually synchronizing the configuration of indicesPermanent link for this heading

The configuration and the indices can be synchronized manually via SSH. To do this, log on to the master appliance via port 22.

Synchronizing the configurationPermanent link for this heading

To synchronize the configuration, execute the following command:

docker exec inspire su mes -c " PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/mindbreeze/bin /opt/mindbreeze/scripts/export-and-sync-masterconfig-to-consumer.sh <target> "

In our case:

docker exec inspire su mes -c " PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/mindbreeze/bin  /opt/mindbreeze/scripts/export-and-sync-masterconfig-to-consumer.sh inspire-4321472b-6095-4863-b73c-5af5131e9d66 "

Synchronizing individual indicesPermanent link for this heading

You can also trigger synchronization manually on the console of the service:

docker exec inspire su mes -c "/opt/mindbreeze/bin/mescontrol http://localhost:23100 syncdelta"  

Automatic synchronization via Cron JobsPermanent link for this heading

Switch to the file upload of the master appliance and edit the file /cron/custom

#Mindbreeze Custom crontab

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/mindbreeze/bin

#Example: Sync index with port 23100. Every hour

#0 * * * * mes /opt/mindbreeze/bin/mescontrol http://localhost:23100 syncdelta

#Example: Sync config to consumer. Daily. IMPORTANT: replace <target> with hostname of consumer

#30 23 * * * mes /opt/mindbreeze/scripts/export-and-sync-masterconfig-to-consumer.sh <target>

In our case:

#Mindbreeze Custom crontab

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/mindbreeze/bin

#Example: Sync index with port 23100. Every hour

#0 * * * * mes /opt/mindbreeze/bin/mescontrol http://localhost:23100 syncdelta

#Example: Sync config to consumer. Daily. IMPORTANT: replace <target> with hostname of consumer

#30 23 * * * mes /opt/mindbreeze/scripts/export-and-sync-masterconfig-to-consumer.sh inspire-4321472b-6095-4863-b73c-5af5131e9d66


AttachmentPermanent link for this heading

Manual identification of the node IDPermanent link for this heading

You can use SSH to find out the node ID of the appliance. To do this, you will need the root password. Once you are logged in to the appliance locally on port 22 via SSH, you can run the following command:

root@inspire ~]# docker exec –it inspire /opt/mindbreeze/bin/mesnodeidtool

The output returns the node ID.