Veeam offsite cloud backup12/23/2023 ![]() ![]() AWS, Azure and Google all offer commit programs to a predetermined annual expenditure that results in contractual discounts on consumed resources, similar to an enterprise agreement. This holds true for not only the data protection software used for protecting cloud, but the cloud resources themselves. Much like anything you buy these days, the more you purchase, the better the price per unit. It also breaks down the total cost into subcomponents like snapshots, backups, replicas, archives, traffic and API calls, so if tweaks do need to be made, you’re already in the right place to make those changes. ![]() Veeam’s solutions for AWS, Azure and Google Cloud all come with proactive backup cost calculators built directly into the policy wizard to help you get an understanding of what that policy is likely to cost you monthly, which helps avoid bill shock. One area where this can become a little muddy, however, is with backup. Cloud providers are incredibly transparent about their pricing and often strive to help you drive the best value for your business. There are a lot of resources out there to help you understand cloud costs based on your business needs, such as the AWS Pricing Calculator and Azure Pricing Calculator. A true backup can be made from these snapshots, compressed, and then stored on more cost-effective object storage to meet compliance, retention and budgetary requirements. However, from a cost lens, you can see above that the volumes snapshots are stored on are among the most expensive cloud storage options. Snapshots afford us the ability to achieve low RPOs as they can be taken frequently, as well as low RTOs to overcome data loss scenarios quickly. Native snapshots are typically the go-to method for protecting cloud-hosted resources, whether they are manually created and managed, scripted, or orchestrated with another tool. Azure and Google follow a very similar model, and understanding the pros and cons of these storage classes is critical to cloud cost optimization. The visual representation below gives a general comparison of AWS list prices for common storage types used in backup based on pay-as-you-go, per-GB, per-month rates in us-east-1, accurate as of Aug. But not all storage options are created equal, with varying performance and cost needing to be balanced based on the criticality of data, how long it needs to be retained, and how old the data is. ![]() Perhaps the most obvious resource consumption for cloud backup is storage. So, what are some best practices when it comes to cloud backup to meet required service level agreements (SLAs) like RTOs, RPOs and retention while realizing cloud savings, whether you’re an end user or service provider? Planning Cost-Effective Cloud Storage Options So, when it comes to cloud backup, what are some best practices to meet required service-level agreements (SLAs) like RTOs, RPOs and retention without breaking the bank? Strategies for Cloud Backup Cost Optimization Other vendors are more transparent, with licensing fees only entitling licensing, and with storage, compute and data transfers billed separately based on their exact usage. Sometimes vendors will combine all the above into one, irrespective of how many resources you consume, representing savings for some and additional costs for others. Cloud backup consumes varying degrees of compute, storage, and data transfer resources, not to mention the licensing involved with the backup tool itself. To achieve cloud cost savings, it is critical to better understand the transition from typical CAPEX models to the pay-for-what-you-use OPEX models of the cloud. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |