4.5.8 Importing Analytics Server in a High Availability Setup

If you require importing Analytics Server in a high availability setup, perform the following steps on the nodes of the Analytics Server cluster:

You must first import the passive node in the cluster, then import the active node.

Enable the maintenance mode on the cluster.
```
crm configure property maintenance-mode=true
```
Maintenance mode helps you to avoid any disturbance to the running cluster resources when you import Analytics Server. You can run this command from any cluster node.
Verify if the maintenance mode is active.
```
crm status
```
The cluster resources should appear in the unmanaged state.
Import the passive cluster node:
1. Stop the cluster stack.
```
rcopenais stop
```
  Stopping the cluster stack ensures that the cluster resources remain accessible and avoids fencing of nodes.
2. Import Analytics Server on the passive node. For information about importing Analytics server, refer Section 4.5.7, Importing Analytics Server.
3. After importing the passive node, start the cluster stack.
```
rcopenais start
```
Import the active cluster node:
1. Stop the cluster stack.
```
rcopenais stop
```
  Stopping the cluster stack ensures that the cluster resources remain accessible and avoids fencing of nodes.
2. Import Analytics Server on the active node. For information about importing Analytics server, refer Section 4.5.7, Importing Analytics Server.
3. After importing the active node, start the cluster stack.
```
rcopenais start
```
4. Run the csync2 -x -v command to synchronize any changes in the configuration files.
Disable the maintenance mode on the cluster.
```
crm configure property maintenance-mode=false
```
You can run this command from any cluster node.
Run the insserv -r sentinel command on both the nodes to remove the autostart scripts so that the cluster can manage the product.
Verify whether the maintenance mode is inactive.
```
crm status
```
The cluster resources should appear in the Started state.