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.
DescriptionBenjamin Chardi
2016-07-11 07:13:17 UTC
Description of problem:
Dear friends,
We are building the DR strategy for our Satellite 6.1.9 deployment, one satellite server + 3 capules with RHEL6 and RHEL7 channels + some custom content (~ 250G on /var/lib/pulp). For the moment we have ~50 clients attached to it but in the next year we will reach more that 30K clients attached.
The problem that we are facing now (and it will be getting worst when we attach more clients) is that the recommended DR strategy for Satellite 6.1.9 (katello-backup and katello-restore) is taking more that 4 hours to complete a full backup and it requires satellite services to be stopped in order to do it.
What we need is a faster and continuos DR strategy without the need to stop satellite services. Maybe the inter satellite sync ISS feature provided on Satellite 6.2 can be used to archive it. The ideal scenario for this kind of satellite DR for us is:
* Satellite is continuously hot-replicating content to Satellite-DR .
* Satellite-DR must be fully operational as a replica of Satellite, Satellite-DR can have some clients attached to it and that clients must see the replicated content from Satellite.
* In case of DR scenario, after executing some fast process on Satellite-DR the satellite services are re-established and clients can get content from Satellite-DR via Capsules.
Version-Release number of selected component (if applicable):
Satellite 6.1.9
How reproducible:
Always when katello-backup and katello-restore are executed
Steps to Reproduce:
1.
2.
3.
Actual results:
It takes more than 4 hours to complete katello-backup and the process need satellite to be stopped in some steps.
Expected results:
Continuous and fast katello-backup without stopping Satellite services
Additional info: