> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/bmc-user-guide/configuration/managing-bmc.md).
# Managing BMC
Just like any other critical system, the BMC itself requires proper maintenance. Knowing how to back up its configuration, preserve settings through an update, or restore it to a known-good state is essential for stable and reliable remote management.
This chapter covers the key tasks for managing the BMC's configuration and lifecycle.
## **Backing up and restoring the BMC configuration**
Creating a backup of your BMC's configuration is a crucial first step before making any major changes or performing a firmware update. A backup file saves your critical settings, such as network configuration and user accounts.
To back up the configuration:
1. In the sidebar menu, navigate to **Operations** > **Backup And Restore**.
2. Under the **Backup** tab, use the toggles to select which settings you want to include in the backup (e.g., **SMTP**, **Virtual media**, **Network**).
3. Click **Download**. A `.tar` file containing your selected settings will be saved to your computer.
To restore a configuration:
1. Select the **Restore** tab.
2. Click **Add File** and choose a previously saved `.tar` backup file.
3. Click **Upload**. The settings from the file will be applied to the BMC.
## **Preserving settings across updates**
The **Preserve** feature allows you to select specific configurations that you want to protect during a firmware update or a factory reset. This is more granular than a full backup and ensures that critical settings like network IPs and user accounts remain intact.
1. Navigate to **Operations** > **Preserve**.
2. Check the boxes for each configuration group you want to save (e.g., **Authentication**, **Network**, **FRU**). You can use **Check All** to select everything.
3. Click **Save**.
{% hint style="success" %}
**Best Practice: Preserve Network and User Settings**
Before any firmware update, it's highly recommended to at least preserve your **Network** and **Authentication** settings. This will prevent you from being locked out of the BMC after the update and save you the trouble of re-creating all your user accounts.
{% endhint %}
## **Restoring the BMC to factory defaults**
In some cases, you may need to reset the BMC to its original factory state. This can be a useful troubleshooting step if the BMC becomes unstable or if you are decommissioning a server.
1. Navigate to **Operations** > **Factory Default**.
2. Choose your reset option:
* **Restore Default - Partial**: Resets some settings but attempts to keep critical data.
* **Restore Default - Full**: Wipes all configurations and returns the BMC to its out-of-the-box state. This is a complete reset.
3. Click **Restore**. The BMC will reboot, and the changes will take effect.
## **Rebooting the BMC**
Sometimes, a simple reboot of the BMC can resolve issues like a slow or unresponsive web interface. This action restarts the management controller only and **does not affect the host server's operating system**.
1. Navigate to **Operations** > **Reboot BMC**.
2. The page will show you the timestamp of the **Last BMC reboot**.
3. Click the **Reboot BMC** button.
The web interface will be inaccessible for several minutes while the BMC restarts. You will need to log in again once it comes back online.
---
# 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://doc.engenius.ai/bmc-user-guide/configuration/managing-bmc.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.
