Bug 1125046

Summary:	Disaster Recovery for Capsule Satellite Server
Product:	Red Hat Satellite	Reporter:	Athene Chan <achan>
Component:	Docs User Guide	Assignee:	David O'Brien <daobrien>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Unspecified	CC:	andrew.schofield, bkearney, daobrien, greartes, mmccune, mmurray, xdmoon
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-06-22 01:22:22 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:
Bug Depends On:
Bug Blocks:	1115190, 1179535, 1425213
Deadline:	2015-04-03

Description Athene Chan 2014-07-31 00:25:16 UTC

From bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1123883

DR / Recovery. How do you DR a satellite server? What if a capsule blows up? - Can you DR these? How do you rebuild one and have the clients restore their connections without intervention.

After consultation with the developer team, I have moved this chunk of request out of the original bug as this can only be addressed in 6.1.

Comment 1 RHEL Program Management 2014-07-31 00:33:51 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 3 Athene Chan 2014-07-31 02:53:03 UTC

Hello Andrew,

I am adding you to the cc list as this section of your request for documentation will have to be addressed in a future release of the Red Hat Satellite 6 books. Keeping you in cc will help us update you when we've tackled this issue.

Cheers,
Athene

Comment 6 Athene Chan 2014-09-19 00:47:42 UTC

*** Bug 1136576 has been marked as a duplicate of this bug. ***

Comment 13 RHEL Program Management 2015-04-21 16:11:02 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.