> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/architecture/byoc/disaster-recovery.md). # Disaster Recovery groundcover takes care of periodically backing up data in the system to ensure no loss can occur, both in monitoring data and also in dashboards and alerts created. ## Grafana Dashboards & Alerts groundcover ships with a builtin managed Grafana. As part of this, we make sure to back up every dashboard and alert created. This happens **on a daily basis.** groundcover also supports provisioning dashboards and alerts [with Terraform](/use-groundcover/embedded-grafana/embedded-grafana-dashboards/build-alerts-and-dashboards-with-grafana-terraform-provider.md), which could serve as another way for users to manage and backup what they set up. That being said, as mentioned above we ensure everything that was stored in our Grafana is backed up periodically. Choose whatever works best for you! ## Monitoring data ### Volume Snapshots groundcover operates to consistently maintain backups of your metrics, traces, logs and events. This works by creating daily snapshots of the volumes used by our databases. Snapshot lifecycle is managed entirely by groundcover, and will be used in case of disaster to recover lost data. ### Object Storage {% hint style="info" %} Object storage is not currently used for offloading metrics. {% endhint %} groundcover utilizes object storage for logs, traces and events, periodically offloading older data to object storage to make it safer and cheaper. This also allows to minimize the size of the volume snapshots, as most data is stored in object storage. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.groundcover.com/architecture/byoc/disaster-recovery.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.