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."When I have had to use tech support, they've been very good."
"The ability to diversify jobs within the same server helps break down a large chunk of data into more manageable and concentrated chunks."
"It is a quick and easy way to organize my backups and to keep track of them."
"The simple and fast restore routine."
"The ability to back up both physical and virtual appliances under one roof."
"The most valuable feature of Unitrends for me is the automated feedback"
"It is an easy system to use. The support, if needed, is always willing to help."
"If you are a large organization, this is a product for you."
"The most important feature is that the recovery point (RPO) is less than one minute. The is really good for our customers, as they can keep their data loss to a minimum."
"Its ease of use is valuable. You do not have to do much to install Zerto or implement Zerto on the infrastructure. It is not very complicated."
"We have seen ROI. It reduced the time for failover and failback by 90%."
"We use to use VMware replication appliances to attempt to replicate our VMs to remote locations and servers, but Zerto's one-to-many replication options with deduplication have made the process much simpler without having to constantly worry about the versions of each driver."
"The journaling is the most valuable aspect of the solution."
"The one-to-many replication functionality is helpful. While we were protecting our VMs in Azure, we were able to use the one-to-many feature to also replicate the same VMs to our new data center, in preparation for data center migration."
"The replication feature where it constantly replicates and sees that data is always in sync is valuable."
"The instant recovery at DR locations is the most valuable feature. We're required to do periodic DR tests of critical databases, including Oracle and Microsoft SQL. We have recovery point objectives set for specific databases and we need to be able to achieve them. Zerto helps solve that business problem."
"It could be a little more customizable."
"There's a lot that can be made better. For example, it could be more scalable."
"There are a few quirks where the GUI, agent, and back-end are not precisely meshed."
"Network-based storage stability could be improved."
"The ability to run just differentials without pulling the full on your archive."
"There are some questions as to how safely they are storing backup data."
"Making the seeding process more accessible and easier to understand. Also, make more of the undocumented best practices easier to find."
"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."
"The pricing could be a little bit lower."
"The number one thing we have found we would like changed so far is the cost per VM. It would be great to get that pricing reduced."
"Whenever we do a failover, there's a confirmation box that shows up later. It's a little hard to see sometimes... A popup to continue would be a little bit better because then you're not sitting and waiting for something and it's already there."
"I would like to request better reporting in Zerto. I can see the data that I need in the console, but if I need to put the data or the history into a report, it is difficult. It is something that auditors might require, so reporting is something that needs to be improved."
"I would like Zerto to add support for VMware's lifecycle manager."
"They could iron out the licensing aspect of it, so we might be a bit quicker when implementing and starting to use it."
"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."
"The tech support on my latest issue wasn't so great. I had to figure a lot of stuff out myself. It could be that I had a Level 1 tech who was new or something, but it seemed like the tech was spitballing, which does not help me."
Unitrends is ranked 45th in Backup and Recovery with 34 reviews while Zerto is ranked 2nd in Backup and Recovery with 238 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, Commvault Cloud and Arcserve UDP, whereas Zerto is most compared with Veeam Backup & Replication, VMware SRM, Rubrik, Dell RecoverPoint for Virtual Machines and VMware Cloud Disaster Recovery. 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