Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Various customer reports indicate that there is a step in the restore process that can take an extraordinarily long period of time for backups containing pulp content.
Anecdotal reports:
"The first ~600GB were fast to recover and restore of the last 100GB is taking already 60 hours."
"Satellite restore 870GB not completed after 6 days"
"It would take forever on restoring the last 100GB of pulp data. (Have around 1.5TB in pulp) and it took maybe four days to complete that part. I did a P2V on 6.2 using the backup and restore method with aroun 1TB of content and it only took a few hours. "
This can be severely business impacting when the Satellite is in a disaster scenario and needing to be brought back online.