Previously, we had an Avamar data domain backup environment. It meant that anytime we had capacity constraints, what would happen was that Dell would come in and say that it was just as cheap to buy a new unit as it was to upgrade the existing one. It was always a big sell to supply the customer the newest and greatest thing, which sort of capped out at a certain capacity and couldn't really be expanded past that point.

Being an MSP, having expansion capabilities was really key for us. Having the ability to just add nodes, and have that capacity online inside 30 minutes was really fantastic. We know that the investment being made into the existing equipment isn't dead in the water, having to be thrown away later.

Implementing Rubrik has saved us time and money in managing backups, and I estimate that we've saved approximately 80% in terms of time compared to previously. This was in maintaining the system and doing upgrades. In terms of cost, we have had to hire a very expensive backup administrator that was really well versed in the Avamar product, and we constantly had problems with the upgrades once they were done. So, to move down to a lower-skilled and lower-cost resource, and have the task be completed in less time, was a significant dollar saving.

In the past, when we did upgrades, we could be offline for a week troubleshooting. Now, once we do an upgrade, we're back to doing backups within half an hour to an hour. 

We switched for ease of use, the total cost of ownership, and the cost to maintain. It came down to the financial benefits and the time benefits and in terms of ease of use and customer self-service. There were a significant number of reasons why we switched to Rubrik from the other platforms.

We were looking at a way to standardize our data security platform, because we were using a lot of different software, like Veeam, Aranda, HPE Data Protector, etc. In total, it was something like six or seven different backup solutions. It was completely scary to manage on a day-to-day basis. Depending where in the world that we needed to do backups, it was a different software. 

It was completely crazy to manage, not only because you needed specific knowledge of the product, but also because every product didn't have the same behavior and capabilities. This was one of the many issues that we had. Then, we decided to standardize into a common platform everywhere, and that was why we switched to Rubrik. 

The main driver was to find a way to back up over where Nutanix stressed us, because we are a Nutanix customer. At that time, not many vendors were able to protect Nutanix AHV workloads, but Rubrik was one of them, and we decided to do a trial with them. It was absolutely successful in each aspect. It was easy to use and efficient. You didn't need to worry about our restore tests, which were very easy. So, the use case that we have was to protect our Nutanix workloads and SQL DBs. Also, the flexibility that Rubrik has given us is absolutely crazy.

We wanted to get away from tapes. We tried Veeam but it did not work very well for us. There were a couple of shortcomings which we couldn't maintain, plus it wasn't cloud-ready at that moment, at least not to the extent that Rubrik was.

Rubrik was very fresh in the market at that time, but it was bringing features that we were looking for. We were already set on using either Azure or AWS and it had the needed support for them.

Prior to Rubrik, we used Veritas NetBackup for the backup and CommVault for the tape system. We switched to Rubrik because our success rate was poor. The restore rate was horrendous, especially when we had to go to the tape system. it was hovering around a 75% success rate.

We came from an old IBM solution that was complex. 

Prior to Rubrik, we were using the Unitrends solution for our backup. We switched because we couldn't depend on the Unitrends product. It was missing backups, for example. There were some times where every day, every week, five days a week, we'd spend a couple of hours a day, or maybe an hour a day, in Unitrends trying to get backups to run because they would miss a whole set of SQL servers or miss VMs.

We also couldn't do cloud archiving with it. It just wasn't capable of that.

I think we had outgrown the Unitrends solution. I think Unitrends is great for a small company, but anything small to medium and larger, Unitrends just isn't a good solution.

It seems like a very traditional backup solution. It's not forward-thinking and innovative and new like Rubrik is. So, we just knew that we needed something that we could depend on because, with Unitrends, we knew that if there was a disaster, we couldn't recover and so that's why we started looking at something else. We were very happy when we found Rubrik. It restored the peace of mind that we didn't have with Unitrends.

We had Commvault and NetBackup before. Both of those were based on costly consumption-based licenses, and our CIO really disliked that model. The licenses that we had had been increasing in cost year after year and it just wasn't feasible to keep two separate products that weren't a good fit for the automation piece, for hybrid cloud. And they were on a slightly more pricey model. So rather than going to one or the other, we went out to see if there was anything that made more sense at the time. And that's when we found Rubrik.

