On Thu, Jun 5, 2014 at 7:32 PM, Nate Finch wrote:
> I guess what I don't understand is, why does it matter which mongo DB you
> back up? They should all be identical, right?
>
Replication lag is a real thing, and shouldn't be discounted. We want to be
sure that the backup corresponds to a point
I guess what I don't understand is, why does it matter which mongo DB you
back up? They should all be identical, right?
On Thu, Jun 5, 2014 at 12:58 PM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:
> On Wed, Jun 4, 2014 at 4:36 PM, Nate Finch
> wrote:
> > I'm not sure I understand the
On Wed, Jun 4, 2014 at 4:36 PM, Nate Finch wrote:
> I'm not sure I understand the distinction, Curtis. Backing up the state
> data in an HA environment
This test exists to verify a feature we decided to support
http://juju-ci.vapour.ws:8080/job/functional-ha-backup-restore-devel/
"Verify tha
I'm not sure I understand the distinction, Curtis. Backing up the state
data in an HA environment is what I was talking about for large
environments.
On Wed, Jun 4, 2014 at 4:12 PM, Curtis Hovey-Canonical wrote:
> On Wed, Jun 4, 2014 at 3:58 PM, Nate Finch
> wrote:
> ...
> > Then the only cas
On Wed, Jun 4, 2014 at 3:58 PM, Nate Finch wrote:
...
> Then the only case that is really a problem is large environments which are
> not using HA, which should be something we discourage, and uninterrupted
> backup can be a way to show the benefits of HA.
There is one other scenario. A backup a
