If I implemented a way (from the Panel) to nuke the most recent set
of backups then would that make the "suspend" option the best one as
the customer can still fix it themselves?
That is, upon receiving the critical alert that they had now used
more than 100% of backup space and their backups have been disabled,
they determine that this is because something large got backed up
that shouldn't have been backed up. They could then go to the Panel
and delete the most recent backup run, and then backups start
working again at the next run, all of this without needing to submit
support tickets and without being charged any extra.