This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2279251 - Failed to restore incremental backup with database corrupted error
Summary: Failed to restore incremental backup with database corrupted error
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.14.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-06 06:14 UTC by Hao Chang Yu
Modified: 2024-06-06 17:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:36:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-24936 0 None Migrated None 2024-06-06 17:36:56 UTC

Description Hao Chang Yu 2024-05-06 06:14:07 UTC 
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>
~~~
Comment 1 Eric Helms 2024-06-06 17:36:57 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.