> For the complete documentation index, see [llms.txt](https://docs.vergeos-demo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vergeos-demo.com/automate-protect-and-extend/backup-and-dr/repair-server.md).

# Repair Server (ioGuardian)

A repair server provides a potential repair mechanism after a system experiences a problem that extends beyond its redundancy tolerance (e.g. simultaneous, multiple drive failures spanning multiple nodes). Typically, a repair server is a sync destination that contains a fairly recent replication of the given system. A repair server will automatically attempt to pull back any needed blocks from the remote system, potentially avoiding the need to roll back using a snapshot. It is generally recommended that you have a repair server in place whenever possible.

{% hint style="success" %}
**There is a higher chance of repair success when there is a good network connection, with relatively low latency, between the system and its repair server.**
{% endhint %}

A repair server is created using the existing outgoing sync configuration: vSAN Host (address of the remote destination), vSAN Port, system-generated authorized username/password, and encryption setting enabled or disabled based on the associated sync configuration.

## Create a Repair Server from an Outgoing Sync (common method)

{% hint style="info" %}
**Repair servers may be auto-generated when** [**Adding Sites to the Dashboard**](/run-the-platform/system-administration/site-dashboard-add-sites.md)**.**
{% endhint %}

Typically, a repair server is created from an outgoing sync because the sync destination would contain a recent copy of the data. This is the recommended method in most cases.

1. From the outgoing sync dashboard, click **Create Repair Server** on the left menu.
2. Enter a **Name** for the repair server. Use a name that will be helpful for future administration, for example a name that includes that of the remote system.
3. Optionally, a **Description** can be entered to store additional information.
4. Click **Submit** to complete the creation. A repair server is created using the outgoing sync configuration details, including: vSAN Host (address of the remote destination), vSAN Port, system-generated authorized username/password, and encryption setting.

## Create a Repair Server from the Repair Servers List Page

In instances where there is no current outgoing sync from which to configure the repair server (e.g. a three-way sync configuration or a previous sync destination that is no longer in use), the following instructions can be used:

1. Navigate to **Backup/DR** > **Repair Servers**.
2. Click **New** on the left menu.
3. Enter a **Name** for the repair server. Use a name that will be helpful for future administration, for example a name that includes that of the remote system.
4. Optionally, a **Description** can be entered to store additional information.

### Automatic (Copy) Credentialling

Credentials can be copied from an existing outgoing sync:

* Select ***Copy*** in the **Credentialling** dropdown list
* Select **desired sync** in the **Copy Credentials from** dropdown list

### Manual Credentialling

To manually enter credential information: select ***Manual*** in the **Credentialling** dropdown list.

### Credential Fields

* **vSAN Host** - url to the root level of the remote system
* **vSAN Port** - default 14201, a different port can be used but must also be configured on the remote side with ports open on intermediate firewall(s)
* **User**
* **Password** and **Confirm Password** for the specified VergeOS user
* **Encryption**

5. Click **Submit** to complete the creation.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vergeos-demo.com/automate-protect-and-extend/backup-and-dr/repair-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.