> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/system/database-backup/restoring-a-database-backup.md).

# Restoring a Database

> **Applies to:** Tmedia 3.0, 3.2, 3.3; SBC 3.1, 3.3

The system configuration settings can be restored from a local or remote copy of a database.

```
'''Important Note''': A database backup from a newer major version should NEVER be imported to an older major version.
If you have done this, please refer to:
```

* [Procedure to recover a major upgrade after recovering database from newer version to an older version](/tmedia-documentation/operations-and-support/troubleshooting/field-notices/fn19497-major-release-upgrade-fail-if-the-database-have-data-upgraded-from-a-newer-major-release.md)

1- Click **Backups** in the navigation panel

![Backups 0 A](https://docs.telcobridges.com/w/images/7/70/Backups_0_A.png)

2- Initially the **Recover** feature is disabled. The database must first be validated before it can be restored.

* Click **Validate**

![DB Recovery Rel2.9 Validate](https://docs.telcobridges.com/w/images/7/75/DB_Recovery_Rel2.9_Validate.JPG)

3- After a few minutes, the web portal will return to an online status and if the backup validates successfully, the **Recover** link becomes active.

* Click the **Recover** link to overwrite the current database and restore the backup file

![DB Recovery Rel2.9](https://docs.telcobridges.com/w/images/a/a1/DB_Recovery_Rel2.9.JPG)

**Note**: You must activate the configuration to apply the changes.

The database files backups are stored here:

```
/lib/tb/toolpack/pkg/database_backups
```


---

# 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://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/system/database-backup/restoring-a-database-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.