Doing incremental backups against a node consumes resources to track blocks that have changed since the last backup. In the interest of safety, we will expose a command that can turn off the storage of incremental history (as an alternative to restarting the node).

The backup application is still in complete control of which nodes are keeping incremental history. This ticket will not introduce a MongoDB "timeout" that turns off incremental history.