Backup Utils Versions Save

Changes

• As part of the upgrade to GitHub Enterprise Server 3.13, Elasticsearch (ES) is upgraded from version 5.6.16 to 8.7.0. Upgrading platform components improves performance and security posture. For important upgrade considerations, see "preparing for the elastic search upgrade."
• If you restore a backup from an instance running GHES 3.11 or 3.12, then any content that relies on ES will only be available after the ES indexes have been migrated and rebuilt on the 3.13 instance.

Bug Fixes

• Offline nodes would silently fail when backing up a cluster.
• When running a backup of the HA instance, Estimated Data Transfer Sizes are not reported accurately.
• Package storage secrets were restored when -c flag was not used.
• Backing up a stand-alone GHES instance would report incorrect messages in the output. - Clustering is not configured on this host and 0 MB data transfer estimates.

Bug Fixes

• Only restore package storage secrets if -c flag is used.

Bug Fixes

• Only restore package storage secrets if -c flag is used.

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.

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.

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.

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.

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.

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.

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.