>A stack is spawned from a database backup and once it passes tests, replaces the previous one. I like this approach, although risky if you mean you routinely

>A stack is spawned from a database backup and once it passes tests, replaces the previous one. I like this approach, although risky if you mean you routinely replace the production db. My preferred setup is to automate restores into a pre-prod environment, apply data masking and run tests there. It's not a replacement for full DR exercises, but at least it automates the backup verification process as part of your build system.