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

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

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.

My clients use AWS Backup to back up EC2 instances.

The use case for AWS Backup is the same as Azure. The only difference is the customer's choice and preference.

AWS Backup is primarily meant for customers with workloads on AWS or using cloud-native applications. This is the most common use case, accounting for about 70% of users.

It is also a good solution for customers with a hybrid on-premises environment and highly scalable data. Traditional storage solutions, such as Spectrum Protect, can be difficult to scale down dynamically. With AWS Backup, customers pay as per their consumption, so they only pay for what they use.

Another advantage of AWS Backup is that customers can choose the storage tiering for their data. They can store different types of data for different lengths, depending on how often it is accessed and how quickly it needs to be retrieved. This can help customers to save money on their storage costs.

We deal with confidential client information and use AWS Backup for our KYC solution. We capture the identity details of the end customer and ensure they are securely backed up.

Use cases include the solution's use for typical backup, restore, and disaster recovery. So, AWS Backup provides a solid service as a disaster recovery solution.

We use the product to schedule data backup, restoration, and encryption. It helps with real-time data recovery.

We only use the product for backups. We propose it to some clients. 

We use the solution for disaster recovery features.

AWS is the primary platform that we use for our internal needs and we are trying to best use whatever comes with it. So far, we are happy with AWS and we have 30% or 40% of our workflows implemented there. For example, we are very big SAP users and we use SAP HANA on AWS. In the future, we expected almost everything to be in AWS, with perhaps 10% of our work in Azure.

We use the AWS Backup as a service to perform native backups and recovery of files and other data. It is also our disaster recovery solution.

We are a solution provider and we use AWS Backup for our customers' companies.

We typically install this product on-premises, although it is easy to extend as a center in the cloud. Many our of customers are multi-cloud, using cloud provides such as Azure, AWS, and Google.

We use AWS backup for the VMware environment.

We use it for server backup, which is done weekly.

I'm also using AWS for QuickSight. It's been about four months since I'm using it for some statistical analysis. I'm still on that project, which is also AWS.

Our primary use case for AWS Backup is for SAP systems, including all of HANA databases.

We use the solution for backing up the data of our business applications.

We primarily use the solution as a backup for snapshots so that the data will not get corrupt or lost. It secures our data for us.

We are services vendor for AWS and this is one of the solutions that we implement for our clients. A project that I recently worked on involved a storage gateway and AWS Backup was used for backing up snapshots.

We have implemented AWS Backup for our clients. WS Backup has been used for disaster recovery plans.

We bought it as a service and deployed it. We use it to define each of our instances that we back up like the backup policy and the retention policy.