> For the complete documentation index, see [llms.txt](https://docs.ostara.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ostara.dev/features/local-backups.md).
# Local Backups
### Overview
The local backup feature is designed to periodically capture and store snapshots of your Ostara configurations, and connections. These backups provide a safety net for system recovery and allow you to roll back to a previous known state if needed. The backups are saved locally on your machine and can be viewed/restored from the `Local Backups` window in the settings.
#### Automatic backups
The system will periodically create backups, these backups are rolling, so no more then 30 backups are saved. You can choose to restore them at any time. Additionally you are able to delete unwanted backups.
#### Manual Backups
From this screen you can also create manual backups. These backups can only be created and deleted manually, meaning the rolling feature will not clean up old backups.
#### Legend
 - Restore selected backup
 - Create new manual backup
#### Restoring a backup
When you restore a backup it will override the current configurations, you can see a preview of the backup to be restored.
---
# 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://docs.ostara.dev/features/local-backups.md?ask=&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.
