Bug 1322573 - Document replacing a failed brick and peer with volume snapshots
Summary: Document replacing a failed brick and peer with volume snapshots
Keywords:
Status: NEW
Alias: None
Product: Gluster-Documentation
Classification: Community
Component: Other
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anjana Suparna Sriram
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-30 18:57 UTC by Ben Werthmann
Modified: 2023-01-04 04:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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/
Note You need to log in before you can comment on or make changes to this bug.