Skip to main content
ドキュメントには� �繁に更新が� えられ、その都度公開されています。本ページの翻訳はま� 未完成な部分があることをご了承く� さい。最新の情� �については、英語のドキュメンテーションをご参照く� さい。本ページの翻訳に問題がある� �合はこちらまでご連絡く� さい。

このバージョンの GitHub Enterprise はこの日付をもって終了となりました: 2022-06-03. 重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの改善、新機能のためには、最新バージョンのGitHub Enterpriseにアップグレードしてく� さい。 アップグレードに関する支援については、GitHub Enterprise supportに連絡してく� さい。

Configuring backups on your appliance

As part of a disaster recovery plan, you can protect production data on GitHub Enterprise Serverインスタンス by configuring automated backups.

About GitHub Enterprise Serverバックアップユーティリティ

GitHub Enterprise Serverバックアップユーティリティ is a backup system you install on a separate host, which takes backup snapshots of GitHub Enterprise Serverインスタンス at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing GitHub Enterprise Server instance to a previous state from the backup host.

Only data added since the last snapshot will transfer over the network and occupy additional physical storage space. To minimize performance impact, backups are performed online under the lowest CPU/IO priority. You do not need to schedule a maintenance window to perform a backup.

For more detailed information on features, requirements, and advanced usage, see the GitHub Enterprise Serverバックアップユーティリティ README.


To use GitHub Enterprise Serverバックアップユーティリティ, you must have a Linux or Unix host system separate from GitHub Enterprise Serverインスタンス.

You can also integrate GitHub Enterprise Serverバックアップユーティリティ into an existing environment for long-term permanent storage of critical data.

We recommend that the backup host and GitHub Enterprise Serverインスタンス be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site.

Physical storage requirements will vary based on Git repository disk usage and expected growth patterns:

Memory2 GB
StorageFive times the primary instance's allocated storage

More resources may be required depending on your usage, such as user activity and selected integrations.

Installing GitHub Enterprise Serverバックアップユーティリティ

Note: To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a Geo-replication configuration.

  1. Download the latest GitHub Enterprise Serverバックアップユーティリティ release and extract the file with the tar command.

    $ tar -xzvf /path/to/github-backup-utils-vMAJOR.MINOR.PATCH.tar.gz	  
  2. Copy the included backup.config-example file to backup.config and open in an editor.

  3. Set the GHE_HOSTNAME value to your primary GitHub Enterprise Server instance's hostname or IP address.

    Note: If your GitHub Enterprise Serverインスタンス is deployed as a cluster or in a high availability configuration using a load balancer, the GHE_HOSTNAME can be the load balancer hostname, as long as it allows SSH access (on port 122) to GitHub Enterprise Serverインスタンス.

  4. Set the GHE_DATA_DIR value to the filesystem location where you want to store backup snapshots.

  5. Open your primary instance's settings page at https://HOSTNAME/setup/settings and add the backup host's SSH key to the list of authorized SSH keys. For more information, see Accessing the administrative shell (SSH).

  6. Verify SSH connectivity with GitHub Enterprise Serverインスタンス with the ghe-host-check command.

    $ bin/ghe-host-check		  
  7. To create an initial full backup, run the ghe-backup command.

    $ bin/ghe-backup		  

For more information on advanced usage, see the GitHub Enterprise Serverバックアップユーティリティ README.

Scheduling a backup

You can schedule regular backups on the backup host using the cron(8) command or a similar command scheduling service. The configured backup frequency will dictate the worst case recovery point objective (RPO) in your recovery plan. For example, if you have scheduled the backup to run every day at midnight, you could lose up to 24 hours of data in a disaster scenario. We recommend starting with an hourly backup schedule, guaranteeing a worst case maximum of one hour of data loss if the primary site data is destroyed.

If backup attempts overlap, the ghe-backup command will abort with an error message, indicating the existence of a simultaneous backup. If this occurs, we recommended decreasing the frequency of your scheduled backups. For more information, see the "Scheduling backups" section of the GitHub Enterprise Serverバックアップユーティリティ README.

Restoring a backup

In the event of prolonged outage or catastrophic event at the primary site, you can restore GitHub Enterprise Serverインスタンス by provisioning another GitHub Enterprise appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target GitHub Enterprise appliance as an authorized SSH key before restoring an appliance.

Note: If GitHub Enterprise Serverインスタンス has GitHub Actions enabled, you must first configure the GitHub Actions external storage provider on the replacement appliance before running the ghe-restore command. For more information, see "Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled."

Note: When performing backup restores to GitHub Enterprise Serverインスタンス, the same version supportability rules apply. You can only restore data from at most two feature releases behind.

For example, if you take a backup from GHES 3.0.x, you can restore it into a GHES 3.2.x instance. But, you cannot restore data from a backup of GHES 2.22.x onto 3.2.x, because that would be three jumps between versions (2.22 > 3.0 > 3.1 > 3.2). You would first need to restore onto a 3.1.x instance, and then upgrade to 3.2.x.

To restore GitHub Enterprise Serverインスタンス from the last successful snapshot, use the ghe-restore command. You should see output similar to this:

$ ghe-restore -c
> Checking for leaked keys in the backup snapshot that is being restored ...
> * No leaked keys found
> Connect OK (v2.9.0)

> WARNING: All data on GitHub Enterprise appliance (v2.9.0)
>          will be overwritten with data from snapshot 20170329T150710.
> Please verify that this is the correct restore host before continuing.
> Type 'yes' to continue: yes

> Starting restore of from snapshot 20170329T150710
# ...output truncated
> Completed restore of from snapshot 20170329T150710
> Visit to review appliance configuration.

Note: The network settings are excluded from the backup snapshot. You must manually configure the network on the target GitHub Enterprise Server appliance as required for your environment.

You can use these additional options with ghe-restore command:

  • The -c flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using backup and restore commands" section of the GitHub Enterprise Serverバックアップユーティリティ README.
  • The -s flag allows you to select a different backup snapshot.