[DOCS-11630] Audit `Seed with Mongorestore` tutorial and use Command Line Tools instructions Created: 17/Apr/18  Updated: 29/Oct/23  Resolved: 03/May/18

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

Type: Bug Priority: Critical - P2
Reporter: Andrew Davidson Assignee: Ravind Kumar (Inactive)
Resolution: Fixed Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

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

 Description   

Description

The `Seed with mongorestore` tutorial requires the user to assemble the commands to run. Furthermore, as noted by andrew.davidson the procedure itself may be incorrect.

Make the following changes:

  • Use Command Line tools tab to assemble the `mongorestore` command. Point it at the created dump file.
    • Direct users to whitelist the host they are using to run `mongorestore`.
    • Test whether `--nsExclude` is still required.
  • Connect and confirm the data has transferred.
  • Cut over applications to the Atlas cluster. Use the connect dialog instructions.

Scope of changes (files that need work and how much)

Audit and re-write `/import/mongorestore` (M)

Impact to other docs outside of this product

N/A

MVP (work and date?)

Fix by 2018-04-20

Resources (e.g. Scope Docs, Invision)

N/A

Original

I filed in our report a problem feedback box but then it asked me to file in JIRA.. not sure where that went.

Under "Using --uri:" we are missing the --archive params for both mongodump and mongorestore meaning this command will not work as written as far as I'm aware.



 Comments   
Comment by Ravind Kumar (Inactive) [ 03/May/18 ]

Published

Comment by Ravind Kumar (Inactive) [ 03/May/18 ]

merged

Comment by Ravind Kumar (Inactive) [ 17/Apr/18 ]

andrew.davidson see my comment above. Is there an advantage to piping over just creating the dump file and restoring it? This procedure requires downtime anyways if they want a full-copy that doesn't leave anything behind.

Comment by Ravind Kumar (Inactive) [ 17/Apr/18 ]

andrew.davidson - looking at this tutorial, there are a number of issues. To summarize what I would like to do:

1) Refocus this as a downtime-required tutorial
2) Use `mongodump` to create a dump file (e.g. using `-archive` or `-gzip`
3) Whitelist the host in the target Atlas cluster
4) Use `mongorestore` via command line tools tab
5) Cut over applications using connect dialog

Any objections to walking away from the piping procedure? this procedure would require downtime anyways, and if the goal is to transfer everything w/o leaving writes behind, then this feels more unpredictable.

Generated at Thu Feb 08 08:03:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.