Applies to: 
Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
...
| Panel |
|---|
| panelIconId | atlassian-note |
|---|
| panelIcon | :note: |
|---|
| bgColor | #DEEBFF |
|---|
|
Note Keep the following things handy during disaster recovery, depending on what is affected in your cluster. 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.
|
Disaster recovery through the guided flow on Kyvos Manager
...
Bundle Name | DFS folder Location inside Engine Work directory specified for cluster | Purpose / Contents |
biserver_conf_snapshot.tar.gz | setup/conf/ | BI configurations (bin, conf) |
biserver_lib_snapshot.tar.gz | setup/binaries/ | BI Binaries/lib (jars) |
biserver_connections_snapshot.tar.gz | setup/conf/ | BI Connections (Hadoop, DataLake, DBRepo) |
queryengine_conf_snapshot.tar.gz | setup/conf/ | QE Conf (bin, conf) |
kyvos_webapp_conf_snapshot.tar.gz | setup/conf/ | Kyvos WebApp Conf |
kyvos_webapp_binaries_snapshot.tar.gz | setup/binaries/ | Kyvos WebApp binaries (tomcat & Kyvos WebApp) |
hadoop_connection_conf_snapshot.tar.gz | setup/conf/ | Hadoop conf |
hadoop_connection_lib_snapshot.tar.gz | setup/binaries/ | Hadoop lib |
kyvos_commons_snapshot.tar.gz | setup/conf/ | Kyvos commons (Includes Acknowledgement & SanitySuite) |
jre_snapshot.tar.gz | setup/binaries/ | Jre folder |
postgres_snapshot.tar.gz | setup/binaries/ | Postgres bundle |
km_agent_conf_snapshot.tar.gz | setup/conf/ | KM agent conf |
km_agent_lib_snapshot.tar.gz | setup/binaries/ | KM agent lib |
km_snapshot.tar.gz | setup/binaries/ | KyvosManager Kyvos Manager snapshot (kyvosmanager Kyvos manager application) |
km_data_snapshot.tar.gz | setup/conf/ | KyvosManager Kyvos Manager Data |
km_db_snapshot.tar.gz | setup/binaries/ | KyvosManager RepoKyvos Manager Repo |
km_conf_snapshot.tar.gz | setup/conf/ | Kyvos Manager configuration |
| Panel |
|---|
| panelIconId | atlassian-note |
|---|
| panelIcon | :note: |
|---|
| bgColor | #DEEBFF |
|---|
|
Note Any manual changes that need to be included in snapshots, must be applied on the Kyvos Manager node (having WebPortal Role and Postgres Role when bundled repository is used) Executing start scripts of BI Server and Query Engine has behavior that those download snapshot bundles from DFS to sync their state. If any manual changes were made on the node and not part of the snapshot bundle yet, then executing the start script of BI Server and Query Engine will sync bundles in their startup, and any changes made locally in the same-named files that already exist in the bundle will get lost. For Web Portal, there are two scripts, start-dc.sh and start-sc_sync.sh in the jakarta/bin folder. When Web Portal service started from Kyvos Manager UI normally, the start-dc.sh will be executed. However, for Services HA or disaster recovery-based Web Portal start, Kyvos Manager will execute the start-dc_sync.sh script. In different operations that are being performed from Kyvos Manager, those bundles will be uploaded, which contain files that may change during that particular operation.
|
...
