AWS Backup is a great service, but I think there could be improvements on the reporting and dashboard side. More visibility into backup-related costs would be beneficial because I am very FinOps-minded. Stronger automated recovery testing capabilities and enhanced governance features for larger, multi-account, and multi-regional environments would make AWS Backup even more valuable for enterprise-scale operations.
AWS Backup could be improved by adding better visibility and reporting features. A more detailed dashboard is required for this service. Another improvement would be faster restore times for large data sets, which is really required and most important. Improved alerting and notifications are also needed so that users receive correct alerts on time. Troubleshooting failed backups can take time, and this could also be addressed.
I would need to get feedback from my colleague to see what additional features I would like to see in AWS Backup in the next release to make it closer to ten.
Regarding disadvantages of AWS Backup, it can be expensive and not particularly user-friendly. To perform backups, we need to follow specific steps and queries. When refreshing, if we want to do daily backups, it becomes quite costly. Weekly backups are more feasible from a cost perspective.
The time it takes to complete the backups could be reduced. If the backups can be more seamless and without impacting server performance, it would be greatly appreciated.
There are some limitations to partial backup in AWS Backup. If we have five volumes attached to EC2 and want to take backup for only three volumes and skip two volumes, it is not feasible in AWS Backup.
Hybrid cloud capabilities could be improved. AWS does have solutions, but it's probably not the best when you have both on-premise data center and Cloud. Unless you bring in AWS Outpost or other AWS solutions, configuring or leveraging AWS backup is not easy. If it's completely Cloud, then it's great. If you've Cloud and on-prem. Then, you have to bring in another AWS product or utility to leverage backup from your on-premise data center.
Director at AM Equipment & Services Private Limited
Real User
Sep 28, 2023
If AWS could also add some hybrid cloud features to AWS Backup, that would be a significant improvement. For example, currently, AWS Backup only backs up to the S3 and Amazon Cloud, and you can only restore from the Amazon Cloud only. However, some people have hybrid environments. They have some workloads on-premises and some workloads in the cloud. So if AWS Backup could work in a way where we could back up on-premises to the Amazon Cloud, and then if something goes wrong on-premises, we could restore it in the cloud and make it work there, that would be a valuable feature. So, a hybrid cloud flow feature would be beneficial.
AWS Backup is an AWS service that's not fully mature and needs to grow. It doesn't give us many options. AWS Backup doesn't have many features, and it's complicated. The solution's reporting features and restore features can be improved. The solution's backup schedule time should be improved because it does not start at the scheduled time. So, it's not a fully matured backup product. AWS Backup should include multiple restoring options.
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.
Senior IT Specialist Network and Security at a marketing services firm with 201-500 employees
Real User
Top 20
Jul 5, 2023
They should work on their visual capabilities. We have to restore the entire stack. We can only restore particular files on particular days. I hope they can help to release storage and instead of a specific file, we can access the entire stack.
I haven't thought about what needs improvement in the solution since it is a comprehensive solution for services related to backup and restoration. I think the solution could be optimized further to make it capable of providing an easier user experience. To create a plan and for all the configuration, one has to do multiple steps, which could be organized in a much simpler way, making the user experience better. In the future release, the solution should be able to provide its users with some notification when a backup is about to expire.
We're not really looking into areas of improvement right now. We do deployments and migrations and hand them over to the client. It's the client's responsibility to manage everything after that. It could be less expensive.
Technical Account Manager - Cloud Native at Maticmind S.p.A.
Real User
Aug 31, 2022
The restore functionality is an area that needs to be improved because right now, it is not very good. It requires a lot of time to connect the snapshot, identify the files, and restore a single file manually. In general, I would like to better manage the granular restoration of files. This is true both in a Linux environment, as well as Windows. A lot of our clients are using Linux for their application servers. We want to be able to restore either single files or multiple files from one volume. Today, it is very complex because it requires us to restore the full image of the volume. Only after that, can we extract a single file. Ideally, we should be able to extract a single file from a snapshot.
The AWS Backup backend reporting is a major area that needs improvement. We would be very excited if we can see some reporting, such as trends. We do understand that there are reports available for S3 Bucket, in which the AWS backend stores the data. However, if we can receive holistic reporting, then it would be very helpful for us.
Solutions Architect at a tech services company with 1,001-5,000 employees
Real User
Apr 23, 2020
If AWS Backup were a hybrid solution that also supported on-premises backups then it would be very helpful, especially if you are doing a migration to the cloud. Ideally, I would like to take an AWS snapshot, move it to a storage vault, and then migrate it to the cloud. That would be a nice strategy and it would mean that I don't need to use two different backup approaches.
Head of Cloud COE at a non-tech company with 10,001+ employees
Real User
Jan 22, 2020
One of the limitations of AWS Backup is that it only does file-based copying. It is not as good as some of the external products for handling things like the Oracle Database backups. For example, it lacks the ability to do database backups and differential backups. It is doesn't keep a schedule, and it doesn't keep full track of success and failure. Overall, the functionality is pretty limited, although it does meet our requirements. For places that have deeper requirements, they use different software to do their backups. In the future, I would like AWS Backup to be more robust and be able to handle database-level backups. It should support Oracle, MySQL, and other types of databases. Better integration with standard backup management tools that provide control, such as the ability to schedule backups, would be an improvement.
The notifications on the backup and on the mobile app could be more useful. If they could arrange notes or notifications properly and offer services for managing it in our region, it would be helpful for us.
AWS Backup provides centralized management of backups with automated scheduling and cross-region support. It ensures easy restoration and policy-based automation for error reduction while integrating seamlessly with AWS services for efficient data management.AWS Backup is a cloud-native solution offering a unified platform for managing backups across different AWS services. It supports lifecycle policies, point-in-time recovery, and security vaults. The service is cost-effective with a...
AWS Backup is a great service, but I think there could be improvements on the reporting and dashboard side. More visibility into backup-related costs would be beneficial because I am very FinOps-minded. Stronger automated recovery testing capabilities and enhanced governance features for larger, multi-account, and multi-regional environments would make AWS Backup even more valuable for enterprise-scale operations.
AWS Backup could be improved by adding better visibility and reporting features. A more detailed dashboard is required for this service. Another improvement would be faster restore times for large data sets, which is really required and most important. Improved alerting and notifications are also needed so that users receive correct alerts on time. Troubleshooting failed backups can take time, and this could also be addressed.
I would need to get feedback from my colleague to see what additional features I would like to see in AWS Backup in the next release to make it closer to ten.
Regarding disadvantages of AWS Backup, it can be expensive and not particularly user-friendly. To perform backups, we need to follow specific steps and queries. When refreshing, if we want to do daily backups, it becomes quite costly. Weekly backups are more feasible from a cost perspective.
There are multiple enhancements needed in terms of compatibility with all database services, as AWS Backup is currently limited to specific ones.
The time it takes to complete the backups could be reduced. If the backups can be more seamless and without impacting server performance, it would be greatly appreciated.
There are some limitations to partial backup in AWS Backup. If we have five volumes attached to EC2 and want to take backup for only three volumes and skip two volumes, it is not feasible in AWS Backup.
There could be a centralized dashboard with a reporting feature notifying us of daily backup status.
Hybrid cloud capabilities could be improved. AWS does have solutions, but it's probably not the best when you have both on-premise data center and Cloud. Unless you bring in AWS Outpost or other AWS solutions, configuring or leveraging AWS backup is not easy. If it's completely Cloud, then it's great. If you've Cloud and on-prem. Then, you have to bring in another AWS product or utility to leverage backup from your on-premise data center.
If AWS could also add some hybrid cloud features to AWS Backup, that would be a significant improvement. For example, currently, AWS Backup only backs up to the S3 and Amazon Cloud, and you can only restore from the Amazon Cloud only. However, some people have hybrid environments. They have some workloads on-premises and some workloads in the cloud. So if AWS Backup could work in a way where we could back up on-premises to the Amazon Cloud, and then if something goes wrong on-premises, we could restore it in the cloud and make it work there, that would be a valuable feature. So, a hybrid cloud flow feature would be beneficial.
AWS Backup is an AWS service that's not fully mature and needs to grow. It doesn't give us many options. AWS Backup doesn't have many features, and it's complicated. The solution's reporting features and restore features can be improved. The solution's backup schedule time should be improved because it does not start at the scheduled time. So, it's not a fully matured backup product. AWS Backup should include multiple restoring options.
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.
They should work on their visual capabilities. We have to restore the entire stack. We can only restore particular files on particular days. I hope they can help to release storage and instead of a specific file, we can access the entire stack.
The solution's price could be better than a few other vendors.
I haven't thought about what needs improvement in the solution since it is a comprehensive solution for services related to backup and restoration. I think the solution could be optimized further to make it capable of providing an easier user experience. To create a plan and for all the configuration, one has to do multiple steps, which could be organized in a much simpler way, making the user experience better. In the future release, the solution should be able to provide its users with some notification when a backup is about to expire.
They should improve the installation process. Presently, it requires a bit of customization to implement it.
We're not really looking into areas of improvement right now. We do deployments and migrations and hand them over to the client. It's the client's responsibility to manage everything after that. It could be less expensive.
The restore functionality is an area that needs to be improved because right now, it is not very good. It requires a lot of time to connect the snapshot, identify the files, and restore a single file manually. In general, I would like to better manage the granular restoration of files. This is true both in a Linux environment, as well as Windows. A lot of our clients are using Linux for their application servers. We want to be able to restore either single files or multiple files from one volume. Today, it is very complex because it requires us to restore the full image of the volume. Only after that, can we extract a single file. Ideally, we should be able to extract a single file from a snapshot.
AWS Backup could improve because you cannot use Glacier for anything but EFS.
The AWS Backup backend reporting is a major area that needs improvement. We would be very excited if we can see some reporting, such as trends. We do understand that there are reports available for S3 Bucket, in which the AWS backend stores the data. However, if we can receive holistic reporting, then it would be very helpful for us.
Only the price could be improved.
This backup tool does the full backup of the entire snapshot server. I would like to have the option to not do the full server backup.
If AWS Backup were a hybrid solution that also supported on-premises backups then it would be very helpful, especially if you are doing a migration to the cloud. Ideally, I would like to take an AWS snapshot, move it to a storage vault, and then migrate it to the cloud. That would be a nice strategy and it would mean that I don't need to use two different backup approaches.
One of the limitations of AWS Backup is that it only does file-based copying. It is not as good as some of the external products for handling things like the Oracle Database backups. For example, it lacks the ability to do database backups and differential backups. It is doesn't keep a schedule, and it doesn't keep full track of success and failure. Overall, the functionality is pretty limited, although it does meet our requirements. For places that have deeper requirements, they use different software to do their backups. In the future, I would like AWS Backup to be more robust and be able to handle database-level backups. It should support Oracle, MySQL, and other types of databases. Better integration with standard backup management tools that provide control, such as the ability to schedule backups, would be an improvement.
The notifications on the backup and on the mobile app could be more useful. If they could arrange notes or notifications properly and offer services for managing it in our region, it would be helpful for us.