We performed a comparison between Unitrends and Zerto based on real PeerSpot user reviews.
Find out in this report how the two Backup and Recovery solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Iinstant recovery (allows a spin-up of your image as a VM on the appliance)."
"The ability to diversify jobs within the same server helps break down a large chunk of data into more manageable and concentrated chunks."
"The ability to back up both physical and virtual appliances under one roof."
"Replication to Forever Cloud."
"Unitrends has helped us cut down the time that it takes to restore a server to its original configuration."
"What I found most valuable in Unitrends is its simple user interface. It also works reliably."
"Stability-wise, I rate this solution a nine out of ten."
"The ability to backup both physical and virtual machines, along with having an appliance store the backups locally instead of on a file server, NAS, or SAN."
"I like that the failover is simple and that it's a stable platform. It makes it easy for us to do failovers in the event that we have an issue. It also makes it easier to do test failovers because we can test it prior to actually doing a real failover. This means that we can pull things back or commit them over on the other side. Zerto streamlines the process instead of having to have a whole team of people who are dedicated to disaster recovery."
"The return to operations is the most valuable feature because it decreases the amount of time it takes us to recover."
"It helps us keep our required retention period for specific documents and allows us to recover older documents if we have to compare and recreate those."
"You can set the number of days a VM can be rolled back in case of corruption or virus infection."
"It's very stable. It doesn't require a lot of intervention."
"Another big attraction is the near zero RPO. A lot of other products have minutes, half-hour, or an hour RPO. We have proof indicating that Zerto is near zero, or a matter of minutes, as far as the RTO is concerned. So again, that's another attractive offering where you can actually fail something over and bring that back up in a target location in a matter of minutes. Meaning very little data loss as far as recovery time. It's fantastic."
"Since the log files are continuously transmitted, the granularity of restores is amazing."
"Zerto is low maintenance, so I can set it and forget it. It has a great process and an excellent solution."
"Techs don't see to be well-versed in troubleshooting issues that arise and tickets stay opened for weeks for resolution."
"Support is great for small simple issues, but anything more difficult, it is hard to get good resolutions without having to badger them and their management."
"Unitrends can be challenging to scale."
"The solution’s support and onboarding process needs to be improved."
"In terms of improvement, the UI, especially in the recovery section, is unclear about which repository it uses."
"Comparing the features and the working pattern, definitely they have to come down on pricing if they want to compete in the market."
"I would like to see the real-time replication process improved, and a zero RPO feature added."
"Network-based storage stability could be improved."
"We have had issues with licensing, where the license we've been given by Zerto support doesn't include VSS replication, which was a pain at the time."
"The replication appliances tend to have issues when they recover from being powered off when a host is in maintenance mode. Sometimes you have to do a manual task where you go in and detach hard disks that are no longer in use, to get the replication appliances to power back on. There are some improvements to be made around the way those recover."
"Their data backup and restore have some ways to go."
"The product could benefit from improvements in automation, specifically in the area of failovers."
"From the technical side, there can be a little bit more PowerShell integration. I know it leverages APIs, but people still use PowerShell. Some people would rather use PowerShell if that is an option."
"Not all of the knowledge required for implementing Zerto is available in their online documentation for non-partners."
"I would like to see them continuously improve Zerto's automated functions, such as putting hosts in maintenance mode within vSphere and not having to worry as much about how Zerto is going to react... Sometimes, Zerto almost holds the vSphere environment hostage when it comes to taking certain actions. You really need to be cognizant about what you're about to do. They should further automate that and increase Zerto's ability to handle things like that in a very slick, automated way, without intervention."
"When I have a technical question, it sometimes takes a while for tech support to respond."
Unitrends is ranked 42nd in Backup and Recovery with 34 reviews while Zerto is ranked 2nd in Backup and Recovery with 235 reviews. Unitrends is rated 7.8, while Zerto is rated 9.0. The top reviewer of Unitrends writes "The solution can be used to back up servers and Hyper-V cluster nodes, but its support is super expensive". On the other hand, the top reviewer of Zerto writes "Gives us business continuity capabilities during hurricane season and in case of ransomware". Unitrends is most compared with Veeam Backup & Replication, Rubrik, Acronis Cyber Protect and Commvault Cloud, whereas Zerto is most compared with Veeam Backup & Replication, VMware SRM, Rubrik, Dell RecoverPoint for Virtual Machines and Commvault Cloud. See our Unitrends vs. Zerto report.
See our list of best Backup and Recovery vendors.
We monitor all Backup and Recovery 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.
So does that mean you want to have a Disaster Recovery solution where data is not on site your bunker site? but yet allows for a fast recovery in case your primary site is down?
- What virtualization solution do you use?
- What is the link between the 2 (?) sites?
- What RPO and RTO are you aiming for?
- How much data do you need to recover?
If you don't have live backup? Well as per my understanding backup is always a happened at local site (DC) on VTL and or on Tape and they were offloaded to out of DC, but as mentioned correctly it can take 24hours or more depend on the Recovery site location, accessibility & final is data size. Now the correct terminology is Online Replication or Archive/log base replication, and it is completely depend on the RPO & RTO define by business. So, answare to your 1st query : No way you can do a site recovery if you don't have DR site. Many says to take a back on tape, on disk or on storage but if all these product are installed at production site i.e. DC, will not make any sense as your DC is down and not accessible. So, "must to have live back or rather Replication to DR site.
2nd question" fast recovery without VM in passive or standby mode at DR site. VMware has SRM which does the site recovery in case of disaster. Only condition is that you have to have a Storage with replication between the site. Other option as mentioned by Mr. Smith, is DR as a service model (DRaaS) from any cloud providers. Some of the Cloud service providers also offers CDP solution while not charging for DR site but conditions is DC must be hosted with them.
Tested used my own little setup for hyper V machines have an offsite server using altaro backup offsite server backup software with windows server
restored (anywhere) the Virtual machine was up and running within a 10min entire server
I would also recommend to use Vision DoubleTake at VM level dat has an CDP , continous data protection feature for filesystem replication and SQL integration also. It can be a choice of synchronous replication over DWDM lines if latency it not excceding 0,5 ms round trip, otherwise it will impact disk write ops.
If zero downtime is a must I would recommend using VPLEX,ViPER from EMC or HDS Global Active Device that will present disk LUN from SAN as a single device to more processing nodes, but thus means app is aware of SW clustering (can run in multiple nodes sharing the same filesystem ir SAN LUN).
In such approach in VMware ESXi you will present a datastore spread over DWDM like a strech cluster so you won't have to keep in mind where the app node is really running, the hypervisor will see the strech cluster as only one storage device, thus means you can move app with vMotion very fast to a second or DR site, or recover it to a DR site. More if app is SW cluster enabled then the app nodes will run seamlessly over strech cluster.
The 2 nd option I can see is to go for Hyperconverged infrastructure and application containerization just like Docker tehcnology. How to do it: for ex. Make use of technologies like VxRail appliances and OpenStack + app transformation in Docker (for Windows VM is not so complicate). Such technolgies will apply private Cloud technology for DR.
Hi there, we are talking about Recovery from DR site, now few suggestions from my side 1) what is the defined RTO & RTO. 2) Visibility of the RPO. 3) connectivity between two or three site to meet replication requirements. 4) DR for physical & virtual, both the environment. 5) how many time in a year do the DR Drill. These point need to think and perform to achieve desire & accurate recovery from DR site.
Hi you could try Arcserve UDP -> Instant VM.-
IfI understand correctly the guy needs a fast recovery solution for the production environment to a remote site, for Windows VM under VMware ESXi (or Hyper-V).
In my understanding a DR site means an alternate location with hot or cold standby systems, the recovery plan for business continuity is depending on their RTO and RPO.Unless an RPO and RTO are defined for IT services noboby could picture o solution for such cases. In general solutions are dependent of TB of data to be assured on remote site, basically there are many practices for assuring storage space in DR in case you would need to recover:- cold backup with ESXi that sustain test and development environment physically placed in DR, in case fast recover is mandatory, they could destroy the test/develop environment and restore data from scratch with VTL replicated in DR (backup and restore with 4TB/hour or more). The single point to be assured is correct IP addressing (test/develop could be treated as untrust zone and separated with VLAN and/or firewalls). You can use data protect and snapshots for VM, backup to tape, replicate virtual tapes and restore in case of a disaster (full recovery)- hot backup means CPU and storage for backup DR purposes but can be more faster, but cost a lot of money $$$$$$- rent some storage space and CPU from Cloud vendors, use as they need, maybee the DR location can be in the Cloud provider Data Center but data confidentiality can be a showstopper.
My proposal is to investigate the 1st option with fast backup of data snapshots (space efficiency if dedupe or data compression are available at production site at storage level) and sent them to a restore solution at remote site (virtual backups), restore ops must be tested from time to time to validate business data (not only apps).For fast backups you can try VTL or NFS appliances that include replication services, the bandwidth between sites must accommodate fast delivery to remote site (to assure that RPO and RTO, including restore times are met). I would not recommend a SW solution to replicate VM because if no storage is existing in DR dedicated for this purpose it make no sense to think on such solutions.The 2nd option if to address disk space and CPU needed with Cloud providers, otherwise disk space for VM and user data must be assured always in DR.
Hello,
I suggest taking a look at VMware - Actifio, It might be an option for the
environment you are working at. The minimum data backup for Actifio is
10TB. If your environment smaller than 10TB it will not work.
Regards,
www.actifio.com