GitHub Enterprise Server Backup Utilities v3.9.5
·
3 commits
to 3.9-stable
since this release
Bug Fixes
- On an instance with multiple nodes, backups failed silently if a node was offline or unavailable.
- On an instance with Actions enabled, incorrect backup and restore settings prevented the storage container name from being restored. This made the logs from that container inaccessible, and caused Actions to create a new storage container in a different location.
- When restoring a backup using the
ghe-restorecommand, 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 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 thatreplica-hostnameresides in the same region as the backup host in order to reduce latency. - 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
ghe-backuporghe-restorecommands 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.