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."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 is the disaster recovery process from the data center."
"Just knowing that the data is easily recoverable is our ROI. It definitely lowers risk."
"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."
"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 solution's most valuable aspect is its ability to back up a physical server to another physical or virtual server."
"Built-in encryption helps to secure our data as it travels from our on-site server to our off-site backup server."
"The best feature of the solution is the user interface."
"From my experience, Veeam is very good. Its interface is user-friendly. We can restore it whenever. It's not complicated. It's very easy to manage and administration is very easy."
"It's fairly easy to manage and set up."
"Provides lots of reporting and visualization of how much data has been transferred."
"Its backup capabilities in general are great."
"It is way easier to take backup with Veeam Backup & Replication than the regular ones."
"The solution is easy to use and have good performance."
"The integration with some storage systems like HP or Nutanix and great support are the most valuable features. You get productivity support. You get a response within one hour, even in the evening or night. The functionality of the whole software is good."
"One of the best things about Veeam is that they have consistently improved on themselves since they started. Personally, I've been using Veeam since around 2013/2014 when it was only supporting certain hypervisors such as HyperV, and since then it has become truly mature enterprise-level software with a lot of versatility."
"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."
"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."
"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."
"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."
"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."
"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."
"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."
"I would like to see a storage application in the next version of the product."
"Offering mobile apps that give engineers a global view of his backup regime would be a "nice to have" feature."
"The initial setup of Veeam Backup Replication is straightforward. The process took approximately two days. The setup could be streamlined to take less time."
"We would like to have the ability to perform more things on the web interface. The heavy client is still needed to perform advanced tasks."
"Veeam doesn't have the reporting part quite right. Its data visualization isn't as slick as other solutions like Veritas. For example, in Veritas, you can see a calendar that shows you which days are backed up. Veeam lacks features like that."
"Near-synchronous, better RPO and RTO snapshot-based takes a lot of space and resources."
"Its price is higher than other solutions and can be improved. They can also change the version of the software more often."
"The solution requires a lot of bandwidth."
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