GitHub Enterprise Server Backup Utilities v3.10.0

Features

• To reduce the time to generate a backup using ghe-backup, administrators can choose to prune old backup snapshots after a new backup has been generate. For more information, see "Scheduling backups & snapshot pruning."
• On instances with large MySQL databases , administrators who wish to save storage space can use the new --incremental flag with ghe-backup and ghe-restore. For more information, see "Incremental MySQL Backups and Restores"
• Administrators can choose to skip the storage and software version checks that are run during ghe-backup using the --skip-checks flag. For more information, see "Using the backup and restore commands".

Changes

• Removed the git clone path for setting up backup-utils from the getting started instructions.
• Added bc v1.07 or newer to the requirements for a backup host machine.

GitHub Enterprise Server Backup Utilities v3.9.2

Bug fixes

• Setting GHE_HOSTNAME as an environment variable did not override the value configured in backup.config.

GitHub Enterprise Server Backup Utilities v3.8.2

Changes

• Administrators can disable backup or restoration of GitHub Pages data.

GitHub Enterprise Server Backup Utilities v3.7.2

Changes

• Administrators can disable backup or restoration of GitHub Pages data.

GitHub Enterprise Server Backup Utilities v3.6.2

Changes

• Administrators can disable backup or restoration of GitHub Pages data.

GitHub Enterprise Server Backup Utilities v3.9.1

Bug fixes

• On an instance with GitHub Actions enabled, GitHub Enterprise Server Backup Utilities sometimes failed to back up GitHub Actions data despite indication that the backup was successful.
• On a standalone GitHub Enterprise Server instance with GitHub Actions enabled, backups failed.
• For administrators who need to correlate and troubleshoot errors, ghe-backup and ghe-restore include timestamps with logging information.
• Fixes a known issue that caused users to potentially not be able to sign into the instance after restoration of a backup created using GitHub Enterprise Server Backup Utilities 3.9.0. For more information on this known issue, see "Known issues with backups for your instance."

GitHub Enterprise Server Backup Utilities v3.8.1

Bug fixes

• On an instance with GitHub Actions enabled, GitHub Enterprise Server Backup Utilities sometimes failed to back up GitHub Actions data despite indication that the backup was successful.
• On a standalone GitHub Enterprise Server instance with GitHub Actions enabled, backups failed.
• For administrators who need to correlate and troubleshoot errors, ghe-backup and ghe-restore include timestamps with logging information.
• Fixes a known issue that caused users to potentially not be able to sign into the instance after restoration of a backup created using GitHub Enterprise Server Backup Utilities 3.8.0. For more information on this known issue, see "Known issues with backups for your instance."

GitHub Enterprise Server Backup Utilities v3.7.1

Bug fixes

• On an instance with GitHub Actions enabled, GitHub Enterprise Server Backup Utilities sometimes failed to back up GitHub Actions data despite indication that the backup was successful.
• Fixes a known issue that caused users to potentially not be able to sign into the instance after restoration of a backup created using GitHub Enterprise Server Backup Utilities 3.7.0. For more information on this known issue, see "Known issues with backups for your instance."

GitHub Enterprise Server Backup Utilities v3.6.1

Bug fixes

• On an instance with GitHub Actions enabled, GitHub Enterprise Server Backup Utilities sometimes failed to back up GitHub Actions data despite indication that the backup was successful.

GitHub Enterprise Server Backup Utilities v3.9.0

Overview

• Includes general improvements & bug fixes and support for GitHub Enterprise Server v3.9.0.

Known issues

• After restoration of a backup created using GitHub Enterprise Server Backup Utilities 3.7.0 or 3.8.0, users may not be able to sign into the instance. For more information, see "Known issues with backups for your instance." [Updated: 2023-07-03]