AWS Backup Reviews & Insights

Short-term retention backups for Production, Development, and UAT are used for backups that do not require long-term monthly archiving.

Because it is a native AWS service, it integrates well with all AWS services. However, it lacks the ability to manage long-term archive backups.

In line with other backup solutions for the cloud (from third parties), we have used AWS Backup as a PoC for multiple web application servers.

Well suited for DR scenarios, especially in scenarios with multiple applications web servers are required to be backed up.

The whole organization uses AWS Backup to ensure our important files are kept safe. It [has] saved my butt a few times with a few poorly chosen delete commands. Our cloud providers offers a backup solution but they don't guarantee the location of the data. A fire at their data center could result in the loss of our data, so we chose AWS for our offsite solution.

We also suffered a complete loss of data at our cloud providers and despite their best attempts to get the files back, we had to rely on our backups at AWS to get our services back up and running.

We've also implemented AWS [Backup] for a few of our customers looking for offsite backups.

There is a cost involved with data retrieval. AWS Backup is truly that, a backup. If you need to access this data on a regular basis, there are better options out there.

For long term, just in case incremental backups, AWS [Backup] checks all the boxes. Just set it up, start your backups, and rest assured your data is safe.

AWS Backup is used as the main backup solution for the core of our system (which is based on AWS infrastructure). AWS Backup is used mainly to back up our servers--and some important data--on regularly scheduled backups. This solution enables us to centralize and automate the backup of all of our AWS services (EBS volumes, EFS file systems, and databases).

Backing up your AWS infrastructure and services can be simplified by using AWS Backup, as it provides features to support multiple services. The backup plans can be defined using JSON files (not straightforward) and you can use tags to identify the resources that you need to back up. The main advantage is that all the backups are in one place and that you can see your backup status using AWS Backup dashboard.

We used AWS [Backup] as a backup for each server we have. Our data retention policies are fairly strong, and we keep about 3 months of backups in our services. AWS [Backup] was always some of the fastest and most efficient storage I've ever received. We were able to store lots and lots of backups with no problems. Never had an issue uploading either.

AWS [Backup] does what it intends on doing. AWS [Backup] is very fast, however, for that speed, you'll end up with a high bill at the end of the month. Compared to competitors, AWS [Backup] is a lot more expensive than others. However, I believe it makes it up in it's versatility - there's no company more compatible with others than AWS.

Basically we use AWS Backup to complete the cycle of lifetime backups, and also for centraliz[ing] those backups in one place. In first place we used just AMI backups, but when AWS release this service was amazing for us, because we can tag all resource that we want backup for.

AWS Backup is being used by my project as a method to make regularly scheduled backups of data from various services. It is being used just by the project at this point but it addresses the business problem of disaster recovery and having the capability to restore data that was deleted by accident that may be critical or customer facing.

AWS Backup is great for data backup because it solves a lot of data integrity and disaster recovery issues as a centralized backup tool on the Amazon platform. This is really only good if you use AWS as your main infrastructure organization. It is less appropriate in cases where you have data from other systems not covered by AWS.

We use AWS Backup to simplify backup tasks of all our workloads in AWS.

Backing up cloud workloads can be simplified by using AWS Backup as it provides features to support multiple services. Backup plans can be defined easily by json files and it's great to use tags to identify the resources to be backed up. The dashboard helps a lot with information to audit backup and restore activity.

It was primarily being used as our DB backups across the whole organization. We had daily backups as well as rollups of weekly and monthly backups. We could pull application state at any one of those given times.

Any scenario where you need to make backups, this is the product for you. It beats the use of old tape drives.

We use AWS Backup for hot backups to store our clients' active projects so they have an active cloud based NAS for their most important doc, emails, and creative projects.

When dealing with all three types of cloud back ups - AWS is almost the only provider where you can get deep freeze, cold and hot cloud storage from only one provider and have them all integrated between one another. Also they have a large list of third party integrations for programs like CloudBerry and the like to make it even easier.