Skip to content
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

MongoDB backups support. #23

Closed
mrrooijen opened this issue Jul 14, 2010 · 12 comments
Closed

MongoDB backups support. #23

mrrooijen opened this issue Jul 14, 2010 · 12 comments

Comments

@mrrooijen
Copy link
Contributor

This would be nice for all our MongoDB fans out there. ; )

@RedBeard0531
Copy link

FYI here is some info on recommended ways to do backups in mongodb: http://www.mongodb.org/display/DOCS/Backups

If you have any questions, don't hesitate to get in touch.

@boblmartens
Copy link

Looks like mongodump might be the best option just to get something going.

@mrrooijen
Copy link
Contributor Author

I agree. I've been busy with a project a while back and mongodump is actually a very simple utility to get this done. I'll see if I can find the time to look at this.

@skippy
Copy link
Contributor

skippy commented Sep 19, 2010

I'm working on this now and will have a patch shortly (in the next 2-5 days). FYI

@mrrooijen
Copy link
Contributor Author

Woah mate! That's AWESOME. I am merging your changes as we speak and will release all the stuff I have up until now that was in .pre as a full release.

Take your time on MongoDB, whenever you're ready let me know and I'll add it and release a new gem as that is a huge addition! Thanks again for your work! :)

@skippy
Copy link
Contributor

skippy commented Sep 20, 2010

np! I needed it. I'll have some stuff checked into my branch here shortly

http://github.com/skippy/backup/tree/mongo

it was simple to add mongo (not finished yet, but getting there!), however, I needed the ability to add streaming ability for s3. The s3 gem doesn't support streaming, which means it loads everything into memory. I wasn't trying very large files but I can't spare 3gb of ram every time I need to do a backup. So I converted to aws-s3. The good thing is that because of the code structure it was very easy to do. But let me know if this is ok... if you were attached to the s3 gem for a particular reason, just let me know?

@mrrooijen
Copy link
Contributor Author

Sounds good! The thing is, we used to use the aws-s3 gem but it did not support EEUU/European buckets. There was need for that by particular Backup users so we made the switch to the s3 gem simply to accomplish that.

However, storing everything that it's going t send in memory is crazy, and aws-s3 is the only gem that supports this? Any idea if AWS-S3 now supports buckets, other than the US only?

Thanks again m8!

@skippy
Copy link
Contributor

skippy commented Sep 20, 2010

good to know! I'll take a look and check it out.

@skippy
Copy link
Contributor

skippy commented Sep 21, 2010

I fixed this and it is in my mongo branch (which isn't ready). I moved over to fog, which a few people recommended to me; it is fast, streams, simple, and it supports regions. so far so good.

@mrrooijen
Copy link
Contributor Author

Oh! I heard about this one a while ago! It's supposed to be like a single interface for various cloud servers right?

That might be even better to use instead of 2 separate gems (s3 and cloudfiles)?

Then we could also implement it for the Cloud Files storage method.

But hey that sounds super good man, thanks for that, that'd once again be a great addition!

@skippy
Copy link
Contributor

skippy commented Sep 22, 2010

it can be used for cloudfiles, though I haven't converted that over (as I don't use that service). do you want me to go ahead and do the optional gem change that is in issue #39 or should we leave that for later?

@mrrooijen
Copy link
Contributor Author

We can leave it for later. First get the S3 thing working I'd say :)

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants