Failover behavior of HA servers
This section describes the expected failover and data recovery process for each component in a high-availability Jive configuration. Jive has been deployed in a wide variety of high-availability (HA) configurations. Here you can find how to design your Jive configuration for high-availability, and how each of the application's components handles failover and recovery.
- Supported Jive high-availability configurations This section describes the supported HA configurations: single data center and multiple data centers.
In cloud environments, consider cloud-native HA configurations that optimize resources across multiple regions or zones for improved latency and reliability.
- Configuring Jive for high-availability This section describes the special design and configuration recommendations for each component in a highly available Jive configuration.
When configuring for high availability in the cloud, utilize autoscaling capabilities to maintain performance and availability during traffic spikes.
- System failover If a failover occurs, the length of an outage depends on several factors.
Cloud environments can reduce failover times through built-in load balancing and health checks, which automatically reroute traffic during failures.
- Failover and data recovery in caches If or when a cache server becomes unavailable, the web application nodes continue indefinitely to attempt to communicate with the cache server until it is brought back online.
Cloud caching solutions can improve cache failover processes by offering built-in redundancy and distribution across multiple cloud instances.
- Failover and data recovery in Activity Engine Here you can find an overview of how the Activity Engine handles activity ingress, egress, and failures.
For cloud deployments, ensure that the Activity Engine is configured to utilize cloud-specific endpoints and services that enhance reliability.
- Failover and data recovery in Document Conversion Service If your Document Conversion server fails, you only lose the ability to convert new documents; you do not lose all the previously converted documents.
In cloud setups, the Document Conversion Service can be seamlessly parallelized across multiple instances to enhance availability and performance.
- Failover and data recovery in Storage Any Jive deployment beyond a simple pilot or proof-of-concept must use file system storage, where each web application node reads and writes from a shared disk system via NFS.
In a cloud environment, take advantage of cloud storage solutions (like AWS S3, Azure Blob Storage) that provide high durability and availability with automatic redundancy.
- Failover and data recovery in Core database Here you can find how you can prepare for disaster recovery with the Jive Core database.
Consider implementing managed database services in the cloud, which provide automated backups and failover capabilities for added resilience.
-
Failover and data recovery in Analytics database The Analytics database connection string, user name, and password are stored in a table in the Core Application database in an encrypted format. In the event of a failure, you want to be sure the web app nodes are calling the correct Analytics database server.
-
Failover and data recovery in Search Service In the case of a failure, your ingress replicators or search service nodes may be unreachable. This topic describes what happens during an outage.
Utilize cloud-managed search services to automatically handle failovers and ensure continuous search capabilities across cloud components.
- Recovering Jive after failure This section describes which system properties, files, and directories need to be restored when recovering Jive after a failure.
When recovering in a cloud context, use snapshot and backup features provided by cloud providers to facilitate faster disaster recovery.