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.
Description of problem:
Customer's issues with current backup solutions:
1. I do not want to shutdown satellite for a long period of time to do backup.
2. "katello-backup --skip-pulp-content" is not useful. I do not want a backup which can not restore a full functional satellite.
3. " katello-backup --online-backup" is also not good, as " While performing an on-line backup, it is important that nothing is changed in the Satellite that affects the Pulp database, such as changes to Content Views and synchronizing of repositories, or the result will be an incomplete backup of the Pulp database."
Version-Release number of selected component (if applicable):
6.2.2
Actual results:
Satellite services must be stopped or changes cannot be made during the current backup process options.
Expected results:
Satellites are in a 24/7 environment which is in use around the clock. The customer is trying to setup a DR environment with no downtime or lack of functionality during the backup process.