Zerto Review

Instant data rollback, self-healing, and good reporting


What is our primary use case?

We use Zerto to protect our staff information against ransomware and is outlined in our disaster recovery plan. We have a DR site that we failover to if anything happens at our primary data center. We have only our core services, that we could not live without, being protected.

How has it helped my organization?

It is very easy to use. Almost anyone in our IT team can manage it after not using it for months at a time. As the DR strategist here, I like that. I enjoy having a fast way to bring a server back up. It will take me longer to get to my desk and log into everything than it will to actually complete the failover. 

What is most valuable?

I really like how you can test the failover as often as you need.

The reports it generates are very good at showing our protection state.

It is self-healing in case I mess up on something and need to re-sync. When you are protecting Terabytes of data, this comes in handy.

What needs improvement?

I think Zerto could do better with size planning because it would be nice to analyze a server for a week and give an estimate on sizing the Journal. I find myself estimating too high.

It would be nice if I had an option to dynamically restore to any host in a cluster. Right now, if we have multiple things happen and the main host is down it will not work. 

For how long have I used the solution?

I have been using this solution for three years.

What do I think about the scalability of the solution?

We are only using a fraction of what it can do. If you add the backup function it scales very largely. I could see a hospital really finding this product useful.

How are customer service and technical support?

My first experience with technical support was not good at all. In the last few years, it has improved quite a bit. 

If you previously used a different solution, which one did you use and why did you switch?

Prior to this solution, we used storage mirroring and DFS syncing. Our old way used far too much storage. Zerto compresses the data well. 

How was the initial setup?

The initial setup of this solution is very straightforward. We were making initial syncs in forty-five minutes. 

What about the implementation team?

We did both, with most over the phone. Their expertise was fine. I didn't in any way feel like I was not getting my questions answered. 

What was our ROI?

Our ROI happened in nine seconds.

What's my experience with pricing, setup cost, and licensing?

I don't remember it being cheap. We started out slow, which was a good call. We found that in an event that was massive enough to cause an entire cluster to go offline we would be happy with our core services up and running.

Which other solutions did I evaluate?

At the time, Zerto was the only product doing this so easily. It might still be.

What other advice do I have?

Don't underestimate how good it feels to rollback data instantly. It makes me look like a Wizzard at my desk. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email