Bug 1547650 - Update backup section to say to encrypt or move somewhere secure
Summary: Update backup section to say to encrypt or move somewhere secure
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Server Administration Guide
Version: Nightly
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Melanie Corr
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-21 16:43 UTC by Chris Roberts
Modified: 2019-09-26 16:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-01 16:38:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chris Roberts 2018-02-21 16:43:01 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_Satellite_Server_or_Capsule_Server

Section Number and Name: 

5.1. Backing up Satellite Server or Capsule Server

Describe the issue: 

Currently, if the backup was compromised it could cause issues since there are hosts names in the dbs and ssh keys for foreman-proxy

Suggestions for improvement: 

Add a section about moving it to a secure place or encrypting it with a password.

Additional information:
Comment 1 Andrew Dahms 2018-02-21 21:47:36 UTC 
Assigning to Melanie for review.
Comment 8 Melanie Corr 2018-03-01 16:38:30 UTC 
These changes are now live on the Customer Portal

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html/administering_red_hat_satellite/chap-red_hat_satellite-administering_red_hat_satellite-backup_and_disaster_recovery
Note You need to log in before you can comment on or make changes to this bug.