HPE Zerto Software Reviews

Zerto allow us to to replicate our critical application servers with a sub 5 min RPO. Before Zerto we would restore from tape backup. 

Also, the testing recovery in an isolated environment allows us to test recovery any time we need to.

I would like to have automated load balancing of the ZVM's at the target site. Each ESX server needs to have  ZVM system to replicate the VM's. At the target site if you need to take one of the ZVM's offline at the target site you need to manually change the VM's using the ZVM. I would like this to be automated. 

ZVR is very simple to setup and administer. Out of the box it just works and allows me to set my replication source and destinations and nearly forget it. Our RPOs are generally 5 seconds on a replicated base of 4Tb so we have only a very small data loss in the event of needing to recover.

Now that v4.5 has been released, I have the ability to recover individual files in the event of accidental deletion or even encryption by Ransomware. This ensures that data is easily recovered no matter when it is deleted, ensuring that files that have been created and deleted in the same day and prior to backup are recoverable easily.

And, perhaps more importantly, out of the box ZVR allows me to test the failover whenever I want to verify that my systems can come up as expected.

I have been a user of Zerto Virtual Replication for 1 year.

Technical Support at ZVR is very good. Any calls are promptly responded to and dealt with to resolution. The support personnel are very knowledgeable on the product.

Initial setup is very straight forward. You simply create a group and populate your machines into the group, select a destination and voila ZVR does the rest.

Replication for disaster recovery between data centers is valuable.

Zerto allows us to replicate entire systems between data centers instead of setting up replication within the applications, which sometimes is non-existent.

The backup capabilities require too much disk space and I would like to see better compression. or deduplication built in to reduce the amount of WAN traffic. It would also be nice to have it be able to monitor a VM to let you know how much bandwidth a particular VM would require to replicate.

I've been using it for nine months.

We have had no issues with the deployment.

There have been no performance issues.

Scalability is all about bandwidth, so the only issue we had was trying to guess how much bandwidth we would need.

Technical support is good.

We used point solutions for our disaster recovery needs and we were very selective about the applications we would setup with disaster recovery due to costs.

The Zerto setup is very easy. The difficult task is setting up any processes that need to be run after a failover.

This was all setup in house.

The two key features for AssureStor are hypervisor based replication and the automation for failover, testing and failback.

As a cloud service provider we are always looking at how we can reduce risk for our customers, the ability to provide a DR service that delivers RPO’s typically as low as 15 seconds, over relatively slow connections is fantastic. And as the replication is performed at the hypervisor level we can protect any virtual (VMware or Hyper-V) environment without worry about the storage layer. The automation element is also a crucial element as it ensures we do not have to spend lots of man hours in the event of a DR failover request, as well as streamlining the ability to test the DR environment without needing any down-time of the production environment. And finally add in the ability to automatically reverse replication once you have failed over allowing you to re-seed the production site and failback with minimal downtime and you have a great all-round DR solution.

Before we took on Zerto our DRaaS offering was based on snapshot based backup’s with an automated restore process to our cloud hypervisors. This was a good service but we could only offer RPO’s as low as 1 hour and even then this was subject to caveats specifically around the size of the VM and how quickly we could ship the new data to our cloud platform. In addition, testing was much more cumbersome and meant a much higher number of hours had to be invested in every DR test, ultimately raising our costs. With Zerto in place we are now offering commercially sound services to small and large businesses without the worry of needing to invest in large numbers of staff to manage and perform testing, etc.

Backup capability as it is limited and not as streamlined as it could be. At present Zerto delivers backup protection by making duplicate copies of VM disks to a defined storage location (but this is limited on the schedule and retention). In the latest version 4.5 this has now been extended with the capability to do object level recovery from the replicated VMs, the caveat here is that the retention period is limited to the journal retention (which is a maximum of 14 days). I would like to see a more integrated backup/retention capability in the solution allowing more flexible scheduling and unlimited retention with the capability to easily restore objects using the one Zerto web interface. The backup images should be able to be stored off-site, away from the main replication site, and easily be reintegrated in the main DR platform if needed for VM recovery of an old image.

I've been using it for 18 months. v4.5 for the last four weeks, and prior to that we ran v4.0 since our initial deployment.

When we first deployed Zerto we didn’t understand some of the limitations around the built-in database (it uses SQLite). Whilst this would normally be fine for most small to medium deployments (the database is supported for up to 100 protected VMs and 4 sites), as a cloud provider we needed to have greater scalability. This is provided by using a full deployment of Microsoft SQL, thankfully Zerto have a tool that will migrate the SQLite DB into your Microsoft SQL server so the transfer is pain free, but I would make sure that anyone who is deploying in an environment that may have more than 100 VMs to deploy initially on Microsoft SQL. Another area to be aware of in scalability is not with Zerto itself but the demands it can put on the DR storage environment, you will be replicating all your VM disk writes as well as journaling and potentially adding more demand when testing (as the Zerto continues to replicate even when testing, which is great, but does hammer the storage).

We've had no issues with the performance.

It's been able to scale for our needs.

In one word, fantastic. When we evaluate a product one of the key areas we look at is the level of technical support we will get from the vendor. Bottom line IT systems have a habit of going wrong (one of the reasons I have had a job for the past 20 years), so once you accept that no system will be error-free, you need to know that if you do need help its available. We have had issues, bugs and questions and in every case we have been supported by the Zerto tech support team.

