RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 855321 - Create an explicit section about the disaster recovery procedures.
Summary: Create an explicit section about the disaster recovery procedures.
Keywords:
Status: CLOSED DUPLICATE of bug 814489
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-07 11:40 UTC by Dmitri Pal
Modified: 2013-06-26 21:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-26 21:27:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dmitri Pal 2012-09-07 11:40:32 UTC 
The disaster recover procedures are weak spot of IPA. We do not have replica backup and restore capabilities. So the special section should be created that talks about how to deal with disaster recovery scenarios.
It should include:

1) Recommended procedure of creating new replica instead of the old one and re-installing
2) Planning ahead and validating that replication agreements are actually properly created in the first place so that there will be no orphans if any server goes down
3) Explicitly state that there is currently no backup and restore procedure.

Please add more details as needed.
Comment 2 Deon Ballard 2013-06-26 21:27:09 UTC 

*** This bug has been marked as a duplicate of bug 814489 ***
Note You need to log in before you can comment on or make changes to this bug.