Skip to content

Commit 3720f16

Browse files
author
Matt Duff
committed
updated title and first paragraph
1 parent bab312c commit 3720f16

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ This repository includes backup and recovery utilities for [GitHub Enterprise][1
1313
- **[Using the backup and restore commands](#using-the-backup-and-restore-commands)**
1414
- **[Scheduling backups](#scheduling-backups)**
1515
- **[Backup snapshot file structure](#backup-snapshot-file-structure)**
16-
- **[How do backup snapshots differ from a HA (High Availability) replica?](#how-do-backup-snapshots-differ-from-a-ha-high-availability-replica)
16+
- **[How does backup utilities differ from an HA (High Availability) replica?](#how-does-backup-utilities-differ-from-an-ha-high-availability-replica)
1717
- **[Support](#support)**
1818

1919
### Features
@@ -232,8 +232,8 @@ most recent successful snapshot:
232232
Note: the `GHE_DATA_DIR` variable set in `backup.config` can be used to change
233233
the disk location where snapshots are written.
234234

235-
### How do backup snapshots differ from the HA (High Availability) replica?
236-
The backup utilities and [HA replica](https://help.github.com/enterprise/admin/guides/installation/high-availability-cluster-configuration/) serve different yet complementary purposes as part of a recommended GitHub Enterprise deployment.
235+
### How does backup utilities differ from an HA (High Availability) replica?
236+
It is recommended that both backup utilities and an [HA replica](https://help.github.com/enterprise/admin/guides/installation/high-availability-cluster-configuration/) are used as part of a GitHub Enterprise deployment but they serve different roles.
237237

238238
##### The purpose of the High Avaibility replica
239239
The HA replica is a fully redundant secondary GitHub Enterprise instance, kept in sync with the primary instance via replication of all major datastores. This active/passive cluster configuration is designed to minimize service disruption in the event of hardware failure or major network outage affecting the primary instance. Because some forms of data corruption or loss may be replicated immediately from primary to replica, it is not a replacement for the backup utilities as part of your disaster recovery plan.

0 commit comments

Comments
 (0)