Details
-
Improvement
-
Resolution: Won't Fix
-
Minor - P4
-
None
-
*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
*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
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.