You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/admin/backing-up-and-restoring-your-instance/about-the-backup-service-for-github-enterprise-server.md
For high availability, you can designate a replica node as your backup server. To minimize latency, {% data variables.product.github %} recommends picking a replica node in the same region or datacenter as your primary node.
15
17
16
-
> [!IMPORTANT]
18
+
> [!IMPORTANT]
17
19
> Backups from cache replica nodes or active geo replica nodes are not supported.
18
20
19
-
To configure your backup server on a replica, run the following commands. See [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/backup-service-for-github-enterprise-server/configuring-the-backup-service).
21
+
To configure your backup server on a replica, run the following commands. See [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/configuring-the-backup-service).
For clustering, you can designate a node as your backup server. To minimize latency, {% data variables.product.github %} recommends picking a data node (for example, a `mysql-server` node or a `git-server` node) instead of a frontend node.
15
17
16
-
> [!IMPORTANT]
18
+
> [!IMPORTANT]
17
19
> Only one node can be specified as a `backup-server` node.
18
20
19
-
1. To configure your backup server, run the following commands to set up a backup disk on one of the cluster nodes of your choice. See [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/backup-service-for-github-enterprise-server/configuring-the-backup-service).
21
+
1. To configure your backup server, run the following commands to set up a backup disk on one of the cluster nodes of your choice. See [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/configuring-the-backup-service).
20
22
21
23
```shell
22
24
ghe-storage-init-backup /dev/YOUR_DEVICE_NAME
23
25
24
26
ghe-config-apply
25
27
```
26
-
28
+
27
29
1. After `ghe-config-apply` is executed, the `backup-server` role will be set on this cluster node. You can now run `ghe-backup` directly on this node, or use the management console to schedule backups.
intro: As part of a disaster recovery plan, you can protect production data on {% data variables.location.product_location %} by configuring automated backups.
21
21
versions:
22
-
ghes: '*'
22
+
ghes: '< 3.22'
23
23
contentType: how-tos
24
24
category:
25
25
- Back up and upgrade your instance
26
26
---
27
27
28
-
## About backup options for {% data variables.product.prodname_ghe_server %}
29
-
30
-
{% data variables.product.company_short %} offers two options for backing up your {% data variables.product.prodname_ghe_server %} instance:
31
-
32
-
***{% data variables.product.prodname_enterprise_backup_utilities %}**: An open-source backup system that you install on a separate host. For more information, see the sections below.
33
-
***{% data variables.product.prodname_enterprise_backup_service %} (in {% data variables.release-phases.public_preview %})**: A managed backup service available in {% data variables.product.prodname_ghe_server %}. See [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/backup-service-for-github-enterprise-server).
28
+
>[!IMPORTANT][{% data variables.product.prodname_enterprise_backup_service %}](/admin/backing-up-and-restoring-your-instance/about-the-backup-service-for-github-enterprise-server) is now the preferred solution for backing up a {% data variables.product.prodname_ghe_server %} appliance. {% data variables.product.prodname_enterprise_backup_utilities %} is scheduled for removal in {% data variables.product.prodname_ghe_server %} version 3.22
34
29
35
30
## About {% data variables.product.prodname_enterprise_backup_utilities %}
36
31
@@ -54,7 +49,7 @@ Physical storage requirements will vary based on Git repository disk usage and e
54
49
55
50
| Hardware | Recommendation |
56
51
| -------- | --------- |
57
-
|**vCPUs**| 4 |
52
+
|**vCPUs**| 4 |
58
53
|**Memory**| 8 GB |
59
54
|**Storage**| Five times the primary instance's allocated storage |
60
55
@@ -208,4 +203,4 @@ Optionally, you can run the following command to print the current progress, the
If you are running {% data variables.product.prodname_ghe_server %} on a cloud platform or virtualization platform that supports disk snapshots, we recommend that you use snapshots to archive your backup disk, and recreate a new backup disk for testing, restoring, or disaster recovery purposes. However, if your infrastructure does not support disk snapshots or similar solutions, you can setup a {% data variables.product.prodname_ghe_server %} backup archive on a remote {% data variables.product.prodname_ghe_server %} appliance for data replication and restoration purposes.
@@ -15,7 +17,7 @@ If you are running {% data variables.product.prodname_ghe_server %} on a cloud p
15
17
16
18
Remote archives are required to be saved on a backup disk of a {% data variables.product.prodname_ghe_server %} appliance, which is used as a staging or testing {% data variables.product.prodname_ghe_server %} appliance. Follow these steps to configure remote backup archives.
17
19
18
-
1. Set up a backup disk on a remote {% data variables.product.prodname_ghe_server %} appliance. See [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/backup-service-for-github-enterprise-server/configuring-the-backup-service).
20
+
1. Set up a backup disk on a remote {% data variables.product.prodname_ghe_server %} appliance. See [AUTOTITLE](/admin/backing-up-and-restoring-your-instance/configuring-the-backup-service).
19
21
1. From the production appliance, run the following command to initiate configuration and display the SSH public key that needs to be added to the remote {% data variables.product.prodname_ghe_server %} appliance:
0 commit comments