We performed a comparison between Quest Rapid Recovery 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."Definitely, the mount and recovery points are the most valuable, because if someone deletes a file or something, or if something gets corrupted, we can always revert back to an old change because our repository goes about a month back. The ability to roll back files and the ability to roll back servers is really important."
"The compression and deduplication features have helped to save on storage costs."
"The best feature of the solution is the user interface."
"Not having to switch tapes is wonderful. It makes it so easy. We have an on-prem deployment that we also replicate to an offsite replication host. So by not having to deal with tapes and moving them off-site every day and every week, that's amazing ease of use for us."
"The most valuable feature of Quest Rapid Recovery for our organization is the VM recovery functionality."
"The most valuable feature is the disaster recovery process from the data center."
"The local mount utility is most valuable. I do restores fairly regularly. Thankfully, I have not ever lost an entire server that I've had to resurrect, but I certainly have people who erroneously saved over a file or have deleted a file. So, we've done that quite a bit. We still have the DL4000 appliance, and we had, kind of, extrapolated that out over a five-year period. Now, we're in year six, so we had to add storage, which we did as a SAN next to DL4000, but prior to adding in that extra storage, we, here and there, would run into situations where for whatever reason, it would want to be pulling a new base image, and then we would run out of storage. So, we would utilize the archive feature and archive the old data that we want to hang on to, but we don't necessarily need it taking up current data storage. Being able to export out really old data is most valuable to us. Then, we just store that on a NAS that we keep in another building."
"The fact that it can take a snapshot of everything on a server and replicate it on another server in real-time is the most valuable feature."
"Files can also be extracted from the VMDK at the remote site even when the VM is off."
"The communication between the VM and the secondary data center is the most valuable feature."
"The most valuable feature is the ability to recover critical systems, such as public safety, within a few minutes. In addition, the RPO is six seconds of data loss, tops."
"There are two things that are keeping us with the solution: 1. It does a very good job of keeping the data in sync at all times. 2. In the event of a failover or in the event of a contingency, we are able to retrieve the data very quickly without any issues."
"Consistency Groups: If you replicate groups of VMs, then during failover, all of the VMs in groups are failed over to the exact same point in time."
"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."
"During a failover to a DR site, Zerto can automatically change the IP address of servers."
"The continuous data protection is great. We love it because I can see exactly how many seconds behind real-time we are, which is usually under 10 seconds. It keeps things up to date. We love the product."
"In terms of what needs improvement in Quest Rapid Recovery, though the solution is seamless, right now, they are just giving the software which means we'll need to arrange the hardware. If they can combine the appliance and software, that would be a great approach. In the next release of Quest Rapid Recovery, it would be great if they'd add a folder backup feature because only a snapshot backup feature is available at the moment."
"It's buggy. That's a big problem. We're arranging to get rid of it. We're going to switch to Veeam."
"For the most part, it is really good in terms of flexibility and choice of recovery methods. What we found lacking was being able to back up virtual volumes that are clustered. We ran out of luck there. There should be an option for backing up clustered virtual volumes."
"When you do a full backup, all of the memory resources on the server are used, which is something that should be improved."
"You can only take a snapshot from a virtual environment. It should have the ability to take snapshots from both a virtual and physical environment."
"One area where Quest Rapid Recovery has room for improvement is in the handling of snapshots on Hyper-V."
"The on-premises deployment model shouldn't have a maintenance fee. If there's going to be technical support, they need it to be free or it should be paid on upon adopting the solution."
"Sometimes, when we have certain batches for Windows, it needs to be restarted. When it's restarted, the service is configured as a delayed start. Sometimes, you need to wait too long until it rights itself, or you have to do it manually."
"The alerting could be fine tuned and improved. It does a lot of alerts, but it's a little bit cumbersome to modify them."
"I wish they would...develop their PowerShell module to be more robust. So instead of having to rely on the API to actually include a PowerShell command, it would let you create VPGs, delete VPGs, modify VPGs, etc. This would ease the automation effort of deployment and decommissioning and I'd really appreciate that."
"Zerto could add text alerts if there are critical problems and alerts if changes affect our replication."
"There should be an automatic installation in a cluster. When I add a virtual client or ESX source to the cluster, it should automatically install that. There should be automatic installation. Currently, I have to do that manually."
"We have had some issues with trying to get certain parts of the backup or restore functionality to work."
"An area for improvement is the support because it gets really expensive. They need to make it a little cheaper. Support also takes time."
"They could iron out the licensing aspect of it, so we might be a bit quicker when implementing and starting to use it."
"It is crucial for Zerto to collaborate closely with VMware in order to promptly test updates."
Quest Rapid Recovery is ranked 27th in Backup and Recovery with 18 reviews while Zerto is ranked 2nd in Backup and Recovery with 238 reviews. Quest Rapid Recovery is rated 8.8, while Zerto is rated 9.0. The top reviewer of Quest Rapid Recovery writes "Allows us to do point-in-time recovery and mount the whole server and saves quite a bit of time". On the other hand, the top reviewer of Zerto writes "Gives us business continuity capabilities during hurricane season and in case of ransomware". Quest Rapid Recovery is most compared with Veeam Backup & Replication, Quest NetVault, Azure Backup, Dell PowerProtect DD (Data Domain) 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 Quest Rapid Recovery 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