I mentioned before that this is the worst possible way to implement an option to disable backups. A client can simply delete the website container and create a new one, completely bypassing the restriction. At scale, with hundreds of websites, administrators have no way to detect that a client has done this.
A more robust implementation would be to define clear rules at the platform level, for example:
• Do not back up if website size or inode count is greater than X
• Do not back up if database size is greater than X
It is disappointing that this concern was raised earlier but does not appear to have been taken into consideration.
