[DOCS-9700] Manual restore of sharded cluster using Ops Manager snapshots docs missing critical steps and notes Created: 27/Dec/16  Updated: 06/Mar/17  Resolved: 01/Mar/17

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Critical - P2
Reporter: Tomer Yakir Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.opsmanager.mongodb.com/current/tutorial/restore-sharded-cluster/


Participants:
Days since reply: 7 years, 7 weeks, 1 day ago
Epic Link: C/OM Backup

 Description   

The current docs are missing the following steps and notes:
1. When starting the primary, need to use --setParameter=recoverShardingState=false and remove the admin\system.version document (see server documentation on how to restore from filesystem snapshots)
2. When starting the secondaries, need to use the same parameter
3. The entire cluster has to be shut down and automation suspended from Ops Manager GUI
4. Missing instructions on how to use the original data directories (so it'll be possible to keep using the same Ops Manager deployment)
5. Missing note about needing to issue resync to backup after restore is complete
6. Missing note about needing to keep the original replica set member order to be able to get it back to automation

See HELP-3149 for reference


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