[DOCS-3570] Comment on: "mongodb-ecosystem/tutorial/backup-and-restore-mongodb-on-amazon-ec2.txt" Created: 11/Jun/14  Updated: 11/Jan/17  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: ecosystem
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Minor - P4
Reporter: Greg Swallow Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://docs.mongodb.org/ecosystem/tutorial/backup-and-restore-mongodb-on-amazon-ec2/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36
Referrer: http://docs.mongodb.org/manual/search/?query=ec2%20backup
Screen Resolution: 2560 x 1600
repo: docs-ecosystem
source: tutorial/backup-and-restore-mongodb-on-amazon-ec2


Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

Reassembly of the RAID array with mdadm is different than what's described here.

First, if I need to be aware of the original UUIDs of the block devices, then it would be helpful to know – beforehand – that I need to create a tag called "original-uuid" or something on the EBS snapshot.

Second, I think I can just run mdadm --assemble --scan md0. But I haven't figured this out yet since I've always used hardware RAID. In any case the --auto-update-homehost (??) flag doesn't work.



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Generated at Thu Feb 08 07:46:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.