mongodump/mongorestore and oplog.bson

[Horacio Duran]

Well that file should only contain something if the db got changed while
you where performing the dump.
The usual test db is rather small and one usually is only doing the dump
during the test so this becomes a bit hard to achieve.
I really would hope the content of oplog.bson are somehow documented but
that can be naive of me.
Anyway, if you want to get one of those with contents you need to have a
large mongo that changes while you are dumping.


On Thu, Oct 30, 2014 at 11:45 AM, Eric Snow <eric.snow at canonical.com> wrote:

> When running mongodump with the --oplog, you end up getting an
> oplog.bson file dumped, along with a directory for each dumped
> database.  mongorestore likewise has an --oplog option, which
> presumably causes it to use that oplog.bson file.
>
> Who could tell me about that oplog.bson file?  In my testing for
> backups, it always comes up empty.  If I can always expect it to be
> empty then I'll be a happy camper.  Otherwise, what are the cases
> where it would not be empty and is there a safe way I could parse/edit
> oplog.bson in those cases?  My guess is that it will be non-empty when
> mongdump is run while mongo has actions queued up or when requests
> come in while mongodump is running.  Regardless, any insight here
> would be helpful.  Thanks!
>
> -eric
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20141030/a1f09117/attachment.html>