We checked 53,709 production resources for backups. 61% had none.
Disclosure: I work at Eon, on the content side. Our team ran these assessments and this is our data. I didn't write the queries, but I sat with the engineer who did, and the methodology below includes what we couldn't see. Argue with it. Most backup tools produce a coverage report, and most of those reports work from tags. They check the resources a policy already enrolled, which is usually…
A recent assessment by a team from Eon found that 61% of production resources in 78 cloud environments on AWS, Google Cloud, and Azure had no backup policy, no recovery point, and no native cloud snapshot. The assessment connected through a read-only role, discovered every resource, classified which ones were production, and checked each one for a recovery copy.
The findings show that 14% of AWS production resources had a production tag, 66% had no environment tag at all, 27% had no tags of any kind, and 19% had an environment tag containing something that isn't an environment. Of the 53,709 production resources, 61.2% had no backup policy, no recovery point, and no native cloud snapshot the assessment could detect.
The assessment also found that the median age of a production resource with no recovery copy is 502 days, while the median age of one with a recovery copy is 363 days. This suggests that the unprotected resources are not new ones, but rather an old resident population that nobody is watching.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