With Rubrik, we have an agreement where it isn't license-based, and we are able to add more Briks as needed and more clusters as needed. It makes it extremely easy to expand our backup environment as the need arises.

With the other models out there, you would buy one quota and then you would hit it and prices would change and other things would happen. They have you locked in, no matter what. It was basically a situation where you had to pay whatever price they said you had to pay. With Rubrik, it's been very nice to have all of the equipment in our own data center and to have a little bit more control. For example, if we think we're going to need this much next year, this is what the hardware cost is going to be, and we can pay for any additional capacity that we need. That's been really nice with Rubrik.

We had Veeam before this, and we've also had IBM TSM, Tivoli. We've also used a couple of other solutions out there.

We switched because the cost of Veeam was too much. After 200 core licenses, the support cost was almost the same as buying Rubrik for the first time.

Before we had Veeam, we were with Dell EMC Data Domain storage.

We previously were a Veeam customer. With Rubrik, we could replicate directly into Azure. That released the operational costs of having a third-party hosted solution offsite. We have been able to remove that, managing it directly in Azure.

We switched from a different solution to Rubrik because of better performance during the restoration. With our previous solution, backup was quick, but restoration took time. Since we experienced the Live Mount in Rubrik, we decided to go with it.

We previously used Commvault. It was a pretty complex setup. There were a lot of hardware, servers, and issues that were hard to troubleshoot.

Previously, we used to have Dell EMC Avamar and we were running into a problem where the backup jobs would conflict with each other. Now, Rubrik does that for us and fixes it. Not only that, but we're uploading to Azure as well. This means that we didn't have to worry about that part and how to configure it. It can be a complicated process, but the Rubrik software made it simpler to do and easy to manage.

This is one of the reasons that we switched to Rubrik.

We also have EMC Isilon, and the backup jobs were taking far too long to complete. It would take days and with Rubrik, there was a significant improvement. I would estimate a 40% cut in the time required to complete a backup.

We previously used Tivoli Storage Manager (TSM).

We used Commvault. Commvault had started to become a little bit cumbersome when it was time to do upgrades. We had all physical servers from Commvault. We had 12 media agents, and at the time of upgrade, we had to individually upgrade all 12 media agents. So, upgrading with Commvault was a two-week project for us, whereas upgrading with Rubrik is a two-hour project.

I use a lot of different backups. For example, NetBackup from Symantec. The main difference between that and Rubrik is that Rubrik is policy-based, so it's easy to apply.

NetApp is very hard to configure. You would need a full-time employee just to manage and configure backups. With Rubrik, it's pretty much plug-and-play, so that's a big difference. And it works both in a physical and virtual environment, so that's another advantage.

We previously used the latest backup restore capabilities offered by Microsoft SQL Server. We used our custom scripts and methods to perform backups and restores. We switched to Rubrik because we wanted a uniform backup restore solution and more advanced data protection against ransomware attacks. With Rubrik, we can safeguard our data more easily than our old custom backup solution.

Prior to using Rubrik we used NetBackup onto tape, and we used a bit of StorSimple as well. It used to take us six days and 23 hours to back up on those, as a full. We only had just just enough time in a week to fit it all in and then we had a very small window to change the tapes and start it off again. That was an ongoing problem we'd always had so it needed very close monitoring. If backup jobs failed it was always hard to work out why. And we had the whole tape-changing piece as well. In addition, StorSimple was quite expensive. 

Rubrik reduced our backup costs and our backup time. It increased our snapshot position as well, because we're doing incremental forever. It just made the whole process so much more efficient.

We had been using ARCserve for about 18 years before we switched. Sometimes it's referred to as CA ARCserve and sometimes just ARCserve. It went through a couple of different incarnations. It got spun off at one point, so it's a hit or miss as to what it's known as.

