We performed a comparison between Quest Rapid Recovery and Veeam Backup & Replication 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."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."
"Built-in encryption helps to secure our data as it travels from our on-site server to our off-site backup server."
"The solution's most valuable aspect is its ability to back up a physical server to another physical or virtual server."
"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."
"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 solution offers a 100% guarantee that if it's backed up you will be able to restore it onto any platform you want."
"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."
"Most of the features that we can use with HPE products are directly integrated with the Veeam. This is very important for the customers to have only one pane of glass to manage the backups and also use the HPE products for the backups."
"It's very easy to work with and it's very reliable."
"It is cost-effective. A lot of times, people pick Veeam because of its price."
"It serves its intended purpose and it works well."
"Very flexible, all-in-one solution."
"Strong performance with a high level of compatibility."
"I like all the backup features in Veeam."
"For virtualization it's perfect."
"There could be better space management for incremental data. When you use incremental data, the space in the appliance keeps on going up. There should be a better way to manage the space. You have to manage the incremental data to reduce the time."
"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."
"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."
"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."
"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."
"Rapid Recovery can only backup the machine or disc, but it can't back up from folders, and files, and things like that."
"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."
"Veeam Backup Replication could improve by having better integration with the cloud. Additionally, they do not have direct integration to S3 or Azure storage for the backups of the VMs. This feature would be beneficial because we have to go through the scalable repository which I do not like."
"They fixed everything that I was hoping for. It is pretty good. There were a few things in 9.x that I was wishing for, and they came true in version 10. We were looking for retention without having to make a copy job. We're getting ready to migrate m365 to the cloud. I haven't dived into it to make sure, but I wish the m365 backup would integrate into the current console so that we don't have to use two different consoles."
"The initial setup can get complex."
"A backup and replication solution should be able to back up a system and do recovery very fast. Even though Veeam Backup & Replication is able to meet most of our needs, it would be better if they can make it faster for backup and restore."
"The initial setup of Veeam Backup Replication is straightforward. The process took approximately two days. The setup could be streamlined to take less time."
"Veeam Backup & Replication should include a cloud solution."
"They have an integration with MS SQL, and you have to license MS SQL. This is something they need to change. They should go for an open-source database or a free SQL because you're already buying this product, and you shouldn't have to buy another product."
"Margins should not be distinct; instead, they should seamlessly integrate with the Veeam Backup and Replication tools, requiring minimal separation."
Quest Rapid Recovery is ranked 26th in Backup and Recovery with 18 reviews while Veeam Backup & Replication is ranked 1st in Backup and Recovery with 329 reviews. Quest Rapid Recovery is rated 8.8, while Veeam Backup & Replication is rated 8.6. 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 Veeam Backup & Replication writes "Beneficial pricing model, user friendly interface, and many free features". Quest Rapid Recovery is most compared with Quest NetVault, Dell PowerProtect DD (Data Domain), Azure Backup, Rubrik and Acronis Cyber Protect, whereas Veeam Backup & Replication is most compared with Acronis Cyber Protect, Azure Backup, Rubrik, Zerto and Veritas NetBackup. See our Quest Rapid Recovery vs. Veeam Backup & Replication 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