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."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."
"Just knowing that the data is easily recoverable is our ROI. It definitely lowers risk."
"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 most valuable feature of Quest Rapid Recovery for our organization is the VM recovery functionality."
"The best feature of the solution is the user interface."
"The solution's most valuable aspect is its ability to back up a physical server to another physical or virtual server."
"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 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."
"What I like most about this solution are the simplicity and the price-performance ratio."
"The initial setup is simple to do in Veeam Backup Replication."
"The most important part is that you actually know you have a backup of the whole virtual server."
"Instant recovery, ease of use, and integrations are some of the valuable features."
"It is cost-effective. A lot of times, people pick Veeam because of its price."
"The solution does a good job with VM backups."
"Veeam Backup Replication's most valuable features are it is easy to use and manage."
"The encryption password is used to protect the backup files. Even if someone gains access to the backup job or files, they won't be able to utilize them without the password."
"One area where Quest Rapid Recovery has room for improvement is in the handling of snapshots on Hyper-V."
"Rapid Recovery can only backup the machine or disc, but it can't back up from folders, and files, and things like that."
"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."
"It's buggy. That's a big problem. We're arranging to get rid of it. We're going to switch to Veeam."
"When you do a full backup, all of the memory resources on the server are used, which is something that should be improved."
"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."
"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."
"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."
"Additional executive summary reports for the entire infrastructure would be a nice to have."
"Its licensing needs to be improved. Its licensing has become complex since last December. They have changed the way the product is licensed, and there is a lot of confusion. Sometimes, when a new version comes, it seems that it has not been tested enough because I usually find some bugs in it. It could also have more integration with other virtualization products, such as desktop virtualization products and open-source virtualization products."
"The Veeam backup application interface is application-based and not web-based."
"The price is an issue. If one has a large number of servers, say... 100-plus, and wishes to add more, an exhausted budget may hinder this ability."
"The initial setup of Veeam Backup Replication is straightforward. The process took approximately two days. The setup could be streamlined to take less time."
"I like the Acronis backup solutions on the block-based part of backups or snapshots. That's a nice functionality that Veeam doesn't have."
"One challenge that we have encountered was on the long-term retention of data. Be sure to look into a dedicated deduplication appliance."
"They need to improve their technical side."
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