Project

General

Profile

Actions

Feature #21240

closed

[RFE] katello-restore should offer an option --skip-pulp-content

Added by Daniel Moessner over 6 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Description of problem:

katello-restore --skip-pulp-content

should be a valid option, then the next scheduled sync or a manual sync should rebuild the contents of /var/lib/pulp appropriately.

Version-Release number of selected component (if applicable):
6.2.10

How reproducible:
Always

Steps to Reproduce:
1. katello-restore does not offer this option
2.
3.

Actual results:

katello-restore does not offer this option

Expected results:

Regardless of whether backups include pulp content or not, katello-restore should allow the user the option to skip the requirement to restore the pulp-content. If --skip-pulp-content is used, then the next scheduled sync or manual sync should rebuild the contents of /var/lib/pulp appropriately.

Additional info:
This greatly alleviates backup window and backup volume issues with larger deployments and depending on the customer may decrease recovery time.

This would likely then require full resyncs of downstream systems like... capsules...

Actions #1

Updated by Amit Upadhye almost 3 years ago

  • Status changed from New to Closed

Daniel Moessner wrote:

Description of problem:

katello-restore --skip-pulp-content

should be a valid option, then the next scheduled sync or a manual sync should rebuild the contents of /var/lib/pulp appropriately.

Version-Release number of selected component (if applicable):
6.2.10

How reproducible:
Always

Steps to Reproduce:
1. katello-restore does not offer this option
2.
3.

Actual results:

katello-restore does not offer this option

Expected results:

Regardless of whether backups include pulp content or not, katello-restore should allow the user the option to skip the requirement to restore the pulp-content. If --skip-pulp-content is used, then the next scheduled sync or manual sync should rebuild the contents of /var/lib/pulp appropriately.

Additional info:
This greatly alleviates backup window and backup volume issues with larger deployments and depending on the customer may decrease recovery time.

This would likely then require full resyncs of downstream systems like... capsules...

The foreman-maintain(https://github.com/theforeman/foreman_maintain) now handles the backup and restore. The skip pulp content option is available by this project. Accordingly I am closing this issue.

Thank You!

Actions

Also available in: Atom PDF