[YW] Restoring universe backup from Backups tab into a different universe fails to create tables #5890
Assignees
Labels
Comments
andrewc-dev
added
priority/critical
andrewc-dev
pushed a commit
that referenced
this issue
Sep 30, 2020
…e in the event of restoring cross-universe. Summary: When restoring to a universe we check the universeUUID of the backupInfo object but universe backups contain nested backupInfo, so the fix is to update the nested objects to match the parent universeUUID. Test Plan: Create universe backup and then try restoring to a different universe from the Backups tabs and selecting a specific backup from the table action. Reviewers: sanketh, arnav Reviewed By: arnav Subscribers: jenkins-bot, yugaware Differential Revision: https://phabricator.dev.yugabyte.com/D9514
andrewc-dev
pushed a commit
that referenced
this issue
Sep 30, 2020
…e in the event of restoring cross-universe. Summary: When restoring to a universe we check the universeUUID of the backupInfo object but universe backups contain nested backupInfo, so the fix is to update the nested objects to match the parent universeUUID. Test Plan: Create universe backup and then try restoring to a different universe from the Backups tabs and selecting a specific backup from the table action. Reviewers: sanketh, arnav Reviewed By: arnav Subscribers: jenkins-bot, yugaware Differential Revision: https://phabricator.dev.yugabyte.com/D9514
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When restoring from the action in the list of backups, the user is able to specify a different universe. When the restore completes no missing tables are added to the destination universe.
The text was updated successfully, but these errors were encountered: