Skip to content

DOCS-1245: Improve backup strategy overview. #736

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

Closed
wants to merge 2 commits into from
Closed

DOCS-1245: Improve backup strategy overview. #736

wants to merge 2 commits into from

Conversation

michaeltwofish
Copy link
Contributor

Both filesystem snapshots and mongodump can be point in time. Clean
up the language. Leave the details that will help people make a
decision as to their best options in the linked detail pages. Put
the links in the same order we've talked about the options.

Both filesystem snapshots and mongodump can be point in time. Clean
up the language. Leave the details that will help people make a
decision as to their best options in the linked detail pages. Put
the links in the same order we've talked about the options.
@tychoish
Copy link
Contributor

Hi Michael,

I've been trying to touch base with you on IRC, but the time difference hasn't been kind to my efforts. Thanks so much for your work here. To get larger non-trivial patches like this merged in, we'll need you to sign the MongoDB/10gen contributor agreement, which is located here:

http://www.10gen.com/legal/contributor-agreement

I'll continue discussion of this patch here:

https://jira.mongodb.org/browse/DOCS-1245

Cheers,
sam

@michaeltwofish
Copy link
Contributor Author

Thanks, Sam, I've made a couple of efforts to catch you on IRC too, and I'll continue to do so. Is there a docs-specific channel?

I've signed the agreement and continued the patch discussion on the ticket.

@michaeltwofish
Copy link
Contributor Author

I don't think adding pull requests sends notifications, so I guess this is a polite bump. Please forgive me if you've already seen it and you're just busy, say, working on a release.

@tychoish
Copy link
Contributor

Thanks for the bump! I hadn't seen the revision, and I still need to get this in front of someone else just for sanity, but its definitely still on my radar.

@tychoish tychoish closed this Mar 20, 2013
@tychoish tychoish reopened this Mar 20, 2013
@tychoish
Copy link
Contributor

Just to keep you up to date, I've asked a couple of engineers who've worked on mongodump and backup strategies in the past to take a look at this, and I'll get back to you when I know more.

@kay-kim
Copy link
Contributor

kay-kim commented Jan 16, 2014

Hi Michael -- thanks for your time and patience with this. The backup strategy page has undergone significant rewrite, and as such, this pull request no longer applies. Apologies for the belated response, and thanks again for your time and efforts. Much appreciated.

@kay-kim kay-kim closed this Jan 16, 2014
mongo-cr-bot pushed a commit that referenced this pull request Feb 28, 2022
* DOCS-14442  operator limitation

* DOCS-14442 Fixes from internal review

* DOCS-14442 Refactor per Nic Feedback

* DOCS-14442 Refactor per Nic Feedback

* DOCS-14442 Refactor per Nic Feedback

* DOCS-14442 Refactor per Nic Feedback
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request May 22, 2025
(cherry picked from commit fbec731)
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants