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 ability to back up both physical and virtual appliances under one roof."
"It is an easy system to use. The support, if needed, is always willing to help."
"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."
"Backup/archive to multiple locations."
"I really like the reporting options you get for various email reports."
"I like the fact that you can recover the VMs inside the appliance. For example, they're basically running this appliance on a Linux-based distribution, and they're spinning off KVM virtual machines inside."
"It's not easy to scale it."
"The second feature that sold us was the sub-second RPO. One of the things that made Zerto's product stand out from some of the more traditional solutions four years ago was its ability to maintain sub-second RPO over a group of machines, and that group of machines could be spread over multiple storage hardware."
"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%."
"Continuous replication is the primary feature we use now because we originally purchased Zerto. I'm starting to utilize the long-term retention and instantaneous file restoration features, which have been introduced since the original purchase in 2015. Initially, we deployed Zerto as a second data storage point, but ultimately it will probably facilitate some of the migration of my workloads up to the cloud. It's evolving with the network and how we deliver computation."
"Journaling allows us to leverage Zerto's journal for sub-minute recoveries, instead of having to wait for the storage array to replicate."
"The most valuable feature is the point in time recovery. This allows us to recover at any point in time, up to a minute or so."
"The initial setup was very straightforward and easy. We were able to start replication within minutes of the initial setup."
"In terms of continuous data protection, it's the best product that we've found that does this. It's not snapshot-based. It's continuous, so there are no specific points in time we have to worry about recovering to or from. It's pretty much any time, as long as it's within our replication window."
"I would like to see more storage options for the free version."
"Network-based storage stability could be improved."
"There's a lot that can be made better. For example, it could be more scalable."
"In terms of improvement, the UI, especially in the recovery section, is unclear about which repository it uses."
"It would be great to have the job throttle/limit the max number of backups on a single ESXi host."
"Unitrends can be challenging to scale."
"No appliance update notifications."
"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."
"Zerto's price has room for improvement."
"The pricing could be a little bit lower."
"Their offsite backup is a bit clunky, but it will probably improve."
"More user support would be best for me because I'm not in the product all the time. So, having strong support is probably the most important decision on any products that we buy."
"Improvements in Zerto's user interface and the addition of advanced features such as artificial intelligence or machine learning for predicting ransomware attacks and workload requirements would be beneficial."
"The time between releases is too long. Zerto doesn't seem to really keep up with the products with which they need to be compatible. For instance, the 9.5 updates 3 took about 90 days to come out after the latest version of vCenter 7.0 update 3 was released."
"The technical support response needs improvement."
"They definitely have room for improvement in a couple of areas. One is role-based access control. Right now, they don't have an identity source so they use the identity of the vCenter or the VMM. If they connected to an identity source like Active Directory and allowed for granular roles and permissions, that would be an improvement."
Unitrends is ranked 45th in Backup and Recovery with 34 reviews while Zerto is ranked 2nd in Backup and Recovery with 236 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