Microsoft Azure is a cloud computing platform and infrastructure for building, deploying, and managing applications and services through a global network of Microsoft-managed datacenters.
$29
per month
VMware SRM
Score 9.0 out of 10
N/A
VMware's Site Recovery Manager (VMware SRM) is a disaster recovery option, used to automate orchestration of failover and failback to minimize downtime and improve availability with VMware Site Recovery Manager.
N/A
Pricing
Microsoft Azure
VMware Site Recovery Manager
Editions & Modules
Developer
$29
per month
Standard
$100
per month
Professional Direct
$1000
per month
Basic
Free
per month
No answers on this topic
Offerings
Pricing Offerings
Microsoft Azure
VMware SRM
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
The free tier lets users have access to a variety of services free for 12 months with limited usage after making an Azure account.
—
More Pricing Information
Community Pulse
Microsoft Azure
VMware Site Recovery Manager
Features
Microsoft Azure
VMware Site Recovery Manager
Infrastructure-as-a-Service (IaaS)
Comparison of Infrastructure-as-a-Service (IaaS) features of Product A and Product B
Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.
It's quite well suited for a medium to large size VMWare virtualization infrastructure where your production infrastructure can be failed over to a disaster recovery site. There are other cheaper options for a smaller budget business. Also, for a non mission critical virtual infrastructure, you can simply use VM backups such as Veeam backups for restoring failed VMs
Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.
The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
The documentation needs to be improved, and some advanced configuration options require research and experimentation.
Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.
It’s unfortunate, but more and more, the quality of VMware’s products and the technical support teams behind them has degraded significantly. We have opened several support requests within the last few months and ended up resolving a large majority ourselves due to the poor performance of their remote teams.
VMware is suffering from the same illness that’s affecting multiple U.S. technology firms, in that their focus has shifted completely away from their customers and moved to pleasing investors. In doing so, clients suffer because they do not get properly tested products and the support teams behind them are very weak and overwhelmed.
We worked close to a month trying to get SRM V6.5 to work. We have worked with many previous versions of SRM in the past while using HP EVAs, NetApps and Hitachi arrays, and we can honestly say that we are greatly disappointed with this release and the company.
We escalated right up to engineering, but their response times were brutally slow; the technicians were juniors at best.
As a technology leader, the last thing you want during a DR is to be dealing with a company that just can't deliver. SRM is not cheap, and you would expect much better products and support from VMware.
If you are comparing products, try other companies like Veeam... We ended up using them instead, the setup and execution was easy and seamless, and they answered all our questions quickly and efficiently. They actually do care about their clients.
Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.
As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.
We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!
Sometimes we have to struggle explaining the problem and getting it resolved on priority. The overall quality of support team is not as good as it used to be in past.
As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.
As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.
Entertained Veeam, however with SRM's tight integration and "brand" it was an easy decision. The cost for a 25 server license also weighed in the decision for using a VMware product. Plus I am a VMware fan and feel this option to go with SRM will transcend jobs.
For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.
The biggest positive is that we have a data recovery solution that we can test and verify in a live condition. Prior to this we were only hoping we could recover from a disaster.
We've been only running for 4 months and haven't had to use SRM.
