# Backups (Helm) {% hint style="info" %} This documentation only applies to **advanced Orchestrated container deployments** using **Kubernetes** and **Helm** {% endhint %} Ensuring the safety and security of your CARTO Self-Hosted version is crucial. Regular backups of your external database and configuration files are essential to protect your data and settings from unexpected failures, data corruption, or system crashes. The CARTO platform only requires the **configuration files of an existing installation and the contents of the metadata database to be completely restored**, so that's why it's highly recommended to use an [external database](/carto-self-hosted/guides/guides-helm/migrating-carto-self-hosted-installation-to-an-external-database.md) for self-hosted deployments. By including these elements in your backup strategy, you not only safeguard your data but also ensure a seamless recovery process. This ensures that in case of any disruptions, your CARTO Self-Hosted installation can be fully restored to its operational state, minimizing downtime and potential data loss. ### Restore an existing backup The process of restoring a CARTO Self-Hosted backup involves reinstalling CARTO with the same settings as before and ensuring that the external database, where your data is stored, is still operational and accessible to the new installation. This way, you can recreate your CARTO environment in a state identical to when the backup was created. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.carto.com/carto-self-hosted/maintenance/maintenance-helm/backups.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.