Our DRaaS platform, prior to Zerto, was an extension of our Asigra Cloud Backup platform. Whilst this worked it could not deliver the low RPOs we now see with Zerto nor the efficiencies we see from Zerto in managing day-to-day tasks on the platform such as validation, failover tests (and on the odd occasions actual live failovers). Our choice with Zerto was based on our own piece of mind, we protect a variety of end-users so never failing them (i.e. never failing to replicate their VMs and know we can spin them up when needed) was crucial, Zerto has delivered this for us.

Our deployment was fairly complex, but then we had to deploy a platform capable of multi-tenant support with complex networking and integration with vCloud Director so that customers could access their DR systems via a secure web interface. If you are deploying a site-to-site solution then deployment is very straightforward. Each site requires a Zerto Virtual Manager (ZVM) which is deployed upon Windows, this will then integrate with your vCenter servers at each site. From here it’s a few button clicks to deploy the Virtual Replication Appliance/s (VRAs) which are small Linux systems bound to each host that handle the ‘smart’ features of Zerto Replication, linking the site and your off.

Deployment was performed using in-house resources. The most important bit of advice I can offer to anyone considering implementing Zerto is understand your storage requirements at the production site and then decide on what levels of performance are acceptable. If you want to have low RPOs (seconds) then remember that you will be replicating all of your production writes into the DR storage device. And as initially these writes are put into the journal datastore and then read out after the defined retention period and written to the actual storage datastore be careful not to overload your DR SAN. As an example we deploy using separate SANs for journals and customer storage, with larger customers getting dedicated storage designed to accommodate their traffic patterns.

As a Zerto Cloud Service Provider (CSP) our licence model is different to end-users who can purchase the licence on a perpetual basis. For us the ROI was under 6 months, but we already had a large portion of the hypervisor and storage environment needed so were able to keep our costs to a minimum.

Zerto, in my opinion, is one of the best DR products on the market currently, its only flaw (if it can be called that) is that it is limited to virtual environments, specifically VMware & Hyper-V (it does also support replication to AWS if needed). If you are looking to streamline your DR capability and remove risk then speak to Zerto and get them to run you through a demo, what they say the product can do is not sales talk, it really can do it.

Zerto Dashboard

Failover Wizard

Recovery Checkpoints (Journal)

HW agnostic, no impact on production systems, no snapshot, easy management.

Version 4.0 is revolutionary, allowing replication between VMware, Hyper-V and AWS - conversion on the fly, and a a HTML5 GUI

Version 4.5 allows file restore, access based on roles, more powerful APIs.

We dismissed SRM and we no longer need the NetApp replication license. We were able to offer a DRaaS multitenant environment integrated with vCloud Director. Our customers think this tool is awesome.

Backup dedup and online restore, support for SMTP authentication.

4 years

Just in case of strict permission, we needed several ports to be opened. English language of OS for ZVM is needed, otherwise there's a bug showing some of the graphs.

Sometimes in large environments - enough to restart the service in ZVM.

No because it scales with ESXi scale.This is a strong pro.

Very very great, reactive answers in minutes and they don't leave you until the issue is resolved.

Great too - If the first level is unable to solve the issue, it scales to higher-level engineers on the fly.

SRM, but it needeed replication and it was complex to manage.

Smooth and Zerto techs assisted.

It was direct.

We only got SP licensing prices/model.

No, we had to decide if leaving SRM or not. Choice was simple.

There are other competitor on the market, but this is the only one dedicated to DR. All others are backup based. It could seems expensive, but when you realize its power, you'll understand that cost is justified.

• Replication from Hyper-V to ESX so I can retire my old environment
• Failover from Site A to Site B

Before this product, we had a lot of custom scripting and multiple other products to try and get to a similar place that Zerto allows without fully managing to. Zerto allows for a more granular replication ability and therefore a more flexible model than the per-socket licensed alternatives. It is positioned fantastically for pay as you grow which is just what we were after.

• IP Addressing of failed over VM’s isn’t working properly.
• Over time, it would be great to get more meat on the bones in the backups side of the product.
• Ability to add hard disks to a VM and have Zerto just pick up those changes rather than perform a full re-mirror.

There are many post migration activities associated with a Hyper-V to ESX migration – don’t presume this is a hands off activity as it very much isn’t at this time.  To make it hands off, there would be a ton of custom scripting required.

There have been no issues with the stability.

It has not been an issue to scale it for our needs.

The product has significant promise but it’s a long way from fully functional, there are fantastic features in the product and fantastic features promised “in the next release” too. Make sure you run through a good sizing exercise first.

• Interoperability between Hyper-V, ESX, vCloud, and AWS.
• Very easy to use
• Reliable
• Fast
• Also the architecture (on the ISP side) is designed with isolation and multi-tenancy in mind, so it's safely deployable on an ISP environment.

It allows smooth migrations which would be a lot more difficult with other technologies.

• A "manual mode" which would allow the user to failover the VMs but keeping them powered off at destination

• More powerful scripting engine

• Ability to move protected VMs between VPGs
• More reliable ETA on VPG syncronization
• root-level user for VRA installation ( at the moment the user "root" is hardcoded )
• Bandwidth throttling schedule should include days of week

I've used it for four months.

Not at all.

There were no issues.

There were no issues.

Great pre-sales experience, and good support.

8/10.

It was pretty straightforward.

I love the application, and it has become essential in my work.

Being able to provide customers with DR options that work.

We are a Cloud Services provider that owns and operates data centers coast-to-coast.

Couple of years

no

no

Only slightly when using it to protect 37 SQL servers. The high IOPS have been dealt with and we have solved that issue.

excellent

excellent

We used many other solutions, but this is the one we reached for first.

Yes - super simple.

When you can't afford to risk your data, Zerto is the solution.