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
Zerto
Score 9.1 out of 10
Enterprise companies (1,001+ employees)
Zerto, a Hewlett Packard Enterprise company, aims to enable customers to run an always-on business by simplifying the protection,
recovery, and mobility of on-premises and cloud applications. Zerto’s cloud
data management and protection platform is designed to eliminate the risks and complexity of
modernization and cloud adoption across private, public, and hybrid
deployments. The software-only platform uses continuous data protection
at scale to converge disaster recovery, backup, and data…
Zerto replicates at the hypervisor level, not the VM level like VMware Site Recovery Manager (SRM). SRM replicates vms within or across vSphere clusters, but not between different hypervisors. While I only replicate from vcenter to vcenter, if we needed to replicate to a …
Hands down Zerto blows VMware SRM out of the water. The configuration is easy to setup. Managing replications are just a few short key strokes and there is an easy-to-navigate web dashboard.
The speed of WAN replication is great. It is faster compared to RecoverPoint and 20 VMs replicating over a 20Mbps VPN, which has a RPO less than one minute. Of course, your mileage will vary.
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
Zerto is well suited for disaster recovery and virtual machine replication between multiple data centers. DR testing for audit or regulations is much easier with Zerto, great reporting, dashboard etc. It is not well suited for physical server replication for disaster recovery or as a primary backup solution.
Anyone with a large disk (VMDK) knows the issues of VMware snapshots. Most backup software is a "point in time backup" that uses snapshots. While the backup can be run multiple times per day the stress of the snapshot on the host and storage is eliminated by the continuous protection of Zerto log replication.
A client had a the disks on a VM go missing for some reason. We had them "flip the switch" for a real fail over and press the fail over button. The VM on our DR site started to come alive as the VM at the customer site was brought down. When the DR VM was fully up, automatic reverse replication started. The DR machine was available in a few minutes (to take into account different host hardware) for access. One the vm at both sites were in sync, we had the customer again repeat the fail over process and the DR site VM was turned off and the Production site VM was brought back on line. This was a 200 GB VM and the whole process was finished in about 3 hours.
Zerto also allows for "Test" fail overs that can be configured on many different functions, such as host, datastore, network and IP usage. Configuring the IPs is crucial to avoid inadvertent site cross contamination of the same VM.
Zerto can also retrieve files from any VM disk on the DR site without starting a VM. Very handy for retrieving files or directories.
Since Zerto is running continuous log replication, changes on the production VM are nearly instantaneously copied to the DR site. As with any data process, having sufficient bandwidth for "churn" peaks minimizes the delay in updating the DR site.
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.
We really like the easy setup of this replication solution, as well as the ease of management. Not to mention, our internal IT Economist determined that the Zerto solution would provide the best ROI out of the competing solutions we analyzed. So far, his calculations have been spot on, and we have saved substantially
Usability was the primary reason we purchased the software in the first place. We had compared it to several other software products in the same area, and it was by far the easiest to set up and use. Long-term maintenance proved to be similar, with updates driven by updates to VMware and vSphere, rather than the product itself.
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.
Overall support is very good. We sometimes get pushback when asking Level 1 support to escalate to Level 2. This causes undue frustrations when you need a more knowledgeable support person to get involved. We've had to escalate to account reps a few times for this scenario. Zerto is very responsive and normally handles our requests very quickly.
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.
We started out using Backup Exec which was in service until we virtualized our environment where it didn't perform as well at the time. Then we switched to Veeam which worked well, but then as we started needing to do migrations and off-site DR, we found ourselves relying on Zerto more often.
For my organization, the pricing model was an upfront investment for the Zerto licenses. My organization prefers to pay upfront and not deal with month-to-month or year-to-year pricing models that most companies are moving to. But for some, the investment may be more than they can afford, and would prefer the year-to-year pricing model.
I mean, it was 6 years ago, but we were up and going with all applications synchronizing in short order. The longest tasks was getting the 30 TB of application data synchronized between the datacenters.
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.
Zerto is like having the best possible insurance ... it just works, and often provides the backups taken overnight that are key in recovering data/work between overnight backups.
Zerto easily enabled the move of primary datacenters by allowing easy failover to a secondary site, and failback to the primary site.
