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.
Document URL:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/administering_red_hat_satellite/restoring-satellite-server-or-capsule-from-a-backup_admin#Restoring_from_a_Full_Backup_admin
Section Number and Name:
14.1. Restoring from a Full Backup
Describe the issue:
The 1st prerequisite for restoring a satellite from backup is:
Ensure that you are restoring to the correct instance. The Red Hat
Satellite instance must have the same host name, configuration, and
be the same minor version (X.Y) as the original system.
What is meant by "configuration" is unclear.
Suggestions for improvement:
Ensure that you are restoring to the correct instance. The Red Hat
Satellite instance must be similarly sized (number of processors,
memory & storage), have the same host name, and be the same
Satellite software minor version (6.y) as the original system.
Additional information:
I thought it might mean that if the source satellite was setup as a DHCP server, the destination needed setup as one, too. Yet I did a restore of such a satellite to a destination that was *not* setup that way and it appears to have come out of the restoration as a DHCP server.
Upon asking about this in the satellite-tech-list mailing list, I got this response:
https://lists.corp.redhat.com/archives/satellite-tech-list/2023-May/001392.html
Hello BErnie,
Many thanks for this suggestion for improvement.
The BZ will go through proper team triage and updates will be shared as soon as soon as the work on the fix starts.
Thnak you!
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.