GitHub Enterprise Server Backup Utilities v3.12.2

Bug Fixes

• Backing up a stand-alone GHES instance would report the incorrect messages in the output - Clustering is not configured on this host. and 0 MB data transfer estimates.
• When running a backup of HA instance, Estimated Data Transfer Sizes were not reported accurately.

GitHub Enterprise Server Backup Utilities v3.11.3

Bug Fixes

• Backing up a stand-alone GHES instance would report the incorrect messages in the output - Clustering is not configured on this host. and 0 MB data transfer estimates.
• When running a backup of HA instance, Estimated Data Transfer Sizes were not reported accurately.

GitHub Enterprise Server Backup Utilities v3.10.5

Bug Fixes

• Backing up a stand-alone GHES instance would report the incorrect messages in the output - Clustering is not configured on this host. and 0 MB data transfer estimates.
• When running a backup of HA instance, Estimated Data Transfer Sizes were not reported accurately.

GitHub Enterprise Server Backup Utilities v3.9.7

Bug Fixes

• Backing up a stand-alone GHES instance would report the incorrect messages in the output - Clustering is not configured on this host. and 0 MB data transfer estimates.
• When running a backup of HA instance, Estimated Data Transfer Sizes were not reported accurately.

GitHub Enterprise Server Backup Utilities v3.12.1

Bug Fixes

• When restoring an instance using the ghe-restore command from GitHub Enterprise Server Backup Utilities, restoration of files in /user/data/storage failed with a xrealloc: cannot allocate (...) bytes error.

Backups and Disaster Recovery

• ghe-backup or ghe-restore commands could fail to delete progress files created by older versions of GitHub Enterprise Server Backup Utilities.
• Administrators running ghe-backup will no longer see "Verifying Routes" messages. Route verification has been found to be unnecessary and has been disabled by default. Administrators who prefer to see these messages can enable route verification by setting GHE_ROUTE_VERIFICATION to "true" in their backup-utils configuration file.
• To prevent problems associated with incomplete backups, the ghe-restore process will exit with an error if the snapshot being restored is incomplete.

GitHub Enterprise Server Backup Utilities v3.11.2

Bug Fixes

• When restoring an instance using the ghe-restore command from GitHub Enterprise Server Backup Utilities, restoration of files in /user/data/storage failed with a xrealloc: cannot allocate (...) bytes error.

Backups and Disaster Recovery

• Administrators running ghe-backup will no longer see "Verifying Routes" messages. Route verification has been found to be unnecessary and has been disabled by default. Administrators who prefer to see these messages can enable route verification by setting GHE_ROUTE_VERIFICATION to "true" in their backup-utils configuration file.
• To prevent problems associated with incomplete backups, the ghe-restore process will exit with an error if the snapshot being restored is incomplete.

GitHub Enterprise Server Backup Utilities v3.10.4

Bug Fixes

• When restoring an instance using the ghe-restore command from GitHub Enterprise Server Backup Utilities, restoration of files in /user/data/storage failed with a xrealloc: cannot allocate (...) bytes error.

Backups and Disaster Recovery

• Administrators running ghe-backup will no longer see "Verifying Routes" messages. Route verification has been found to be unnecessary and has been disabled by default. Administrators who prefer to see these messages can enable route verification by setting GHE_ROUTE_VERIFICATION to "true" in their backup-utils configuration file.
• To prevent problems associated with incomplete backups, the ghe-restore process will exit with an error if the snapshot being restored is incomplete.

GitHub Enterprise Server Backup Utilities v3.9.6

Bug Fixes

• When restoring an instance using the ghe-restore command from GitHub Enterprise Server Backup Utilities, restoration of files in /user/data/storage failed with a xrealloc: cannot allocate (...) bytes error.

Backups and Disaster Recovery

• Administrators running ghe-backup will no longer see "Verifying Routes" messages. Route verification has been found to be unnecessary and has been disabled by default. Administrators who prefer to see these messages can enable route verification by setting GHE_ROUTE_VERIFICATION to "true" in their backup-utils configuration file.
• To prevent problems associated with incomplete backups, the ghe-restore process will exit with an error if the snapshot being restored is incomplete.

GitHub Enterprise Server Backup Utilities v3.12.0

Changes

• When using GitHub Enterprise Server 3.9.10 or newer, 3.10.8 or newer, or 3.11.5 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, or 3.11.5 or newer, with a cluster configuration,
  backup-utils will backup the MySQL database from one of the MySQL replica nodes instead of the primary node.
• ghe-backup will provide a clear error message if an offline node in a cluster configuration is detected by ghe-cluster-host-check.

Backups and Disaster Recovery

• ghe-backup or ghe-restore commands could fail to delete progress files created by older versions of GitHub Enterprise Server Backup Utilities.

GitHub Enterprise Server Backup Utilities v3.11.1

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 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, 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 or ghe-restore commands could fail to delete progress files created by older versions of GitHub Enterprise Server Backup Utilities.