Backup and Recovery Software Forum

Rhea Rapps
Content Specialist
IT Central Station
Sep 22 2018
One of the most popular comparisons on IT Central Station is Cohesity vs Rubrik. People like you are trying to decide which one is best for their company. Can you help them out? Which of these two solutions would you recommend for Backup and Recovery Software? Why? Thanks for helping your peers make the best decision! --Rhea
Nathan MonkIf you do a head to head challenge with the two products capabilities, Rubrik will win out every time. Cohesity's UI is a little clunky and childish and Rurik's is simple, elegant and intuitive. Rubrik has amazingly simple scale-out and you will not beat the search functionality and time to recovery. On top of that, their support is beyond top notch. I evaluated both products before ultimately going with Rubrik and haven't looked back since! Compare customers and awards alone to give you an idea of how Rubrik is leading the way in Data Management both on premise and in the cloud. Happy to give more input if anyone needs it :) Trust me, you wont be disappointed choosing Rubrik.
Jon McFarlandWhen looking at both solutions, I originally had a leaning preference to Rubrik, but that quickly faded when looking at demos of both the solutions. Cohesity and Rubrik basically have the same feature sets and do the same in the backup realm. If you compare they both use Policy based backups, they both integrate very well into VMware, they both do near instant recoveries, they both use scale-out file system, they both have search capabilities, and many more capabilities. What ultimately lead us down to choosing Cohesity, was the sale team. Rubrik ignored us, sent us a full price sheet and never gave us the time of day. Cohesity setup meetings, helped size out our infrastructure (even if we didn't go with their solution), and their sales team was very laid back and not bombarding us with calls and e-mails about if we had decided yet. After learning more and more about Cohesity and Mohit Aron, it is a company I truly believe will continue changing not just the backup space for a long time, but the secondary storage space. Their technology and staff are the best in the industry and they help do anything needed. I believe Cohesity provides way more than Rubrik ever will, simply because they are focusing on the entire secondary storage landscape and not just backup. You can do analytics, test/dev, automated policy assignment, etc. While I cannot speak to the cloud functionality because we utilize two clusters with site to site replication, everything else just works. I'm not sure the accuracy of those utilizing Rubrik that are speaking for Cohesity's clunky interface, because the UI is painstakingly easy and intuitive. Rubrik may very well be the same, but look up videos of Demos and I would say the UI is not a reason to pick one over the other. The support from Cohesity is industry leading and I have been shocked from the first ticket submitted, when at 2AM you submit a ticket and get a response within minutes, they are quick, efficient, and even proactive in fixing problems you may not have even knew existed. They are constantly coming out with additional features and they truly listen to what the users actually want or need. I end with the contention that I would invest in Cohesity in a second, if they ever went Public and willingly will refer anyone and everyone I hear having a backup problem to Cohesity. Oh as a side note, Mohit seems to truly be a great leader, I've listened to a few of his interviews, and I believe the leaders of a company make or break it. Two shocking things that I think need to be more widely known. He refuses to have an office (wants to sit with his "troops") and he sets time every week to still code on the platform. ______________________________________________________________________ Answering the "View box" issue that Paul mentioned, is that Cohesity provides "View boxes" to be able to provide flexibility and security on the data you want to store. Taken from the Cohesity's site "A View Box is a logical division of a partition, that contains one or more filesystems. Each of these View Boxes encrypt data ‘stored’ by them using their own independent keys. This allows for robust data isolation. For example, if IT data and financial data are on different view boxes, a breach on the IT data will not automatically risk your financial data." Of course, if you want Global Dedupe and are not concerned about siloing off data then you can always just make one View Box that provides global dedupe (it is also dedupe's before replication).
Brian CritchlowWe chose Cohesity over Rubrik. The POC was very close, but our techs preferred the Cohesity UI and the ability to restore VMs to a standalone ESXi host, which Rubrik can only do via API.
Rhea Rapps
Content Specialist
IT Central Station
Sep 05 2018
One of the most popular comparisons on IT Central Station is Commvault vs Rubrik. One user says about Commvault, "The capacity savings of this approach led to significant cost savings on the long-term retention of data in the cloud for us." Another user says about Rubrik, "This has become our go-to solution for disaster recovery requirements for many of our applications. The great part is we don’t have to build out DR VMs to sit there and do nothing, instead we can deploy a snapshot from production when needed." In your experience, which is better and why?
reviewer816135If you have a simple environment with a small infrastructure team and Rubrik will do everything you need, Rubrik is a strong solution. Commvault is the most complete data protection solution if you have a complex environment and need a more flexible range of recovery methods, but you will need dedicated Commvault administrators because it’s a beast. Another point is that in general, I don’t like physical appliance-based solutions like Rubrik, because the hardware and software go EOL together. Software solutions like Commvault retain their value through successive hardware life cycles, you just keep updating the software and replacing the hardware.
Brandon MorrisIf you would like a solution that requires constant babysitting and restarting agents, then Commvault is for you. If you would love to be upsold to backup more than your backup server can handle, then Commvault is for you. If during that process you would like your deduplication engine to die, and lose the ability to use all of your backups, then Commvault is for you. If you would like something that just works and keeps doing it without further effort, then Rubrik is for you.
Jonathon ManciniWe looked at Commvault and Rubrik and ended up going with Cohesity. We are using it both to store backups and as a file server to replace windows file servers so Cohesity was the best fit for us.
Rhea Rapps
Content Specialist
IT Central Station
Aug 09 2018
We all know it's important to conduct a trial or do a proof of concept as part of the buying process.  Do you have any advice for our community about the best way to conduct a trial or PoC?  How would you conduct a trial effectively? Are there any mistakes which should be avoided?
Gary-CookI am not sure if this question comes from a vendor or customer so the response is somewhat generic. If you are the technical customer or end user, try to be involved in the process start to end. If possible, be the hands on the keyboard. No better way to understand the solution if you are going to be the user of it in the future. If you are the vendor promoting ease of use, there is no better way to sell your product to the technical team. I have managed a lot of data replication, protection, and archiving POCs. Two requirements always stand out. Success criteria and POC type. As a vendor delivering the POC, you will fail 90% of the time without clearly defining these up front. As a customer, you should have a clear idea about why you are investing your time in POC and what you expect to gain from it. POCs should not be a training exercise. They are a path to purchase a solution for a budgeted project. If you are just kicking the tires, consider the free or self-paced options provided by many vendors. These include on-line labs and downloadable virtual machines or trial software. These cannot be considered a POC in my book. Now the two key components for a successful POC. #1 - Define as a Functional or Performance POC Decide whether you are running a functional or performance-based POC. If you are the vendor, make sure the customer is aware of the limitation of a functional POC in a limited resource environment. Don't allow a Functional POC to become a Performance POC. Been there. Done that. It's never a success. Functional testing is easier. There is no requirement for measured performance so sizing the environment is a minor issue. Just has to be "fast enough" to keep your attention. They usually cover base installation, backup target configuration, agent configuration, test backups and restores, reporting, alerting, etc. Data sets are generally small. It can be executed in a limited environment with virtual machines. Sometimes the vendor can supply access to a remote lab environment such as the VMware vSAN lab. Sometimes it can be delivered as a preconfigured VM downloaded from the vendor. Performance testing is complicated. Speeds and feeds matter. You will not be able to backup your entire live environment so you have to build a test environment to mimic it as close as possible if you are looking for GB/sec measurements. Success Criteria become golden in performance tests. You will be following the recommended hardware configuration supplied by the vendor. #2 - Success Criteria Define clear success criteria and stay with the plan. This will avoid scope creep where testing has no endpoint. A test plan can be extremely difficult to create from scratch. Take the time because it is key to a fair and complete test. It will make you think about the purpose of the test. Most vendors have boilerplate POC documents. They are a good starting point but they almost always focus on the strength of the product. If you are the customer performing comparison testing, blend them into a single document. Some or all of the success criteria should meet the "must have" requirements of a published RFP if it exists. Test criteria should not be too detailed, especially to favor a particular solution UNLESS that is a pass/fail test. Define a start and end date based on the testing requirements. Testing should be sequenced. Test backup of app A, app B, os C.. Don't jump back and forth between Oracle and Sharepoint for example. Complete one, deal with any issues, check the boxes, and move on. DR, Performance, and SLA testing absolutely require detailed planning. Too much to detail in this short response. Imagine a POC where you are faced with "I need to recover my 50 TB Oracle server off-site with an RPO of 5 seconds and an RTO of 5 minutes". In a large POC, you might have regularly scheduled meetings or conference calls for updates on the progress and to deal with issues. Include a site survey covering security and the network configuration, Prepare to deal with fixed IPs, firewalls, ports, Active Directory, etc. Nothing like a backup solution to break a network and bring the testing to a standstill. Make sure you have a clear understanding of the environment. I once had a POC where they were migrating some AD domains that were part of the test infrastructure. Unknown to me. Needless to say, we faced constant failures. Define the hardware and configuration requirements on a per server basis. OS, partition sizes, network, etc. This applies to the backup infrastructure servers and the servers that will be the source of the backup data. Include all the key contacts with access information to servers. Make sure you have ALL the required resources (human and compute) resources available on the start date. For example, you might need help from an Oracle DBA or SME on day 2 to continue the installation. Define a process to modify the plan. I've seen cases where another department sees the shiny new object and wants to jump into testing their app after the plan was approved and tests begin. Plan to deal with this exception in the testing procedure but not deviate from accomplishing the original success criteria. It should be approved by management. Define what is considered critical to the success of the test, what is a nice to have feature, and optionally, what doesn't matter at all. Be specific. Include application versions if it matters. You might judge the test completion as pass / partial pass / no pass or a percentage of how it meets the criteria. Don't use subjective rankings. Add a column next to the test for comments for subjective comments. If you are comparison testing two or more solutions, make sure you can test "apples to apples" across the POC candidates. All vendors should be tested to the same standard. It can be difficult to compare an appliance to an enterprise software solution. The appliance will win the easy to install checkbox but might fail in the ease of expansion category because it requires a new, larger box. Consider the future in a POC, not just how it functions today. For example, you should think about the process to add additional capacity locally or bring on new sites/servers. NOTE: Content here subject to updates if I think of something new or helpful.
MichaelWeimannWas going to write a lengthy response but yours is spot on Gary. I will only add that the front end and back end of every SMART goal is to be Specific and Timely. Document what is important to test and what the criteria for passing are BEFORE you ever take delivery. Then put an expected time for this POC to complete and what would be a successful test. The only other thing I would add is if the vendor is not providing technical resources to drive and/or assist during the POC...don't waste your time. But, if you expect the vendor to devote the resources, you can also expect the vendor to hold you to a purchasing decision when/if everything passes with flying colors.
Fred KovacsI know this is a simple answer but research companies that offer this service and use their free software trial versions to see if you like them or not. Research is the answer.
Ariel Lindenfeld
Sr. Director of Community
IT Central Station
Jul 13 2018
Let the community know what you think. Share your opinions now!
it_user172683Solving My Backup Problem : - small time backup windows - Easy to recovery - Storage Consent - Role Based Access Management
it_user184029-The Average of daily or weekly changes in your data -High level of recovery options -Storage media type based on corporate needs -The size & type of the data
it_user196860-Backup Time (backup Window) -Restore time -Solution which can save Backup data size -Solution which can make DR Backup copy
Rhea Rapps
Content Specialist
IT Central Station
One of the most popular comparisons on our site is Commvault vs Veritas NetBackup.  One user says about Commvault, "[It is] A very stable and scalable platform (you can backup/restore/protect a couple of MBs or hundred of TBs as well from the same console/platform)." Another user says about Veritas Backup, " The product itself is very stable. Most issues with stability come from running too many parallel operations and the hardware itself can’t handle it." In your opinion, which is better and why? Thanks! --Rhea
it_user187182Frankly, we don't use any of above 2 software. We are using Veeam Backup, a rising star, as the mainline now.
Darshana WaghmareBoth solutions have their pros and cons. Commvault is much more simple to operate/Manage and yes we can manage different modules of Commvault backup (Server backup, endpoint backup, and restoration) from a single console as compared to Veritas. With Veritas comes stability and complexity. But it can manage bigger IT infrastructure in a very efficient way. Have various features like AIR, DPO, global deduplication, search option in À la carte as well as in bundle (NEVC) for physical and virtualization. We can mix various licenses in Netbackup like NEVC and agent for windows or NDMP for Physical, which is not available in Commvault.
Kyaw ThanWe are a NetBackup shop. I have followed Commvault as well in discussions with my peers who use Commvault. I am more knowledgeable about NetBackup than I am about Commvault. My very high level assessment would be that: - if backup / restore is your only concern, then both are equally capable and it may come down to which one is more suitable to your particular environment, or price negotiations. - my initial observations would appear to favor Commvault if you have a need for strong integration with storage and SAN architectures. Commvault appears to have many interfaces to different SAN and storage vendors. - Veritas NetBackup is now more than just backup / restore especially if you want to start managing or analyzing your data through NetBackup. You can purchase additional software from Veritas that can manage and analyze your data environment by leveraging the data and metadata information that NetBackup collects in its catalogs. If you intend to go down that path, then perhaps NetBackup might offer you options not (yet) available in Commvault. Beyond this cursory high level assessment, you would of course have to carry out a more detailed analysis to determine what you want. I have not touched upon backup appliances from these vendors for example. Regards, Kyaw
Rhea Rapps
Content Specialist
IT Central Station
On a scale from 1-10, how you rate Acronis Backup, and why? 
MS AlamAcronis backup is good for windows environments or we can say that individuals system because its work very good when we take the images to any system and restore the copy to some other work station. but this is not smart ways backup in big organisation because big organisation need disaster recovery backup like that Veeam or Net worker and Veritas. this Disaster Recovery software work for all the environment.

Sign Up with Email