Bug 1386667 - Procedure 6.5. To Restore Red Hat Satellite from Backup needs to include incremental restore instructions
Summary: Procedure 6.5. To Restore Red Hat Satellite from Backup needs to include incr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Server Administration Guide
Version: 6.2.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: Stephen Wadeley
QA Contact: Brandi Munilla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 12:16 UTC by Ian Tewksbury
Modified: 2019-09-25 20:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-01 21:21:55 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1369288 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1369288

Description Ian Tewksbury 2016-10-19 12:16:20 UTC
Document URL: 

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/server-administration-guide/#sect-Red_Hat_Satellite-Server_Administration_Guide-Backup_and_Disaster_Recovery-Restoring_Red_Hat_Satellite_Server_from_a_Backup

Section Number and Name: 

Procedure 6.5. To Restore Red Hat Satellite from Backup

Describe the issue: 

This section is missing instructions to restore from an incremental backup as outlined in the upstream katello documentation http://www.katello.org/docs/3.2/user_guide/backup/ (Incremental restore)

Suggestions for improvement: 

Add a section as part of 6.5 for doing incremental restore vs full restore.

Additional information:

Comment 2 Stephen Wadeley 2016-10-19 12:33:18 UTC
Hello


Thank you for raising this bug.


Note that some improvements were also requested in BZ#1369288

Comment 3 Ian Tewksbury 2016-10-19 12:58:17 UTC
Stephen,

I see BZ#1369288 has the following as part of it's suggestions

> Also there should be section mentioning restore of incremental backup.

If this is already being taken care of by the existing BZ feel free to dup this one or if you all want to track separately that works for me to. So long as it get's updated.

Comment 4 Stephen Wadeley 2016-10-21 08:10:52 UTC
Hello Ian


I decided not to close this as a dup as I wanted to publish the essential technical corrections, called for in BZ#1386667, ASAP before I go on one weeks PTO (later today), and then ask for your review.

I have just published the updates and BZ#1386667 is now closed. If you could review the updated section for me over the coming week that would be great. It could still be made more detailed by adding more command examples if you think that is best.


Thank you

Comment 5 Ian Tewksbury 2016-10-21 11:43:34 UTC
Hi Stephen,

For me the addition of "Where incremental backups exist, restore the last known good full backup first, then restore the incremental backups in the same sequence that they were made." at the end of the larger paragraph get's lost.

I personally think the styling on the Katello docs is much easier to read and use.
http://www.katello.org/docs/3.2/user_guide/backup/

If I am looking to restore an incremental backup I am looking for a section header labeled, incremental restore. Especially because the Satellite documentation already has a specific section for incremental backup "Procedure 6.3. To Perform an Incremental Backup".

I think It would be good to break it out into two different sections and have the examples like Katello does. That is far easier to find, read, and follow.

Thank you for your support on this and enjoy the PTO.

Comment 6 Stephen Wadeley 2016-10-31 09:26:26 UTC
Thank you Ian for comment 5

Comment 13 Stephen Wadeley 2016-11-01 21:21:55 UTC
Hello

These changes are now live one the customer portal.

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/server-administration-guide/62-restoring-red-hat-satellite-server-from-a-backup

Thank you


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