We performed a comparison between N2WS Backup & Recovery and Zerto based on real PeerSpot user reviews.
Find out in this report how the two Disaster Recovery (DR) Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The backup and restore functionality is very easy to use and manage."
"The product is successful with the SMB market."
"The recovery time is fantastic and proven. Also, by providing a simple interface, the solution lowers the cost."
"The backup and recovery are the most valuable features. So, our developers can work with confidence."
"The most valuable feature is the ease of use."
"N2WS Backup & Recovery is very easy to use and configure backup for AWS instances."
"The initial setup is easy."
"Provides easy, one-click functionality and flexible backup policies and schedules for AWS workloads."
"It reduced the time for DR tests from the infrastructure side. Being able to get our work done in a matter of a couple of minutes so the app teams can get to work and can do their testing has been significant."
"There are a lot of valuable features. The basics of what it does to replicate and recover things within minutes is awesome. It's far above anything that any of the competition has. We offer other disaster recovery software but primarily use Zerto for recovery times and the number of recovery points because of how fast and easy it is. It's so much better."
"Stable disaster recovery solution with a very simple setup and fast failover."
"Our RPOs and RTOs are now more in line with our other critical systems."
"When we use our VMware environment, sometimes the HP hardware is not compatible, and we start to lose data. I like that we can restore our whole application and public-facing system through Zerto."
"The communication between the VM and the secondary data center is the most valuable feature."
"Live replication and up to the second type of failover are valuable. The fact that we can do test failovers and failbacks is important for our ISO certification."
"Some of the most valuable features are the synchronous replication and migration with RDMs. I really like the conversion of RDM VMs for migration."
"The GUI has room for improvement."
"More documentation would be helpful, especially some step-by-step documents for recovery scenarios."
"It's a global feature that the customer thinks they don't have enough tools to manage, to copy, to delay, and to classify the object file in the backup directory. So they need more tools to manage files in object directory."
"The UI is a little dated and hard to use. Some of the buttons are a bit small. You have to go into the menu to get the settings you want."
"Additional features I would like to see are the ability to restore to different vendors, AWS and Azure, and/or the ability or take the information out of the AWS cloud."
"The GUI could be slightly improved."
"The solution has the option to take backup on-prem servers, but it's not very efficient."
"There is room for improvement in stability."
"Certain areas were designed and work fine for VMware but are under development for Hyper-V. Eventually, all features will work for both platforms."
"The full site recovery is not up to SRM standards."
"They could iron out the licensing aspect of it, so we might be a bit quicker when implementing and starting to use it."
"For special situations, there are options within advanced settings. You don't have to dig too far for them, but they're not quite as straightforward."
"There's one feature that SRM had that Zerto doesn't have, and it's one that we've been asking for. With the orchestration part of the failover, with our DR and our primary sites, the IP addresses are almost identical. The only difference is one octet. With SRM, we could say during a failover change. With Zerto, we keep hearing that it's coming, but we haven't received it yet. It's a feature that would be very beneficial. It would reduce the time a little bit more."
"Some of the features need improvement. One would be, as you're creating a Move group or a VPG, as they call it, it should either autosave or have the ability so that you can save it for coming back to later because if the setup times out, you lose all your work. That would be a nice improvement to have."
"The overall management plan could improve. If something happens with the VM on the vSphere side, the error codes are pretty weak. If there was a way to click on something within the UI that takes us to a support page or article, that would be very beneficial."
"From the relationship standpoint, we have never had a local rep in South Bend, Indiana. It has always been somebody in Boston, and there is not a lot of communication. That is one of the big things. We would like help driving the business and talking to our sales people as well as more involvement from them. We could really utilize it more, drawing more customers in, but we need help with that."
N2WS Backup & Recovery is ranked 18th in Disaster Recovery (DR) Software with 8 reviews while Zerto is ranked 2nd in Disaster Recovery (DR) Software with 236 reviews. N2WS Backup & Recovery is rated 8.8, while Zerto is rated 9.0. The top reviewer of N2WS Backup & Recovery writes "A highly stable and easy-to-use solution that can be used for backing up EC2 instances". On the other hand, the top reviewer of Zerto writes "Gives us business continuity capabilities during hurricane season and in case of ransomware". N2WS Backup & Recovery is most compared with Veeam Backup & Replication, AWS Backup and Rubrik, whereas Zerto is most compared with Veeam Backup & Replication, VMware SRM, Rubrik, Dell RecoverPoint for Virtual Machines and VMware Cloud Disaster Recovery. See our N2WS Backup & Recovery vs. Zerto report.
See our list of best Disaster Recovery (DR) Software vendors, best Backup and Recovery vendors, and best Cloud Backup vendors.
We monitor all Disaster Recovery (DR) Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
