GitHub Enterprise Server Backup Utilities v3.11.1
release-controller
released this
19 Jan 21:14
·
6 commits
to 3.11-stable
since this release
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, 3.10.8 or newer, or 3.11.1 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-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, or 3.11.1 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-backup
orghe-restore
commands could fail to delete progress files created by older versions of GitHub Enterprise Server Backup Utilities.