Workarounds for using mongodump?

[Kostassoid]

We're trying to backup from replica set slave. The data should be
consistent so we tried these approaches:

1. Using --oplog param. Failed, because it creates(!) and tries to
backup '*' database. Really wtf, especially considering we can't even
drop it from slave just as easily.

2. Using db.fsyncLock() / db.fsyncUnlock(). Failed, because it hangs
after a few seconds of work.

3. Stopping slave node completely and using --dbpath param. Works, but
feels like overkill.

Is there something else we could try with the current version?

[Scott Hernandez]

On Fri, Jan 27, 2012 at 6:13 AM, Kostassoid <k.alex...@gmail.com> wrote:
> We're trying to backup from replica set slave. The data should be
> consistent so we tried these approaches:
>
> 1. Using --oplog param. Failed, because it creates(!) and tries to
> backup '*' database. Really wtf, especially considering we can't even
> drop it from slave just as easily.

There was a bug which allowed this, but has been fixed. What version
are you using? You can use newer version of the tools with old
servers.

> 2. Using db.fsyncLock() / db.fsyncUnlock(). Failed, because it hangs
> after a few seconds of work.

You cannot, and should not use mongodump with fsyncLock. Using
fsyncLock is for backing up the files, not using mongodump.

> 3. Stopping slave node completely and using --dbpath param. Works, but
> feels like overkill.

See above.

> Is there something else we could try with the current version?

See above.

> --
> You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> To post to this group, send email to mongod...@googlegroups.com.
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
>