Keeping Disaster Recovery Snapshots for Too Long: Avoiding Cloud Cost Sins


The promise of public cloud is the allure of decentralization and agility. But without proper methods to gain oversight and ensure optimization, chances are you may be succumbing to a variety of sins that are costing you time, money, efficiency, and governance.

We’ve recently posted our latest eBook, Avoiding the 7 Deadly Sins of Public Cloud Costs, looking at all the ways your public cloud costs can spiral to the depths but also best practices for pulling your enterprise back up.

This is the sixth in a weekly blog series examining each of the seven sins. This week we’ll look at Sin #6: Keeping Disaster Recovery Snapshots for Too Long.

Sin #6: Keeping Disaster Recovery Snapshots for Too Long

Things can go wrong anytime. It’s malpractice not to account for disaster, so taking disaster recovery (DR) snapshots, especially when using public cloud for the first time, is important. But, these DR snapshots can get outdated fast, and cost a boatload to maintain for no good reason.

Make a plan for how long you want to backup your snapshots. It doesn’t matter where the snapshots are backed up: they’re costing you. Make it a rule that anything older than a certain number of months should be deleted forever.

Cleanse Your Organization of Public Cloud Cost Sins

Looking to learn more about the six other deadly sins of public cloud costs? Download the eBook today. Also be sure to check out our comprehensive AWS Cost Optimization Guide for best practices on AWS costs.

Save 20% on Public Cloud Costs, or We’ll Give You $1,000. Guaranteed.

Related Blogs

VMWare Competitors: Exploring Migration Options after Broadcom’s Acquisition

As the saga of the recent $69 billion acquisition of VMware by Broadcom continues to play out, it has sent…

VMWare Alternatives – What’s Next For Your Cloud Practice

As a VMware partner, you may have received notice that Broadcom is terminating your contract.  It’s like the tech world’s…

Navigating the VMware Acquisition: A Pragmatic Approach to Migration in the Broadcom Era

Introduction: I received a text from a former colleague and friend out of the blue today that read “I guess…