We performed a comparison between Quest Rapid Recovery and Unitrends 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 best feature of the solution is the user interface."
"The compression and deduplication features have helped to save on storage costs."
"The most valuable feature of Quest Rapid Recovery for our organization is the VM recovery functionality."
"Built-in encryption helps to secure our data as it travels from our on-site server to our off-site backup server."
"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 most valuable feature is the disaster recovery process from the data center."
"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."
"Iinstant recovery (allows a spin-up of your image as a VM on the appliance)."
"Backup/archive to multiple locations."
"They have great support."
"VM backup is much faster and more reliable, as I can test my backups with Data Copy Access jobs."
"The ability to diversify jobs within the same server helps break down a large chunk of data into more manageable and concentrated chunks."
"I am impressed with the tool's reporting and UniView features."
"The most valuable feature of Unitrends for me is the automated feedback"
"Being an appliance-based solution, we were able to migrate backup solutions without having to purchase a lot of hardware separately."
"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."
"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."
"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."
"It's buggy. That's a big problem. We're arranging to get rid of it. We're going to switch to Veeam."
"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."
"One area where Quest Rapid Recovery has room for improvement is in the handling of snapshots on Hyper-V."
"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."
"The ability to run just differentials without pulling the full on your archive."
"Support is great for small simple issues, but anything more difficult, it is hard to get good resolutions without having to badger them and their management."
"The solution’s support and onboarding process needs to be improved."
"I would like to see more storage options for the free version."
"In terms of improvement, the UI, especially in the recovery section, is unclear about which repository it uses."
"It could be a little more customizable."
"I would like to see the real-time replication process improved, and a zero RPO feature added."
"The solution's base operating system needs to be improved."
Quest Rapid Recovery is ranked 26th in Backup and Recovery with 18 reviews while Unitrends is ranked 44th in Backup and Recovery with 34 reviews. Quest Rapid Recovery is rated 8.8, while Unitrends is rated 7.8. 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 Unitrends writes "The solution can be used to back up servers and Hyper-V cluster nodes, but its support is super expensive". Quest Rapid Recovery is most compared with Veeam Backup & Replication, Quest NetVault, Dell PowerProtect DD (Data Domain), Azure Backup and Rubrik, whereas Unitrends is most compared with Veeam Backup & Replication, Rubrik, Acronis Cyber Protect, Commvault Cloud and Arcserve UDP. See our Quest Rapid Recovery vs. Unitrends 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