Skip to content

Use old rsync restore method for pages prior to 2.13 #426

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 20, 2018

Conversation

lildude
Copy link
Member

@lildude lildude commented Aug 20, 2018

When unifying the backup and restore approach in #375 we opted to keep using the old behaviour when restoring to hosts running versions prior to GitHub Enterprise 2.13.0 to remove a requirement for a specific GitHub Enterprise release in order to restore.

024cb1f is where I implemented this for repositories and gists but I completely forgot about pages.

This PR adds back the ghe-restore-pages-rsync script required for those older releases and uses it instead of the newer approach.

This will fix problems restoring to GitHub Enterprise 2.12.5 and earlier.

Fixes https://github.com/github/backup-utils/issues/425

/cc @terrorobe @rubiojr

This is needed for restoring to pre-2.13 releases and was missed when I
did something similar for repo, storage and gist restores.
@lildude lildude requested a review from a team August 20, 2018 15:03
@lildude lildude merged commit 08368ff into master Aug 20, 2018
@lildude lildude deleted the lildude/rsync-for-pages-pre-213 branch August 20, 2018 15:30
@lildude lildude added the bug label Aug 20, 2018
@lildude lildude mentioned this pull request Aug 21, 2018
dooleydevin added a commit that referenced this pull request Jul 21, 2023
…t-always-restore-column-encryption-keys

Backport 349 for 3.7: Always restore column encryption keys
@dooleydevin dooleydevin mentioned this pull request Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document or handle version gap in backup-utils
2 participants