We decided to switch because our system was way out of date, and in terms of performance, our backups were taking so long that we couldn't actually complete them. The restore time was abysmal. It took days to restore if we needed a large chunk of data. The maintenance of it, in terms of the human capital, was intense. As I said, I was using at least 50 percent of my time per week just trying to make sure that the backups completed, as much as they could, for that week. We were starting to run into the scale issue, where we couldn't back up our data and export it off to tape within any amount of time that was reasonable. 

We were also way out of space. One of the biggest management issues was that I had to keep moving stuff around. I had to arrange things such that, "That job has got to go over here because there's enough room for it. And this job has to go over here because there's enough room for that one." We did a project and we came across Rubrik and it was the best decision that we've made.

We tried Veeam, which could be a valid alternative, except: 

• You still need storage (Rubrik provides a turnkey solution).
• You need a Windows license (Rubrik is Linux-based).
• You still need to manage jobs (Rubrik is SLA-based).

We used many different products before going to Rubrik, including Tivoli and SnapManager, Nutanix Protection Domains, NetBackup, etc. They were all cumbersome and typically a pain to not only set up, but to recover from as well. By switching to Rubrik, we have been able to simplify many aspects of our backup and recovery procedures.

On top of that, we were able to gain back valuable space on our Nutanix clusters, as we were finding in some instances that snapshots were taking up 50% of the available datastores, which we all know, with Nutanix, is NOT cheap. By switching, we were able to gain that space back for VM deployments instead of having to buy additional blocks as the constraint with Nutanix has typically always been the space, not the CPU and memory.

I previously used Commvault and EMC NetWorker. We switched because Rubrik is more affordable and user-friendly.

Before Rubrik we used IBM Tivoli; however, we could never get Tivoli successfully tied into VMware. Tivoli's snapshot technology was a continual failure, and even with the support of IBM, we could not get it working without it causing infrastructure issues to our VMs. This left us in a state where we had no confidence in the ability of the product to actually execute backups or restores.

I played with various technologies. I played with Veeam, Data Domain, Commvault, and Tivoli.

We switched to Rubrik because of the user interface. The other products use the same VSS Microsoft. The only difference between all these backup products is just the user interface, the PowerShell modules, and the reporting that it presents. 

The underlying technology is all the same, whether it is Veeam, Data Domain, whatever it is. The only thing is the compression and the deduplication. 

We were not previously using another solution.

We learned third-party backup and recovery solutions can be good enough to handle and exhaust all our requirements. Instead of starting to build a backup recovery solution from scratch, we explored outside our organization. Now, third-party vendors are very good and intelligent data recovery solutions are available.

We have previously used a backup tool only for virtual infrastructure, as we were migrating to SAP HANA from a virtual environment. We wanted to have a single solution for virtual and physical  environments , Rubrik is helping us in a great way here.

We used Commvault in Canada and in the U.S. we had Dell EMC Avamar.

We switched from them because of the cost of ownership. The complicity of Avamar, the fact that Avamar constantly had software and hardware errors that had to be dealt with support, and the fact that Dell EMC support is horrendous made us switch. They would not take ownership of an issue and work it through to the end. They'd give us a one-word answer. It was a nightmare.

There are not very many pros, as far as staying with the Avamar solution. It's old, it's outdated, it's slow, and it only half works. It's extremely expensive. It takes forever to restore. There isn't a pro to keeping the old solution.

I didn't use Commvault that much. That was our UK team or our Canada team. I couldn't give too many details. I know that it was an older solution as well, and I know that they were having issues with it.

Prior to using Rubrik we used Commvault. We switched solutions because of the features, the simplicity of the product, and its speed. 

I'm spending less time managing the solution. I would estimate that Rubrik recovery testing saves us 80% in time as compared to our prior solution.

We replaced Avamar with Rubrik and it assumed the exact same role that Avamar had. I never got to use Avamar. It was decommissioned before I got to my current company.

When I worked in higher education, because we didn't have a lot of money to buy solutions, a lot of it was open-source. So I was the support and I was the deployment and I was the debugger and I was the guy that had to code all the integration. It was hard for me to have a vision of, and architect, how we were going to use things. Back then, we needed to use something and I needed to make it happen.

