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.

GitHub Enterprise Server Backup Utilities v3.14.1

Bug Fixes

• Restoring a backup into a new hostname would not correctly updated the OIDC confirationation for remote blob providers. Now it will.

Changes

• If trust-sender is not supported on the backup-utils host version of rsync, a warning will emit.

GitHub Enterprise Server Backup Utilities v3.13.2

Changes

• More detailed information is logged when errors occur during a backup or restore operation.
• If trust-sender is not supported on the backup-utils host version of rsync, a warning will emit.

GitHub Enterprise Server Backup Utilities v3.12.5

Changes

• More detailed information is logged when errors occur during a backup or restore operation.
• If trust-sender is not supported on the backup-utils host version of rsync, a warning will emit.

GitHub Enterprise Server Backup Utilities v3.11.6

Changes

• More detailed information is logged when errors occur during a backup or restore operation.
• If trust-sender is not supported on the backup-utils host version of rsync, a warning will emit.

GitHub Enterprise Server Backup Utilities v3.10.7

Changes

• More detailed information is logged when errors occur during a backup or restore operation.

GitHub Enterprise Server Backup Utilities v3.14.0

Bug Fixes

• By default, the management console password is restored from the backup snapshot data. In 3.14, a backup configuration variable, GHE_MANAGE_CONSOLE_PW_RESTORE, was added to allow administrators to specify that the current Management Console password is to be retained during restore operations.

Changes

• Added more meaningful error messages when a trap is triggered. This change will help users understand the context of the error and take appropriate action.
• Passwords and chat secrets are restored only when -c option is used, in order to reduce security risks of sharing secrets between different environments.

GitHub Enterprise Server Backup Utilities v3.13.1

Backups and Disaster Recovery

• Encrypted column keys from backup snapshots were not always restored.

GitHub Enterprise Server Backup Utilities v3.12.4

Changes

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

Backups and Disaster Recovery

• When backing up an instance in a cluster configuration using GitHub Enterprise Server Backup Utilities, if any nodes were offline, pre-flight checks would silently fail.
• Password and Chat Integration secrets were restored without using the settings -c option.
• Verbose logs include the list of storage objects being restored, helping users track the progress of the restore operation and aiding in debugging any issues.
• Encrypted column keys from backup snapshots were not always restored.

GitHub Enterprise Server Backup Utilities v3.11.5

Changes

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

Backups and Disaster Recovery

• When backing up an instance in a cluster configuration using GitHub Enterprise Server Backup Utilities, if any nodes were offline, pre-flight checks would silently fail.
• Password and Chat Integration secrets were restored without using the settings -c option.
• Verbose logs include the list of storage objects being restored, helping users track the progress of the restore operation and aiding in debugging any issues.
• Encrypted column keys from backup snapshots were not always restored.