If a backup falls in the forest and nobody is there to hear it, does it make a sound?
Backups are only as good as your last restore attempt.
Even AWS ran into this, when they accidentally zeroed out a service in one AZ and found that a combination of the dependency tree and timeouts had made it extremely challenging to spin a data center back up from zero. Instead of minutes it took hours and several false starts. It wasn’t stated but I suspect some of that has to do with the fact that if you’re spinning up a new AZ it contains no customers and no data, while spinning one back up needs to contend with retention and related event queues. Though they don’t actually spin up new AZs very often so what do I know.
If a backup falls in the forest and nobody is there to hear it, does it make a sound?
Backups are only as good as your last restore attempt.
Even AWS ran into this, when they accidentally zeroed out a service in one AZ and found that a combination of the dependency tree and timeouts had made it extremely challenging to spin a data center back up from zero. Instead of minutes it took hours and several false starts. It wasn’t stated but I suspect some of that has to do with the fact that if you’re spinning up a new AZ it contains no customers and no data, while spinning one back up needs to contend with retention and related event queues. Though they don’t actually spin up new AZs very often so what do I know.