Page Comparison

Note

• Keep the following things handy during disaster recovery, depending on what is affected in your cluster.

  • New certificates are applicable if existing settings (domain/subdomain) are changed after recovery.

  • Production license as per new BI nodes in case any BI server impacted

• You must use the disaster recovery capability in any of the following scenarios: 

  • If Kyvos Manager, BI Server, or Query Engine nodes are affected. 

  • If only the Kyvos Manager nodes are affected. 

  • If Kyvos Manager and all Kyvos nodes (BI Servers, Query Engines, Web Portal, and Postgres Server) are affected. 

• If only the BI Server or Query Engine nodes are affected, then add a node for that service, and the cluster can be restored. You will not need to use disaster recovery capability for this case.

• If you enable TLS for Kyvos Manager and Kyvos application, the TLS option is not applicable during the Disaster Recovery restoration. After successful restoration, the TLS-related certificates are restored, and you can continue with the TLS option. 

Important

• After performing Disaster Recovery, if you want to enable TLS, you need to restart Kyvos Manager. To do this, go to Terminal, and run the stop-km.sh and then start-km.sh).

• When Kyvos Manager HA is enabled and Managed zookeeper is used then after completing the Disaster Recovery activity, stop and start Kyvos Manager from terminal (not from Kyvos Manager UI) irrespective of whether TLS is enabled or not. Prior to the Kyvos 2024.1 release, Kyvos Manager restart is required only when TLS is enabled.

• After completing disaster recovery, ensure that the following snapshots are pushed from Kyvos Manager. To do this, navigate to Utilities > Update Snapshot Bundles.