What is our primary use case?
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.
What is most valuable?
The most valuable feature is its ease of use.
What needs improvement?
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.
For how long have I used the solution?
We are been using AWS Backup for more than two years.
What do I think about the stability of the solution?
This is a stable solution.
What do I think about the scalability of the solution?
AWS Backup is scalable. It is used to back up environments and not really for end-users. In our internal IT departments, we have probably 50 people using it.
How are customer service and technical support?
We have reached out to AWS support and our technical architecture manager has a relationship with them. We provide constant feedback with respect to how the product is and what improvements need to be done. The developers are aware and they try to improve the features, but it's a slow process.
How was the initial setup?
The initial setup is very simple. There is not much to it. We just need to run some primitive scripts.
What other advice do I have?
The suitability of this solution for backup and recovery depends on the requirements. I would only recommend it for organizations that need a very simple solution.
There is a lot of work that they need to do in the backup space because, at this time, it only does very basic backups. They don't appear to be prioritizing the building of a robust backup solution. It seems that they are more interested in having us work with another vendor, rather than them creating something that is already available.
I would rate this solution a six out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)