> 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/maintenance-and-troubleshooting/maintenance-guide.md).

# Maintenance Guide

Maintenance procedures for ProSBC: check disk space and processor usage, back up the configuration, and replace a standalone, primary or secondary unit.

### Introduction

This article provides different procedures for maintaining your ProSBC.

### ProSBC Verification

* [Check Disk Space](https://prosbcdocs.telcobridges.com/maintenance-and-troubleshooting/maintenance-guide/check-disk-space.md)
* [Check Processor Usage](https://prosbcdocs.telcobridges.com/maintenance-and-troubleshooting/maintenance-guide/prosbc-processor-usage.md)

<br>

### ProSBC Replacement

#### Backup your system configuration

If this is a 1+1 system, before proceeding with the procedure, make a backup of your configuration. Please follow this link: [Backup procedure](https://prosbcdocs.telcobridges.com/maintenance-and-troubleshooting/maintenance-guide/troubleshooting-toolpack.md)\
Note: The database backup should be stored in a safe place

#### Setup a new ProSBC

Install a ProSBC using one of the following methods: ProSBC Installation\
If the same product key is used, it needs to be reset - please contact [TelcoBridges TB Support](mailto:support@telcobridges.com)<br>

### Replacement of a standalone ProSBC

Go through the initial configuration and select "This unit is deployed as a stand-alone unit"\
If the configuration database is available, restore it on the system: [Restoring Database Procedure for v2.8 and up](https://prosbcdocs.telcobridges.com/maintenance-and-troubleshooting/maintenance-guide/restoring-a-database.md)\
Otherwise you will need to reconfigure the system: ProSBC Configuration<br>

### Replacement of a Primary ProSBC

Go through the initial configuration and select "As part of a redundant system"<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/d/d8/FreeSBC_redundant.png/700px-FreeSBC_redundant.png" alt="Deployment prompt asking how the unit is to be deployed, with As part of a redundant system selected instead of stand-alone."><figcaption></figcaption></figure>

\
Then select "The primary unit"

<figure><img src="https://docs.telcobridges.com/w/images/thumb/d/d0/FreeSBC_the_primary_unit.png/700px-FreeSBC_the_primary_unit.png" alt="Primary or Secondary 1+1 prompt with The primary unit selected, illustrated by the Primary Server Unit highlighted in the left pair."><figcaption></figcaption></figure>

\
and "Get configuration from an existing secondary unit"

\
\ <br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/7/7f/FreeSBC_take_from_secondary.png/700px-FreeSBC_take_from_secondary.png" alt="Prompt asking whether to take configuration and packages from an existing secondary unit, with Yes circled and configuration flowing upward from secondary to primary."><figcaption></figcaption></figure>

### Replacement of a Secondary ProSBC

Go through the initial configuration and select "This unit is deployed as part of a redundant system" and select "The secondary unit". It will automatically get the configuration from the primary unit.<br>

<figure><img src="https://docs.telcobridges.com/w/images/thumb/f/f1/FreeSBC_the_secondary_unit.png/700px-FreeSBC_the_secondary_unit.png" alt="Same 1+1 role prompt with The secondary unit circled, illustrated by the Secondary Server Unit highlighted in the right pair."><figcaption></figcaption></figure>


---

# 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/maintenance-and-troubleshooting/maintenance-guide.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.
