We performed a comparison between Quest Rapid Recovery and Rubrik 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 most valuable feature of Quest Rapid Recovery for our organization is the VM recovery functionality."
"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 compression and deduplication features have helped to save on storage costs."
"The solution's most valuable aspect is its ability to back up a physical server to another physical or virtual server."
"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 general backup for replication and virtual standby are the most valuable aspects. It does what it says it does. It's a decent tool for not a big budget."
"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."
"It is very easy to use and very easy to manage. The fact that I can easily recover data is valuable. I don't use it much. The only way I have been using it is that sometimes, people ask to recover the data, which is a very easy process. It takes only a few minutes to get in and get the data from the server."
"The Live Mount feature is excellent; it's useful for the backup administrator and end user."
"It has a streamlined user interface, provides an improved tech support experience, and reduces time required to locate and restore data."
"The web interface is user-friendly, clean, and it provides a good summary of what you're protecting at a glance."
"The fact that the API is so available to us with the playground — there's an internal and public playground — is also valuable. We can write API calls — and although I'm sure there's a way we could hurt the data — we write those calls with a lot of certainty that we won't be destroying anything. We write these API calls using really easy mechanisms and generate automation a lot faster."
"I would rate the solution's web interface at eight out of ten. It's just fantastic and intuitive. It's so easy to use. I've never done any formal training on Rubrik, but I was able to quickly come to grips with its capabilities."
"Live Mount is where we do the majority of our big recoveries, unless it is a file recovery. A file recovery takes a few minutes to restore to where the file in the event a file was accidentally deleted by a user, etc. There has been at least a 90 percent reduction in recovery time based on our previous solution, from the need to recover something to when it's actually recovered went from hours to minutes."
"We had some VMware issue as VMware did some changes on the AHCI drivers. Rubrik saved our environment those times."
"Adaptative backup and SLAs simply allow you to tell a machine to backup without taking care of the backup window."
"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 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."
"Rapid Recovery can only backup the machine or disc, but it can't back up from folders, and files, and things like that."
"In case, if there is anything, it would be the speed of the operation to be finished. Even then, I can easily work on the storing function before the operation is finished."
"I don't really think that there is a whole lot that needs to be changed. It would be nice if you could deploy the agent without having to reboot. When I upgraded my core to the latest version, I also wanted to update all of my servers, but I had to put that off because I can't just shoot it out there. I have to make sure it is at a time when I can do a reboot right away."
"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."
"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."
"Setup is immediate but pricing is not cheap."
"We have some challenges with the solution's reporting because historical reports have some limitations."
"A singular system is needed to manage all of the clusters."
"It would be nice if they could work on the pricing a bit."
"Looking at how the data is broken down, we can see the total story, but sometimes it's difficult to see how big a particular snapshot is. Across 90 days of snapshots, which one is a particularly large one? Looking at the data holistically could be a lot easier."
"If I could take a snapshot from a physical and be able to stand it up as a virtual immediately without the need to rebuild an entire system and restoring files, that would be HUGE."
"There is room for improvement in pricing. After the licensing, the price tends to go up as time goes by."
"Pricing is something that needs to be considered for improvement."
Quest Rapid Recovery is ranked 24th in Backup and Recovery with 18 reviews while Rubrik is ranked 4th in Backup and Recovery with 82 reviews. Quest Rapid Recovery is rated 8.8, while Rubrik is rated 9.2. 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 Rubrik writes "Easy to use with minimal training required, innovative, good support". Quest Rapid Recovery is most compared with Veeam Backup & Replication, Quest NetVault, Azure Backup, Dell PowerProtect DD (Data Domain) and Acronis Cyber Protect, whereas Rubrik is most compared with Veeam Backup & Replication, Cohesity DataProtect, Commvault Cloud, Zerto and Dell PowerProtect DD (Data Domain). See our Quest Rapid Recovery vs. Rubrik 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.
