Hi Tom,
I have been in touch with the WPvivid team about this feature addition, and along with our dev team, we provided updates that were required to move forward.
However, please note that this feature is very complex, even though it looks like it’s not.
Let me try to explain.
First, the Dashboard site sends requests to execute Updates on child sites. At this point, the WPvivi plugin needs to hook in before updates are executed and run the Backup process. So far, this is good. However, there has to be set a “lock” on the Update process so updates are on Hold while the backup is running and send feedback to Dashboard so users know that the backup is running. Also, now it’s not possible to anticipate how long the backup will take time, so the update process needs to wait until WPvivid plugin does not complete the Backup process and “unlock” the Updates process. After the backup is done, if the case of success, WPvivid needs to unlock the Update process so it continues; in case of failure, it needs to send feedback back to MainWP Dashboard so the user knows that the backup failed and it needs to abort the Update process.
All this requires a lot of work and changes in both systems, so we are both working on making this happen while trying not to jeopardize the functionality of both plugins.
Both teams is working on this and moving as fast as we can.