This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2262827 - Request to improve Satellite Backup and Restore documentation
Summary: Request to improve Satellite Backup and Restore documentation
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.14.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Akshay Gadhave
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-05 15:36 UTC by Ashish Humbe
Modified: 2024-10-05 04:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:01:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-23077 0 None Migrated None 2024-06-06 17:01:34 UTC

Description Ashish Humbe 2024-02-05 15:36:36 UTC 
Description of problem:

We would like to request an improvement in Chapter 11. Backing Up Satellite Server and Capsule Server from Satellite Admin guide where we should provide some recommendations and use cases about taking satellite servers backup for production use. 

Currently, we have different backup methods documented like, 

* Full Backup 
* Backup Without Pulp content
* Incremental Backup
* Snapshot Backup
* Online Backup 

Note: The snapshot backup method is deprecated.

Under section 12.3. Performing a Backup without Pulp Content it is mentioned that " For production use cases, do not restore from a directory that does not contain Pulp content. " and majority of customers take satellite backup without pulp content as it takes a lot of time to perform a backup WITH pulp content. It is practically impossible for customers to take backup of /var/lib/pulp/ which is usually around 500+ GB or 1TB in size. 

Here we are requesting to have Chapter 11 improved in Satellite documentation where we have some Red Hat Recommendations given to the customers about how to take backup in the Production Environment and how to Restore it if/when they need to restore it.  

While adding recommendations, we should provide details about real-time use cases about which backup method should be used for which use cases. Also, we should update the recommendations to restore the satellite server backup in "Chapter 12. Restoring Satellite Server or Capsule Server from a Backup"


https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html/administering_red_hat_satellite/backing-up-satellite-server-and-capsule_admin
Comment 2 Eric Helms 2024-06-06 17:01:35 UTC 
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.
Comment 3 Red Hat Bugzilla 2024-10-05 04:27:13 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.