-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Tutorial copy db #79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tutorial copy db #79
Conversation
available, the copy database commands are faster as there are no | ||
intermediate files to be created. | ||
|
||
.. warning:: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is really a note.
destination server. | ||
|
||
- :dbcommand:`copydb` or :dbcommand:`clone` do not work with a sharded | ||
database, such as a database a from :term:`shard cluster`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are no sharded databases except those in a shard cluster.
I think you're trying to say. "you can use these commands with unsharded databases in a shard cluster when you're connected directly to the mongod," but in that case, we should be explicit about this fact, rather than oblique.
:dbcommand:`copydb` and :dbcommand:`clone` do not produce | ||
point-in-time snapshots of the source database. Write traffic to | ||
the source database during the copy process may result in databases | ||
with different contents. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
write operations to the destination could also theoretically affect the contents of the result database.
I'm making final edits to this before I merge things in. Additional comments are for your own edification. |
:dbcommand:`copydb`. | ||
|
||
This is useful when you want to move a database from the development | ||
environment to the production environment, or create a remote-branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is not something that happens or that will seem reasonable to users.
The reverse may happen, where you might seed development servers using a portion of production data. You may also migrate data into production from a staging environment which isn't the same. and also is much more likely to pass through your application rather than go directly using these commands.
* DOCSP-23928 Fixes relevant limitations * DOCSP-23928 Fix per Lingzhi * DOCSP-23928 Fixes per Ashley
* DOCSP-24967-viewsAsCollections-update * DOCSP-24967-viewsAsCollections-update * DOCSP-24967-viewsAsCollections-update * DOCSP-24967-viewsAsCollections-update * DOCSP-24967-viewsAsCollections-update * DOCSP-24967-viewsAsCollections-update * DOCSP-24967-viewsAsCollections-update * DOCSP-24967-viewsAsCollections-update * DOCSP-24967-viewsAsCollections-update * DOCSP-24967-viewsAsCollections-update Co-authored-by: jason-price-mongodb <[email protected]>
* (DOCSP-13189): Remove deprecated CRUD commands (DOCSP-13189): Remove deprecated CRUD commands * Updates per copy review
DOCSP-36256 Fix Glossary Warning
DOCSP-29066 Add Help Menu Context to UI Page
…-AWS) (#79) * DOCSP-13158: add connection section
Updated the note on what a deprecated version means.
No description provided.