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."The simple and fast restore routine."
"If you are a large organization, this is a product for you."
"Stability-wise, I rate this solution a nine out of ten."
"The predictive analytics are great and the reporting is awesome."
"It is a quick and easy way to organize my backups and to keep track of them."
"It is very easy to set up and get started. Almost too easy. We racked this device and had it up and running in less than 15 minutes."
"Unitrends has helped us cut down the time that it takes to restore a server to its original configuration."
"Replication to Forever Cloud."
"Its ease of use and scalability are valuable."
"The near-synchronous replication is key. That has allowed us to provide the low RPOs that we promise. For key systems, that has been the deciding factor."
"The main purpose of this tool is to allow failover between different data centers and different locations. When one site is unavailable, we can start the failover activity and perform the failover task. When a primary location is unavailable, or there is some hardware or logical issue at the primary location, it allows us to resolve the problem. We are able to start services at safe locations. We handle the disaster recovery process, and this is the main function for which we are using it all the time."
"Zerto helped our organization meet compliance requirements by ensuring data protection and recovery strategies align with our regulatory standards."
"We can spin up our environment in DR without affecting production, which is probably the biggest feature for us. We have the ability to do passive testing. We can even test scenarios, such as installing software or changing software. We can make modifications without affecting our production environment. So, the test functionality of being able to test the failover solution and being able to bring up our virtual machines in a test mode is the biggest benefit."
"Managing the system is easy and reliable, you can choose any VM you want to replicate to your DR Site in Combination with other VM's."
"I like the ease of recovery and backup the most."
"Real-time or near real-time replication has been the most valuable feature. Our RTO is generally between six and eight seconds. The impact on our RTO is essential."
"Comparing the features and the working pattern, definitely they have to come down on pricing if they want to compete in the market."
"Probably the biggest issue I've had is actually paying for the unit, and part of that problem is that they use a third party for the billing."
"The ability to run just differentials without pulling the full on your archive."
"No appliance update notifications."
"If the interface could be less complex, it is would be great."
"It could be a little more customizable."
"The solution’s support and onboarding process needs to be improved."
"The amount of updates which are being released. Updates should be limited to two or three a year, focusing more on quality instead of a rushed bug release."
"It needs to support more public cloud."
"They are not cheap. They are more expensive than others."
"I am a little bit worried about how Zerto will work with large volumes of data, such as replication for big data and very large files."
"I don't have any input for improvement or a critical feature request at this moment. If anything, a lower price is always better."
"Right now, our production environment runs on-premises, and we have a DR copy of everything that we run in production. However, our development runs on that hardware. In the case of a DR event, we would need to shut down development and bring up our secondary copy of production. We're hoping that Zerto is going to be the tool to help us do that."
"It took some time to get to know the solution in general, and exactly what functions each of the features is used for."
"When it comes to a solution, one of the things the management wants is to standardize platforms. That's why when Rubrik came out with their solution, they wanted to look at it. For instance, if you have multiple technologies, you're going to need admins to manage all those different ones. I would like Zerto to be something that fits all our needs, including the backup that Rubrik provides, but I understand that not all solutions can be that way."
"The only complaint is that if I remove a host from a cluster, it does not like that. If I move and put the host in maintenance mode to fix it, and vRA is down, Zerto does not like it. Zerto should figure out that this host has an issue and it went down. Zerto should then let me upload that vRA information to another vRA."
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