Skip to content

GitHub Enterprise Server Backup Utilities v3.10.3
Compare
Choose a tag to compare
@release-controller release-controller released this 19 Jan 21:14
· 4 commits to 3.10-stable since this release
v3.10.3
da132c8

Bug Fixes

  • On an instance with multiple nodes, backups failed silently if a node was offline or unavailable.
  • When restoring a backup using the ghe-restore command, the restore operation could fail due to the root disk filling completely. [Updated 2024-02-29]

Changes

  • When using GitHub Enterprise Server 3.9.10 or newer, or 3.10.8 or newer, with a high availability (HA) configuration, you can backup the MySQL database from a HA replica by setting ghe-config mysql.backup.replica <replica-hostname> on your primary node. We recommend that replica-hostname resides in the same region as the backup host in order to reduce latency. [Updated 2024-03-01]
  • When using GitHub Enterprise Server 3.9.10 or newer with a cluster configuration, backup-utils will backup MySQL from one of the MySQL replica nodes instead of the primary node.

Backups and Disaster Recovery

  • In the Incremental MySQL Backups and Restores documentation, the variable for the number of incremental backups was incorrectly given as GHE_INCREMENTAL_BACKUP_MAX. This has been corrected to GHE_INCREMENTAL_MAX_BACKUPS.
  • ghe-backup or ghe-restore commands could fail to delete progress files created by older versions of GitHub Enterprise Server Backup Utilities.
  • For better compatibility across Linux distributions, the host operating system version displayed in output is obtained from /etc/os-release.
Assets 4
Loading