Bug 2279251
| Summary: | Failed to restore incremental backup with database corrupted error | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Hao Chang Yu <hyu> |
| Component: | Satellite Maintain | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.14.4 | CC: | rlavi |
| Target Milestone: | Unspecified | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-06 17:36:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Description of problem: Fail to restore an incremental backup with the following missing database file error: ~~~ ERROR -- : Failed executing PULP_SETTINGS=/etc/pulp/settings.py runuser -u pulp -- pulpcore-manager migrate --noinput, exit status 1: psycopg2.OperationalError: FATAL: could not open file "base/12345/67890": No such file or directory ~~~ Steps to Reproduce: 1. Create a full backup of the Satellite using "satellite-maintain backup snapshot" command. 2. After that create one or multiple incremental backups of the Satellite using "satellite-maintain backup snapshot --incremental" command. 3. Restore the backups in the target Satellite using "foreman-maintain restore". Actual results: Incremental backup fails with database missing file error. Expected results: Can restore successfully. Additional info: After restoring a backup, Satellite maintain will run some steps that cause database write. Therefore, the next incremental backup will fail due to data inconsistency between the restored data and the incremental backup. To workaround the issue, we need to run the "foreman-maintain restore" command with some skip steps, except the last incremental restore command. Lets say we have 1 full backup and 3 incremental backups To restore the full backup, run: ~~~ foreman-maintain restore -y --whitelist="restore-reindex-databases,installer-upgrade,installer-upgrade-rake-task,service-start" <full backup directory> ~~~ To restore 1st incremental backup, run: ~~~ foreman-maintain restore -y --whitelist="restore-reindex-databases,installer-upgrade,installer-upgrade-rake-task,service-start" <incremental backup directory 1> ~~~ To restore 2nd incremental backup, run: ~~~ foreman-maintain restore -y --whitelist="restore-reindex-databases,installer-upgrade,installer-upgrade-rake-task,service-start" <incremental backup directory 2> ~~~ To restore the last incremental backup, run: ~~~ foreman-maintain restore -y <last incremental backup directory> ~~~