Bug 1322573

Summary: Document replacing a failed brick and peer with volume snapshots
Product: [Community] Gluster-Documentation Reporter: Ben Werthmann <ben>
Component: OtherAssignee: Anjana Suparna Sriram <asriram>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecified   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ben Werthmann 2016-03-30 18:57:13 UTC 
Description of problem:

Please document the recovery procedure for volumes which have volume snapshots. We're testing recovery from a complete server failure where the storage (brick) and compute (peer) have failed. 

Please remove the guess work from this case. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Ben Werthmann 2016-03-31 17:36:41 UTC 
Digging around on the web, I found this page which discusses this recovery scenario, but the link is dead. 
http://www.gluster.org/community/documentation/index.php/Gluster_3.4:_Brick_Restoration_-_Replace_Crashed_Server

Deadlink:
http://community.gluster.org/q/a-replica-node-has-failed-completely-and-must-be-replaced-with-new-empty-hardware-how-do-i-add-the-new-hardware-and-bricks-back-into-the-replica-pair-and-begin-the-healing-process/