AWS Backup Reviews

As a consultant for Amazon Web Services, I manage backups of services such as EC2, RDS, and S3 using AWS Backup. These backups are done via a single platform, which simplifies the process.

The service makes it easy to manage a variety of backups under one platform, reducing complexity and avoiding the hassle of handling each backup service separately. In case of facing challenges, having everything centralized makes troubleshooting much easier.

Our primary use case for AWS Backup is for taking periodic backups of our production servers. We schedule these backups to ensure we have the latest snapshots of our servers in place.

In case of an outage, we are able to restore our servers from the backup. This ensures business continuity and data availability.

We use AWS Backup to protect the resource data in the Amazon cloud.

The solution's most valuable features are its backup capability and tight integration with other AWS services. Since AWS Backup is a managed service, we don't need to do much to manage the solution.

I use AWS Backup to take the backup of multiple databases, including DynamoDB and S3. 

AWS Backup has multiple plans based on the frequency I choose for each service.

Before AWS Backup, we used the native solutions for our databases, which required significant customization and operational overhead. 

AWS Backup has helped us eliminate those tedious tasks, automate the backup process, and reduce operational overhead.

My clients use AWS Backup to back up EC2 instances.

It's very easy to configure. Since it's a managed service, it's very straightforward to set up and use. And my customers get on with it very fast.

We use AWS Backup to protect our running workloads within AWS. We also use WAF, but my networking team handles it.

We use it regularly. Whenever there's a new workload, the RP and R team integrate backup based on our needs.

Reporting is one of the key elements that are valuable for C-suite executives. In terms of monitoring, the solution provides comprehensive details into ongoing processes, flagging issues and warnings as necessary. 

Another primary advantage is that we don't have to handle backup tools; it's a fully managed service. AWS takes care of the backup software, and we consume the service. This aspect of managed backup services is most beneficial.

We are using AWS Backup for 3-2-1 disaster recovery scenarios, records, and retention.

AWS Backup has helped out organization by overall increasing our disaster recovery capabilities. Additionally, it allowed us to support different disaster recovery scenarios.

AWS Backup's most valuable feature is that you can configure it remotely to create backups.

The service disconnects a lot. We configured AWS with VMware, and it's hard to configure because you have to configure the Black gateway and the gateway you connect to VMware. We didn't know what the issue with the gateway was. When we designed this and did the evaluation, we had to run a console application and console commands to verify the backup status, and it gave some errors that were hard to troubleshoot. This was one of the reasons we did not continue with it. Also, when you start, you don't know what's happening with the backups. You start the backup, and then you don't know the progress because there is no indication of where we have reached, like a progress bar. Likewise, there was no indication from the source that the backup was being processed. In the end, we got a notification "backup failed" as an error. We had to troubleshoot what the error was, and that was the main issue with AWS Backup.