Bug 2262827

Summary:	Request to improve Satellite Backup and Restore documentation
Product:	Red Hat Satellite	Reporter:	Ashish Humbe <ahumbe>
Component:	Satellite Maintain	Assignee:	Akshay Gadhave <agadhave>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.14.0	CC:	agadhave, ehelms, rlavi
Target Milestone:	Unspecified	Keywords:	Documentation, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 17:01:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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