Bug 1234985

Summary:	[doc] unclear storage location for backup
Product:	Red Hat Satellite	Reporter:	Fred van Zwieten <fvzwieten>
Component:	Docs User Guide	Assignee:	jsomers
Status:	CLOSED DUPLICATE	QA Contact:	David O'Brien <daobrien>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	adstrong, jsherril, melewis
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-06 14:32:04 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 Fred van Zwieten 2015-06-23 16:12:03 UTC

Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/User_Guide/index.html#sect-Red_Hat_Satellite-User_Guide-Configuring_a_Red_Hat_Satellite_Capsule_Server

Section Number and Name: 
18.1

Describe the issue: 
Step 1 warns that enough space must be available for the backup. But it fails to specify where. Also, is kattelo-backup able to specify a target location? Where is the online backup option? How to backup a capsule? Is it needed?

Suggestions for improvement: 
Describe the missing pieces

Additional information: 
Given the time a full backup takes, customer could opt for doing a online backup of the DB's and snapshot the filesystem for the pulp content (if the OS or hypervisor supports it).

Comment 1 RHEL Program Management 2015-06-23 16:25:26 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 2 Justin Sherrill 2015-07-01 20:40:34 UTC

So the docs say:


 Run the backup script:

# /usr/bin/katello-backup


However this is incorrect, it should be:

 Run the backup script:

# /usr/bin/katello-backup /path/to/backup/location

where /path/to/backup/location is a valid path and has enough space.

Comment 4 jsomers 2015-07-06 14:32:04 UTC


*** This bug has been marked as a duplicate of bug 1172415 ***