Comment 11 for bug 1852502

It's fundamentally a race in how many changes happen while you are doing
the rest of the backup. If you can skip more of the actual content, then
the backup runs faster, giving less time for the data to overflow.

On Wed, May 19, 2021 at 10:30 AM Erlon R. Cruz <email address hidden>
wrote:

> > One plausible fix would be to have 'juju create-backup --no-logs", as
> they
> > aren't usually super relevant to restore and usually consume a
> > significant amount of data.
>
> So, that would only reduce the set of problematic collections as there are
> other collections known
> to fail (aka tnxs.log).
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1852502
>
> Title:
> Juju backups failing Executor error: CappedPositionLost:
> CollectionScan died due to position in capped collection being
> deleted.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1852502/+subscriptions
>