The product's performance is an area of concern where improvements are required. From an improvement perspective, the solution should provide ease of use to its users and try to be a complete solution to be able to act as a CDP replacement.
One area for improvement with Azure is helping customers predict usage more accurately. It would be great to have tools that provide clearer insights into how our costs might evolve over time. Like a budget forecast that considers potential fluctuations based on usage, helping avoid surprises.
The primary area for improvement in Azure Site Recovery is its pricing. While the service is efficient and successful in handling recovery scenarios, especially for large companies dealing with substantial monthly data, the costs can be a significant consideration. The ease and speed of ASR in recovery are commendable, but addressing the pricing aspect would enhance overall satisfaction.
I conveyed the feedback to the agent, suggesting an increase in the agent count in our VNS in the USA. I also addressed notification concerns, as some issues didn't trigger alerts during a recent call.
Team Lead , Enterprise Computing Platforms at a manufacturing company with 10,001+ employees
Real User
Top 5
2023-11-01T12:55:00Z
Nov 1, 2023
It would be good if we could replicate the solution to multiple locations simultaneously because we are currently allowed to replicate to just a single location.
Cloud Engineer at a university with 1,001-5,000 employees
Real User
Top 10
2022-12-16T17:41:31Z
Dec 16, 2022
It was easier to configure the server in the older version of Azure Site Recovery. Still, in the newest version, the configuration was a little more complex, so this is an area for improvement in the solution.
It is for site-to-site replication. When something goes wrong on your site, you only get 15 minutes before it also goes wrong on your replicated site. There should be some way to be able to say that we want to restore it, but we want to restore it to the version from yesterday. It should support versioning. I would also like to see real-time scanning for advanced threat protection, more straightforward billing, and quicker turnaround on the tech support.
Sr. Sales Solutions Architect at a tech services company with 10,001+ employees
Real User
2020-03-16T06:56:20Z
Mar 16, 2020
Improvement could be made on the pricing model. It could be brought in line with the competitive ranges in the market Additional features could include more of a backup and recovery. We'd like to see the AIX operating system added into it. It's more virtual right now.
Technical Director at a tech services company with 11-50 employees
Real User
2020-02-23T06:17:04Z
Feb 23, 2020
There have been issues with replication. It would be helpful if error logging was handled more effectively. When it runs, it runs well but when it doesn't run, the solution needs to make it clearer as to why and what the troubleshooting process is. All this would be possible if the error logging was streamlined a bit.
Disaster Recovery as a Service providers offer solutions that enable businesses to recover their IT infrastructure and data in the event of a disaster.
The product's performance is an area of concern where improvements are required. From an improvement perspective, the solution should provide ease of use to its users and try to be a complete solution to be able to act as a CDP replacement.
One area for improvement with Azure is helping customers predict usage more accurately. It would be great to have tools that provide clearer insights into how our costs might evolve over time. Like a budget forecast that considers potential fluctuations based on usage, helping avoid surprises.
The primary area for improvement in Azure Site Recovery is its pricing. While the service is efficient and successful in handling recovery scenarios, especially for large companies dealing with substantial monthly data, the costs can be a significant consideration. The ease and speed of ASR in recovery are commendable, but addressing the pricing aspect would enhance overall satisfaction.
I conveyed the feedback to the agent, suggesting an increase in the agent count in our VNS in the USA. I also addressed notification concerns, as some issues didn't trigger alerts during a recent call.
It would be good if we could replicate the solution to multiple locations simultaneously because we are currently allowed to replicate to just a single location.
The tool should improve synchronization.
I would like to see more security features.
I'd like to see more integration with other platforms.
Site Recovery could improve its communication of when new features are available.
It was easier to configure the server in the older version of Azure Site Recovery. Still, in the newest version, the configuration was a little more complex, so this is an area for improvement in the solution.
The immutable backup could be better and should be improved.
The pricing predictability and clarity around the final cost of the plan of this solution could be improved.
It is for site-to-site replication. When something goes wrong on your site, you only get 15 minutes before it also goes wrong on your replicated site. There should be some way to be able to say that we want to restore it, but we want to restore it to the version from yesterday. It should support versioning. I would also like to see real-time scanning for advanced threat protection, more straightforward billing, and quicker turnaround on the tech support.
We need to be able to move the virtual servers and not build and then port them across. They need to improve the hypervisor.
Improvement could be made on the pricing model. It could be brought in line with the competitive ranges in the market Additional features could include more of a backup and recovery. We'd like to see the AIX operating system added into it. It's more virtual right now.
There have been issues with replication. It would be helpful if error logging was handled more effectively. When it runs, it runs well but when it doesn't run, the solution needs to make it clearer as to why and what the troubleshooting process is. All this would be possible if the error logging was streamlined a bit.