> 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/configuration/web-portal-3-3/system/status/detailed-status-views/verifydatabasebackup.md).

# Database Status

#### ***Applies to version(s) v2.9, v2.10, v3.0***

**To view the status of the databases:**

1- Click **Status** in the navigation panel.

![Status 0](https://docs.telcobridges.com/w/images/5/53/Status_0.png)

2- Click the **System** tab.

![Status Database 0](https://docs.telcobridges.com/w/images/9/97/Status_Database_0.png)

A listing of the databases is displayed in the **Database toolpack** list.

* Verify that no errors are displayed.

![StatusDatabase 1](https://docs.telcobridges.com/w/images/e/eb/StatusDatabase_1.png)

The fields are defined as follows:

**Standalone System**

* Role: Only one row is shown for a standalone system.
* Up: Must be **Yes**
* Mgmt state: Must be **Ready**
* Replic state: **Master**
* Target replic state: **Master**

**1+1 System**

* Role: Two rows are shown for a 1+1 system.
* Up: Must be **Yes**
* Mgmt state: Must be **Ready**
* Replic state: One is **Master** and the other is **Slave**
* Target replic state: One is **Master** and the other is **Slave**

<details>

<summary>Northbound Interface</summary>

**Path**

```
/status
```

</details>


---

# 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/configuration/web-portal-3-3/system/status/detailed-status-views/verifydatabasebackup.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.