You can restore persisted data from the database as part
of a disaster recovery procedure, and load the data back onto the Decision Server
Insights system
by running the dataLoadManager script commands.
Before you begin
By default, an Insight Server caches
system data in memory, and does not write data to persistent storage.
If you want to persist data, you must configure a server to write
the data to a backend database. For more information, see Configuring system data persistence.
About this task
To recover data from a database after a grid failure, take the following actions and use the
autoload command or the load and finalize
commands.
Procedure
- If all or some of the servers are still running, stop them one by one.
Tip: Catalog servers do not need to be restarted, if they are operating normally. You
can run the following command to tell if a catalog server is operational
<InstallDir>/runtime/wlp/bin/server status <catalog_name>.
- To stop inbound servers, use server stop <inbound_name>.
- To stop outbound servers, use server stop <outbound_name>.
- To stop runtime servers, use serverManager shutdown [options].
- To stop catalog servers, use server stop
<catalog_name>.
- If you stopped the catalog servers, then restart them by running server start
<catalog_name>.
- Restart all of the runtime servers by running server start
<container_name>. Make sure that all of the runtime servers are started by checking that the grid state is in
PRELOAD. The runtime server logs include messages with the string The grid
state is "PRELOAD".
- Load the data from the database by running the
<InstallDir>/runtime/ia/dataLoadManager commands. Pass arguments to connect to the server if the connection properties where you run the command
are not in
<InstallDir>/runtime/ia/etc/connection.properties.
- In a separate command window, run the <InstallDir>/runtime/ia/dataLoadManager
progress command to see the status of the command. Run the progress command again if the
command fails to complete. If the data load command is 100% successful the runtime server logs include messages with the
string The grid state is "ONLINE".
- Restart the outbound servers by running server start <outbound_name>.
- Restart the inbound servers by running server start <inbound_name>.