So in a lot of ways, Rubrik is my first big, differentiating factor in backup and restore software. It's not like we weren't able to do it at my previous organization, but this is a completely different realm. It's a totally different level with Rubrik. I'm not saying that Avamar wouldn't have been a similar feeling. But I hear what other people on the team who were using Avamar before are saying, and I get the feeling that Rubrik is leaps and bounds better in terms of validating that the backups actually happened and that they're there.

We previously used EMC Avamar. The reason that we switched was cost, maintenance, and customer support.

We have been using EMC for the past seven or eight years, and we have recently started moving to Rubrik. When I calculate the ROI for both, there is a lot of difference, and that's why we started using Rubrik.

We are using Rubrik only for the VMware backup. VMware works fine with Dell EMC Avamar and Rubrik. Our environment also has SAP HANA, Oracle, SQL, but we are not using Rubrik for these. We use Dell EMC NetWorker for these.

Avamar with Data Domain, which was expensive and hard to manage, and had poor product updates.

We used EMC Avamar for many years. Cost and support were key reasons for the switch.

I have also worked with Cohesity, Dell, and Veritas. Cohesity was one of the simplest. It is more user-friendly.

We were previously using Avamar, but we switch because it was too expensive.

We used Veeam and switched because of ease of use and time savings.

I have used many other solutions throughout the years. This one just seemed to be quite refreshing at the time. It seemed to be the most cost-effective with the best support options.

We needed to protect our core applications and virtualized environment, which is what Rubrik did.

We had other solutions before this one. We used Veeam and VMware backups. We left Veeam due to storage management. VMware backups were not as feature rich as Veeam or Rubrik.

Before Rubrik, we were using Cohesity, but we encountered personal issues rather than product-related problems. When Rubrik approached us, we were open to change, and ultimately made the switch based on our positive interactions with Rubrik.

We have used other solutions in the past.

We used a different solution called Legato, which is an old school tape backup solution. We switched to Rubrik because of:

1. Costs.
2. Time.
3. Hardware updates and outdated technology.

Compared to the way that we were previously backing up different files and servers, using Rubrik is as easy as clicking a button, except using dates.

We used Avamar, and it was complicated.

HPE Backup Servers, Dell EMC Data Domain, and Veeam. 

Whilst this solution was effective, it took considerable management to keep it all working. Rubrik's all-in-one approach removed all the complexity.

Yes, we previously used a home-brewed solution that didn't have the scalability that we needed.

Previously, we have used Commvault. It was a nice solution and also effective in deduplication. However, the license renewal costs were similar to 1 box of Rubrik.

We have also used Acronis, but it's not an enterprise-class product and the several issues that we encountered have not been solved by their support. We still use it because of the customer interface and BaaS.

Asigra. Old tech, dated code, poor with virtual environments. Zerto, great product for DR but only works on virtual and you can't keep history (journal) for long.

We used NetBackup in the past but it didn't fit with our new requirements.

Yes, we used VMProtect but had problems with large Debian virtual machines under VMware. Sometimes the virtual machine got stuck with CPU at 100% after removing the snapshot.
This solution has much better backup and restore times.

We used Commvault and Acronis and we switched, the first because of complexity, the second because of unreliability.

We used a combination of Veeam and Micro Focus Data Protector (was HPDP). The scalability of those two products was lacking, and it took a lot of man hours to babysit the products.

Before we began using Rubrik, we used to use HP Data Protector. We decided to switch due to the fact that the HP solution we had was getting to be too old and we realized simply upgrading it would have cost us quite a bit of money.

The old solution we had was using a tape library to backup the data and it took too long to backup all the data on the tape. We were trying to find another better way or faster way to backup our data source. That's why we ultimately chose Rubrik.

We were using Data Protector in the past.

I have used Veritas in the past. We switched to Rubrik because the solution offered more. 

We used Backup Exec and Veeam. We made the switch as we found Backup Exec was slow, unreliable, and difficult to manage. Having two solutions was also not ideal, and Rubrik met our needs perfectly. 

I used to use Veeam.

Yes, Asigra. Switched due to cost, near zero recovery times, and the fact that VMDK restores constantly failed.