Bug 1725409

Summary:	Restoring from backup including pulp content takes many days
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	Satellite Maintain	Assignee:	Anurag Patel <apatel>
Status:	CLOSED DUPLICATE	QA Contact:	Jameer Pathan <jpathan>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	Unspecified	CC:	apatel, fgarciad, kgaikwad, molasaga
Target Milestone:	Unspecified	Keywords:	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:	2020-04-06 17:13:40 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:

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 ***