> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/software-releases-and-backups/backups.md). # Backups The Backups section of the [Web Portal](/other-pages/other/web-portal.md) provides a list of the backups that have been made of the overall system configuration database, which contains each of the various sub-configurations that we will discuss in a moment. Making regular backups of your system is considered an excellent habit to keep and TelcoBridges has made it easy to do so. Creating a backup is as simple as clicking the 'Create' button and then refreshing the screen to see it appear in the list. (You can refresh the screen by clicking on the Backups menu item in the navigation bar.) Backups are stored locally but can be exported offline via HTTP for safe-keeping. Simply click on the ‘Download’ link to the immediate right of a backup file’s name. Restoring from an existing backup is as simple as selecting it from the list of previous backups and clicking on ‘Restore’. It is worth noting that the file name of the archive that is created when backing up the database contains the date and the time at which the backup was created. Before clicking ‘Restore’ though, it is advisable to first check the backup file for corruption. You can also restore from an offline copy by uploading it via HTTP. Just browse your local file system to find the archived file, and then click ‘Upload’ to send it to the device. --- # 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://tmediadocs.telcobridges.com/other-pages/software-releases-and-backups/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.