GitHub Enterprise Server Backup Utilities v3.14.4

Changes

• Restores will automatically detect incremental MySQL backups without requiring the -i flag.

GitHub Enterprise Server Backup Utilities v3.13.4

Changes

• Restores will automatically detect incremental MySQL backups without requiring the -i flag.

GitHub Enterprise Server Backup Utilities v3.16.1

Backups and Disaster Recovery

• Backups could fail with an error on awk when logging rsync details, particularly on memory-constrained systems.

GitHub Enterprise Server Backup Utilities v3.15.2

Backups and Disaster Recovery

• Backups could fail with an error on awk when logging rsync details, particularly on memory-constrained systems.

GitHub Enterprise Server Backup Utilities v3.14.3

Backups and Disaster Recovery

• Backups could fail with an error on awk when logging rsync details, particularly on memory-constrained systems.

GitHub Enterprise Server Backup Utilities v3.16.0

Bug fixes

• Not applicable in this release.

Changes

• Added GHE_SKIP_SEARCH_INDICES as an option to skip Elasticsearch backup and restore. This will allow users on standalone and HA configuration to save time on backups and then re-build indices from the DB, which is how it currently works on cluster.

• Added more error information for ghe-gc-disable.

• Added trap_full_cleanup for ghe-prune-snapshots so we will know where it fails.

GitHub Enterprise Server Backup Utilities v3.15.1

Changes

• In a standalone or high availability configuration, Elasticsearch backup and restore can be disabled to improve performance.

GitHub Enterprise Server Backup Utilities v3.14.2

Changes

• In a standalone or high availability configuration, Elasticsearch backup and restore can be disabled to improve performance.

GitHub Enterprise Server Backup Utilities v3.13.3

Changes

• In a standalone or high availability configuration, Elasticsearch backup and restore can be disabled to improve performance.

GitHub Enterprise Server Backup Utilities v3.15.0

Bug Fixes

• If a backup was restored on an already configured appliance, ghe-config-apply may have incorrectly determined the diff and skipped some operations. Note: The diff is between the current configuration in /data/user/common and the configuration stored in the /data/user/common/ghe-config-apply/config-file-history directory.
• Console output was overwritten by ssh trace when verbose log was enabled.
• The ghe-host-check command showed warnings about rsync when no warning was needed.

Changes

• Error handling for MySQL backups has improved. The chosen backup strategy is logged by default. The error coverage and messaging are enhanced, including new warnings for file size constraints relevant to the backup process affect.