In case of a mount failure, the actual redundancy in your system will be reduced accordingly. In the meantime, binaries continue to be written to the remaining active mounts. Once the malfunctioning mount has been restored, the system needs to rebalance the binaries written to the remaining active mounts to fully restore (i.e. balance) the redundancy configured in the system. Depending on how long the failed mount was inactive, this may involve a significant volume of binaries that now need to be written to the restored mount, which may take a significant amount of time. Since restoring the full redundancy is a resource-intensive operation, the balancing operation is run in a series of distinct sessions until complete. These are automatically invoked after a Garbage Collection process has been run in the system.