![]() Veeam Backup for Azure is very similar in look and feel to the AWS product, and I’d assume that much of the leg work for basic functionality can persist across all clouds. The stark reality is that AWS has the largest piece of the cloud pie, so it makes some sense to start there. Given Veeam’s historical partnership with Microsoft, it almost seems like the Azure v1 product could have preceded AWS. Interestingly enough, Veeam Backup and Replication had ties to Azure much earlier than it did to AWS. The more recent addition to its AWS counterpart is Veeam Backup for Azure v1. This allows you to make costing decisions in real time, rather than having to adjust based on monthly consumption charges. Veeam integrates with current AWS pricing to calculate the total cost of running a backup policy. One great feature of Veeam AWS v3 is the cost estimator. Stand alone licensing is also available per instance beyond the free edition. Veeam Backup for AWS is free for up to 10 instances, which makes it easy to PoC or possibly not require licensing at all if you have no more than 10 critical workloads to protect. There is also licensing to consider, and Veeam’s newer universal licensing option (VUL) brings portability across all Veeam products. This significant savings from a storage perspective may in many cases make up for the additional compute cost. From a storage perspective, regardless of backup type, all data is stored as Veeam objects within S3 at $0.023 GB / month (as of this posting). When running Veeam AWS v3, you will incur costs for the EC2 server running Veeam and worker instance compute time. There don’t appear to be any other costs associated other than your typical data transfer stuff and minimal cost for some restores. All of this can be done via a centralized dashboard in the AWS console, making it lightweight and easy consume, although limited in scope to strictly the AWS ecosystem.įrom a surface level cost perspective, AWS Backup can range from $0.05 GB data stored / month for EC2 to almost $0.10 GB data stored / month for RDS and DynamoDB ( US-East-1). It allows you to create backup plans, which basically say what is being backed up, when and with what retention. Like other AWS services, it is consumed directly from the AWS console, which natively integrates with the resources you want to protect. AWS Backup also supports EFS, DynamoDB, FSx, Aurora, Storage Gateway and RDS, but doesn’t currently have VPC backup functionality. With EC2 being fairly new, it isn’t quite as fully featured as its Veeam AWS v3 counterpart in that it isn’t capable of file level restores. AWS Backup is a relatively new-ish service that actually didn’t support EC2 backup until the beginning of 2020. Unsurprisingly, AWS has it’s own service that can protect data across a number of services. An interesting addition to this is VPC backup, which makes plenty of sense if you’ve ever had to comb through VPCs / Route Tables / Security Groups to see why something isn’t working properly. Both backup types draw from their VMware predecessor by utilizing API calls to AWS native snapshot services. That makes PaaS options such as RDS the next logical step. These worker instances only spin up and down as required, leaving a minimal consumption based pricing footprint.ĮC2 is the barrier to entry for cloud backup, but it is also the most “familiar” for organizations that are in the infancy of cloud adoption or operating in a hybrid model. Backup data processing is performed by worker instances, which replace your Veeam proxies and data movers used with on-prem VBR. Supported AWS services can be backed up directly to S3 buckets configured as a Veeam S3 Repository. As of the latest Veeam Backup and Replication v10a, AWS v3 can also be pushed out and managed from within VBR itself. Veeam Backup for AWS is available via the AWS Marketplace and is deployed as a separate EC2 instance. AWS v3 adds support for RDS and VPC backup, along with an EC2 enhancement of allowing file level restore to the original file location. The initial release of Veeam Backup for AWS focused on EC2 instances. Originally released at the end of 2019, Veeam for AWS v3 is now available from the AWS Marketplace. I spent time digging into these updates and contrasting them with their cloud native counterparts to find out where Veeam brings value for backing up your cloud data. Recent coverage from Tech Field Day 22 highlighted some of these updates. Just like many other enterprises, Veeam is realizing that their “ACT II” requires a pivot towards public cloud and modern consumption models. While Veeam may not have a ton of name recognition in the cloud native space, they built an extremely strong foundation within the world of data center virtualization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |