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 1725409 - Restoring from backup including pulp content takes many days
Summary: Restoring from backup including pulp content takes many days
Keywords:
Status: CLOSED DUPLICATE of bug 1726595
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: Unspecified
Assignee: Anurag Patel
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-30 14:18 UTC by Mike McCune
Modified: 2020-04-06 17:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-06 17:13:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Mike McCune 2019-06-30 14:18:33 UTC 
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.
Comment 4 Mike McCune 2020-04-06 17:13:40 UTC 
This is a dupe of:

https://bugzilla.redhat.com/show_bug.cgi?id=1726595

closing

*** This bug has been marked as a duplicate of bug 1726595 ***
Note You need to log in before you can comment on or make changes to this bug.