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 1435063 - [RFE] Backup and Disaster Discovery chapter enhancement
Summary: [RFE] Backup and Disaster Discovery chapter enhancement
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Server Administration Guide
Version: 6.2.10
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: Stephen Wadeley
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks: Sat6_HA_Tracker
TreeView+ depends on / blocked
 
Reported: 2017-03-23 03:11 UTC by jalviso
Modified: 2021-03-11 15:04 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-02 09:54:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description jalviso 2017-03-23 03:11:16 UTC
Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/server_administration_guide/chap-red_hat_satellite-server_administration_guide-backup_and_disaster_recovery#sect-Red_Hat_Satellite-Server_Administration_Guide-Backup_and_Disaster_Recovery-Backing_up_Red_Hat_Satellite_Server

Section Number and Name: 

5.1. Backing up Red Hat Satellite Server
5.2. Restoring Red Hat Satellite Server from a Backup

Describe the issue: 

On Section 5.1, can you add description as to what is expected of the script? Does it stop the katello-services? Also, can you elaborate on what other options are available? Supported or Unsupported? You mention online option, what else are available?

On Section 5.2, can you write down in detail the guidelines/requirements/pre-requisites on the Satellite build that katello-restore needs to be run?  In this section, I can see:

"This process restores the backup on the same server that generated the backup. If the original system is unavailable, provision the same configuration with the same settings (in particular, the host name must be the same)."

This is one of the requirements. It would be good to have it in bulleted form.
Also, can you clarify if in order to restore, katello-services of the original Satellite must be running or down? The reason I'm asking is that customer uses this section to create a DR Plan with their production Satellite.


Suggestions for improvement: 

State clearly in bullet points all the requirements/guidelines/pre-requisites of restoring Satellite 6 backup just like when installing a Sat6, we have all those requirements.

Additional information: 


Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

Comment 24 Stephen Wadeley 2017-05-18 15:38:53 UTC
interesting:

Capsule Backup Solution - Red Hat Customer Portal - https://access.redhat.com/solutions/2651591


Does RedHat support machine snapshot backup for Satellite 6.2? - Red Hat Customer Portal - https://access.redhat.com/solutions/2859581

Comment 25 Christine Fouant 2017-05-18 19:03:35 UTC
(In reply to Stephen Wadeley from comment #24)
> interesting:
> 
> Capsule Backup Solution - Red Hat Customer Portal -
> https://access.redhat.com/solutions/2651591
> 
> 
> Does RedHat support machine snapshot backup for Satellite 6.2? - Red Hat
> Customer Portal - https://access.redhat.com/solutions/2859581

We are working very diligently on getting LVM snapshot backups into 6.2. At this time, no, but a customer can do their own snapshot backup if they prefer to backup this way.

Comment 45 Lukas Zapletal 2017-05-29 07:31:18 UTC
Hello guys,

I think it's not clear enough from our upstream docs (*) that incremental mode only applies to Pulp content, which is by far the biggest one of all (terabytes of data usually). The rest (mongo, postgres, configs) is never incremental at the moment.

(*) feel free to update upstream docs it need much more

Comment 46 Lukas Zapletal 2017-05-29 08:18:17 UTC
Oh I should have read all of the comments, yes this is little confusing design, I'd definitely change that because people fail understanding this a lot.

Comment 47 Christine Fouant 2017-05-31 15:31:34 UTC
(In reply to Lukas Zapletal from comment #45)
> Hello guys,
> 
> I think it's not clear enough from our upstream docs (*) that incremental
> mode only applies to Pulp content, which is by far the biggest one of all
> (terabytes of data usually). The rest (mongo, postgres, configs) is never
> incremental at the moment.
> 
> (*) feel free to update upstream docs it need much more


Just wondering why that is? The capability for incremental on postgres, mongo, and config files is there; unless there's something about the databases themselves that would prevent incremental backup on them, they should all be incremental.


Note You need to log in before you can comment on or make changes to this bug.