A Repair Server provides a potential repair mechanism after a system experiences a problem extending beyond its redundancy tolerance (e.g., simultaneous drive failures spanning multiple nodes). Typically, a Repair Server is a sync destination that contains a relatively 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 a Repair Server be in place whenever possible.
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.
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).
For instructions on adding the outgoing sync, click here: Adding Sites to the Dashboard.
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.
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:
Credentials can be pulled from an existing outgoing sync:
Select Use Outgoing Sync in the Credentials dropdown list.
Select Desired Sync in the Outgoing Sync dropdown list.
To manually enter credential information:
select Manual in the Credentials dropdown list.
Need more Help? Email support@verge.io or call us at (855) 855-8300