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."The compression and deduplication features have helped to save on storage costs."
"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."
"One feature I found that's the most valuable in Quest Rapid Recovery is the VM standby feature which is very useful for my current customer. The solution also has a great replication feature. The third most valuable feature in Quest Rapid Recovery is the five-minute RPO and the fifteen-minute RTO. The solution is also very user-friendly."
"Just knowing that the data is easily recoverable is our ROI. It definitely lowers risk."
"The most valuable feature is the disaster recovery process from the data center."
"Probably the point-in-time recovery is most valuable. The other piece that is really nice is that you can mount a whole server at any point in time. So, you can mount the server with all the drives to a Z drive or something like that. It will just mount it all up, and your data is accessible right there on one drive, which is nice."
"The solution's most valuable aspect is its ability to back up a physical server to another physical or virtual server."
"Zerto ensures a smooth transition during a disaster when we need to automatically switch from our primary environment to our recovery one."
"The real-time replication of data is the most valuable feature. It is a vast improvement in scheduled daily backups. Real-time data is streamed to the offsite data center, which allows us to restore our mission-critical applications up to 10 seconds from when the last changes were made in our system. If we enter a sales order or enter any kind of information in our ERP application it is replicated within 10 seconds to the offsite location."
"I like the fact that Zerto is target agnostic. It doesn't care what type of storage it writes to. The journaling is also excellent. You can easily and quickly restore to seconds before an event. The immutable data copies feature is one reason we adopted Zerto. That's one of its selling points."
"Being hardware agnostic is nice in that we don't really need a 15 second recovery time. It's easy to use. It's always doing updates behind the scenes. These are the positive things. The setup is pretty easy. Building out the VPGs is pretty easy. And it works like it's supposed to."
"It is convenient to use because the API allows for seamless integration when performing our day-to-day operations."
"It is incredibly granular and I really appreciate that."
"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 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."
"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."
"The terminology didn't seem easily available. When I go to the website, it is hard to search for things. You get all the articles, then you finally get the search button. They need the search at the top of the knowledge base. Then, on occasion, if you get an error message in the system, which is very important, it says, "Click here for more information," but I never get more information. The search engine doesn't find it or it is some weird error. It has never worked for me."
"When you do a full backup, all of the memory resources on the server are used, which is something that should be improved."
"It is quite surprising to me that the configuration cannot be backed up automatically, and I think that Rapid Recovery should have an option for scheduled configuration backup."
"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."
"I think the self-paced learning and knowledge base can always be improved so that users can self-service without having to contact either a reseller or Quest. I know there are things that I would have been looking for to try and solve. And the only way I could get there was to actually open a ticket rather than go through self-service through the portal."
"It's buggy. That's a big problem. We're arranging to get rid of it. We're going to switch to Veeam."
"It's not really Quest's fault, but the only issue that I had during the time when I was doing a lot of our restores is whenever the server reboots, it has to bring all of the repositories back in again, which takes around five to six hours to pull eight terabytes back in again."
"We had some issues with replication, especially on Linux, but we have already resolved them."
"Zerto can improve the dashboard by making it even more simple. Right now, there's a lot on the dashboard, and it can be overwhelming. If you're an experienced user, then you'll find it easy to use, but if you're a beginner, it will take you some time."
"We would like the LTR function to be able to retain the past 12 months."
"When we are trying to upgrade any virtual machines, we have to stop the virtual machines that have been replicated in Zerto and then upgrade or update to the virtual machines onsite. Instead of having to do it manually, there should be some way of automating that particular function."
"When we do failover and failback, it doesn't maintain some of the settings that it should and I don't really understand why that happens."
"It has some quirks. We have quirks with appliances. Some things don't really work as expected, but it is minor."
"This solution could be improved if it met all the requirements that we look for including supporting multiple operating systems. We would prefer to use one solution for DR and backup."
"One improvement that could make it easier would be to have an easier way to track journal usage and a little bit more training around journal sizing. I've done all the training and the journal is still a gray area. There is confusion surrounding how it's billed and how we should bill clients. It would be easier if it had billing suggestions or billing best practices for our clients to make sure that we're not leaving money on the table."
Quest Rapid Recovery is ranked 26th in Backup and Recovery with 18 reviews while Zerto is ranked 2nd in Backup and Recovery with 236 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, Dell PowerProtect DD (Data Domain), Azure Backup and Rubrik, whereas Zerto is most compared with Veeam Backup & Replication, VMware SRM, Rubrik, Commvault Cloud and Dell RecoverPoint for Virtual Machines. 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