More about AWS backup
Amazon Web Services (AWS) is used by many organizations to backup on-premise and cloud-based resources. AWS Backup is a new Amazon service that centrally manages backups across the enterprise, both for on-premise and cloud-based resources.
In this post, we’ll explain how AWS Backup works, its use cases and pricing, and show how NetApp Cloud Volumes ONTAP can help you optimize and improve AWS backups.
In this article, you will learn:
What is AWS Backup?
AWS backup has two common meanings:
- Backing up data for services running in the AWS cloud (cloud to cloud)
- Using AWS for backup and data archiving from on-premise resources (on-premise to cloud)
For years, AWS has offered tools for each of these scenarios. For example, you can automate EBS snapshots to backup local storage for an EC2 instance, or use AWS Storage Gateway to backup data from local storage devices to Amazon S3.
However, in 2019 Amazon took its backup offering one step further, launching a dedicated service named AWS Backup, which lets you automate and centrally manage backups across the enterprise.
AWS Backup Service ArchitectureSource: AWS
AWS Backup supports both of the scenarios above—it lets you backup data from Amazon EFS, DynamoDB, RDS or EBS, and also from on-premise resources via the AWS Storage Gateway.
AWS Backup doesn’t replace the previous backup technologies offered by AWS. It is a central management interface that brings those technologies together, letting you orchestrate and schedule backups easily in one place.
How Does the New AWS Backup Service Work?
AWS Backup is built around the following concepts:
- Backup rules—these rules define a backup, specifying a schedule, frequency, and backup window. A backup rule can be applied to specific resources, or to groups of resources defined by tags.
- Lifecycle rules—define what happens with old backups. For example, you can use lifecycle rules to move backups to cheaper storage tiers, or delete them completely, after a specified period of time.
- Vaults—backups are grouped into vaults, and each vault is encrypted by a Key Management Service (KMS) key.
AWS Backup lets you define a new backup using the AWS Console, or define one programmatically using a JSON file.
How to Define a Backup Using the AWS Console
Follow the process below to create a new backup plan.
1. In AWS, click Create Backup Plan and select Build a New Plan.
2. Select Create a new backup rule—below is an example of a backup that runs daily, moves data to cold storage after a month, and deletes it after 6 months.
Image Source: Amazon Web Services
3. Click Create Plan, and then view your plan and click Assign Resources to define what should be backed up using this rule. You need to define IAM roles to AWS Backup with access to each of the resources you would like to back up.
4. Select which resources you want to backup as part of the backup plan. Below is an example in which we backup an EFS folder, a DynamoDB table, an EBS volume, and all data resources defined by a tag value.
Image Source: Amazon Web Services
5. Go to the AWS Backup Dashboard and monitor your new backup job. You can see which backup jobs and restore jobs have been running and their status.
We only covered the most basic functionality of AWS Backup, see the official documentation for more details.
AWS Backup Use Cases
Below are a few common use cases for AWS Backup, and the underlying Amazon backup technologies it manages.
Hybrid Cloud Backup
You can use the AWS Storage Gateway to integrate local storage resources with the Amazon cloud. When you restore from backup, data is automatically copied from Amazon back to your on-premise storage devices. Data is stored in one of the Amazon S3 storage tiers, depending on how quickly or frequently you need to access the data.
AWS Backup lets you automate this process, creating a backup plan that defines a schedule and frequency for backups from on-premises storage to S3.
AWS lets you backup its cloud-based database services—Amazon RDS and DynamoDB, using their built-in backup capabilities. You can also backup self-hosted databases, running on Amazon EC2 instances and stored in EBS volumes, by automating EBS snapshots.
AWS Backup lets you automate all these backups in one place by defining one or more backup plans, and specifying the databases or group of databases you need to backup. You no longer have to define specific backup settings in RDS or DynamoDB, or schedule EBS snapshots—this is done automatically by AWS backup.
Data Lifecycle Management
Amazon S3 provides several storage tiers, which allow you to move data that is used less frequently to cost-effective cold storage. Within S3, you can configure lifecycle policies that automatically move data sets to a cheaper storage class, or delete them altogether, based on predefined criteria.
AWS Backup lets you do this centrally as part of a backup plan. When you define backups, you can specify what happens to your backups after several weeks, months or years—you can automatically define an S3 lifecycle policy to move the data to cold storage or delete it when it is no longer needed.
AWS Backup Pricing
AWS Backup is priced based on the storage space consumed by your backups. The first time you perform a backup of a data resource, you pay for the full storage space, but from the second backup onwards, you pay only for the storage space added since the last backup.
If you backup an AWS-based data resource, pricing is as follows (prices are for US East Region, and may change from time to time, see the official pricing page):
- Amazon EFS File System Backup—$0.05 per GB/month
- Amazon EBS Volume Snapshot or AWS Storage Gateway Volume Backup—$0.05 per GB/Month
- Amazon RDS Database Snapshot—$0.095 per GB/Month
- Amazon DynamoDB Table Backup—$0.10 per GB/Month
The above prices are for warm storage. AWS Backup only supports cold storage for Amazon EFS backups, at a significantly reduced price of $0.01 per GB/month.
Restoring backups is free for EBS, RDS, and Storage Gateway. The following services incur a cost for restoring backups (pricing is for US East Region and may change from time to time):
- Amazon EFS—$0.02 per GB for warm storage and $0.03 for cold storage.
- Amazon DynamoDB—$0.15 per GB
AWS Backup with Cloud Volumes ONTAP
NetApp Cloud Volumes ONTAP, the leading enterprise-grade storage management solution, delivers secure, proven storage management services on AWS, Azure and Google Cloud. Cloud Volumes ONTAP supports up to a capacity of 368TB, and supports various use cases such as file services, databases, DevOps or any other enterprise workload.
In particular, Cloud Volumes ONTAP provides data protection: NetApp Snapshot™ technology requires no additional storage and does not impact application performance. Combined with NetApp’s storage efficiencies, this can be a powerful, cost-effective addition to native AWS backup solutions.
Learn More About AWS Backup
AWS backup is a substantial expense and a major operational burden for many organizations. Read our additional articles below to learn how to control your costs, automate backups, and leverage NetApp technologies to execute hybrid cloud strategies and gain major storage efficiencies.
AWS Backup Pricing
AWS backup pricing is based on the amount of storage your backups use, and the volume of data you restore when needed.
Data storage is priced per GB-month for backup storage, with two storage tiers for backup data: warm storage and cold storage. In addition, Amazon charges per GB transferred out of storage, with prices depending on the transfer destination.
Learn about AWS Backup pricing and see examples of common pricing scenarios.
Read more: Understanding AWS Backup Pricing
Automating Your Disk Backup and Data Archive Part 1: AWS Database Backup with AWS Snapshots
AWS snapshots play an important role in data protection for many workloads, including AWS database backups. These snapshots can also be useful in a wide range of issues which include: creating development and testing environments; fixing corrupted data; solving user errors; and recovering from cyber attacks.
Whether your architecture is hybrid or cloud-only, there are different ways to ensure your AWS database backup is in place and recoverable. For example, you can use both file-based and snapshot-based backups and store backups redundantly across Regions and Availability Zones to maximize availability.
Learn about these and additional options to back up your databases on AWS.
Automating Disk Backup and Data Archiving with Cloud Volumes ONTAP
NetApp Cloud Volumes ONTAP works seamlessly with on-premises NetApp storage, making it easy to integrate cloud-based systems with on-premise systems. If the on-premises database uses iSCSI storage allocations from a NetApp system, you can perform instant, space-efficient application-consistent snapshots of a database of any size.
Cloud Volumes ONTAP snapshots created using SnapMirror® data replication. SnapMirror is NetApp’s enterprise data replication technology, which can rapidly synchronize large volumes of data for use cases such as disaster recovery and cloud migration. After the initial snapshot, SnapMirror only copied blocks that have changed, making it fast and efficient.
Learn how to use SnapMirror to improve database backup performance, reduce storage space and substantially save on backup costs.
Cloud Backup Services: NetApp’s Backup-as-a-Service for Cloud Volumes ONTAP
Backing up mission-critical data is a crucial step in protecting your cloud-based operations. Traditionally, this task was performed by storage admins using the native cloud backup services the major cloud providers offer. However, there is a new cloud backup service available that makes the backup process significantly easier and more efficient.
NetApp Cloud Backup Service, now available for use with Cloud Volumes ONTAP, brings NetApp’s impressive backup and restore capabilities to the hyperscaler cloud. Cloud Backup Service is incredibly easy to set up and is equipped with highly automated backup policies that determine backup frequency and retention period.
EBS to S3: Streamlining Data on AWS
While the cloud has revolutionized IT by making it possible to provision unlimited resources with the click of a button, but that facility can have its drawbacks too. What happens in enterprise-level deployments as data grows and resource usage increases over time, both for the primary deployment as well as for the AWS backup copies? The answer is a bill that gets higher and higher by the month. What can you do to limit these costs?
In this blog post, we introduce you to one solution: streamlining data from EBS to S3, where the costs of storage are much lower, especially for infrequently used backup copies.
Read more in EBS to S3: Streamlining Data on AWS