Recovering Jive after failure
This section describes which system properties, files, and directories need to be restored when recovering Jive after a failure.
You should configure Jive for High-Availability, as described in Configuring Jive for high-availability. Your HA configuration should enable you to automatically or manually start up after a failover. The following provides system properties, files, and directories that need to be restored in the case of a failure without any failover configuration:
- On the Core Application database nodes, restore the properties in the jiveProperty table that need to be persisted. For a list of these properties, see Restoring database with persistent properties.
- On the web application nodes, restore the files and directories in
/jiveHomethat need to be recovered. For a list of these files, see Restoring Web Application server file system.
In addition to the above steps for system recovery, consider implementing a disaster recovery plan to ensure continuity during major outages. A robust disaster recovery strategy will help recover your Jive instance more comprehensively.
-
Restoring Web Application server file system The Web Application server file system contains certain files and directories that should persist in a disaster recovery situation.
-
Restoring database with persistent properties In the jiveProperty table, there are several properties that may need to be changed when restoring data in a Disaster Recovery (DR) situation.
-
Rebuilding On-prem HA Search Service As of Jive 7.0, the HA search rebuild process has been simplified. The ingress replicators now send rebuild traffic to all of the search nodes. Therefore, ensure that all of the search service nodes are available before you start a rebuild.
-
Starting up after failover Depending on whether you're able to correctly set up dynamic redirects for the nodes, you start up the newly active system automatically or manually.