[DOCS-7215] Comment on: "manual/tutorial/restore-sharded-cluster.txt" Created: 21/Feb/16  Updated: 30/Oct/23  Resolved: 27/Dec/18

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.org/v3.0/tutorial/restore-sharded-cluster/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36
Referrer: https://www.google.es/
Screen Resolution: 1600 x 900
repo: docs
source: tutorial/restore-sharded-cluster


Participants:
Days since reply: 5 years, 6 weeks, 6 days ago
Story Points: 0.2

 Description   

I've found somewhere else that the first db to be restored at the config server is the admin one. Is frustrating when the official documentation has such misses.



 Comments   
Comment by Ravind Kumar (Inactive) [ 27/Dec/18 ]

I don't believe providing the exact ordering would help much outside of users attempting to restore one database at a time to the mongod. Our standard backup/restore procedures for the CSRS are for the entire CSRS database, and that should remain the standard.

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