-
Type:
Improvement
-
Resolution: Done
-
Priority:
Blocker - P1
-
Affects Version/s: None
-
Component/s: Cloud Manager
-
Labels:
-
Environment:
*Location*: http://mms.mongodb.com/help-hosted/v1.4/tutorial/restore-from-snapshot/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.137 Safari/537.36
*Referrer*: http://mms.mongodb.com/help-hosted/v1.4/tutorial/restore-from-point-in-time-snapshot/
*Screen Resolution*: 1440 x 900
*repo*: REPONAME
*source*: tutorial/restore-from-snapshot
*Location*: http://mms.mongodb.com/help-hosted/v1.4/tutorial/restore-from-snapshot/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.137 Safari/537.36 *Referrer*: http://mms.mongodb.com/help-hosted/v1.4/tutorial/restore-from-point-in-time-snapshot/ *Screen Resolution*: 1440 x 900 *repo*: REPONAME *source*: tutorial/restore-from-snapshot
There needs to be a paragraph here about restoring an entire replicaset or a whole cluster. The procedure should indeed be trivial (simply perform the below steps for each individual server), but customers typically don't assume that it's so easy and don't know what to do.
Suggested wording: "When restoring a replica set, make sure all replicas are stopped, then copy the restore image to the dbpath directories of all replicas, then start the replicas up again. For a sharded cluster, stop the whole cluster, then copy the appropriate restore images to all the shards (replicasets) and to all the config servers, respectively. Then start the cluster again."
- duplicates
-
-
- Closed
-