> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/connected-insights/configure/local-installation-guide/admin-overview/troub-data-backup.md).

# Data Backup (Connected Insights - Local)

Connected Insights - Local software performs a daily backup of database and variant data to the mounted external storage configured at the time of installation. This backup data is saved to `/mnt/<ici_mount_path>/ici_<ServerFullyQualifiedDomainName>` or `/mnt/<ici_mount_path>/ici_<IPAddressInCaseOfStaticConfiguration>`. The backup data can contain up to 5 days of information, including database and variant data exports.

The data backup process saves backup data when there is a difference between the previous successful backup and the current state of the application. If the application state has changed from the previous backup and new cases were processed, but no new backup directory was created for the following day, run the following command to generate a manual backup manually:

> kubectl create job --from cronjob/elasticsearch-dbbackup esdb-test -n ici && kubectl create job --from cronjob/postgres-dbbackup pgdb-test -n ici

If there is a system failure, contact Illumina Technical Support to recover the system using the backup data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/connected-insights/configure/local-installation-guide/admin-overview/troub-data-backup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.