What is your primary use case for Rubrik?

I use the solution in my company, and we use it to protect our on-prem managed servers from Oracle. My company is trying to back up VMware and VMs, which is the reason why we use Rubrik.

The main purpose of utilizing the product is to maintain immutable backups, protecting our primary data from ransomware attacks. Additionally, it facilitates meeting our restore point objectives (RPO) and restore time objectives (RTO) by centralizing all restore activities through a single tool. This unified approach eliminates the need for disparate backups stored in various locations for different products.

We use the solution for backups. We transitioned from Veeam to Rubrik, and we currently have on-premises backups for production and disaster recovery purposes. These backups are clustered between both sites, with 60 appliances used for backup operations.

Rubrik Cloud Data Management is my go-to backup solution, offering robust security features to ensure the safety of our data.

We're using the solution for backing up email to file servers and for Oracle backups.

We primarily use Rubrik to back up and restore our VMware VMs and our Microsoft SQL databases and also to perform long-term archival.

I use Rubrik daily for streamlined data management. It simplifies monitoring, administration, and security tasks. With easy backup job setups and automation, it simplifies routine operations.

We use the product for backup and disaster recovery.

The solution is used for data center, backup, and recovery. Also, two companies are looking for an ERP solution, a Cyber Recovery Vault.

We predominantly use the solution as a backup system to protect and manage the data. The data is logically air-gapped making the backup immune to malware.

Our primary use case is to back up our physical and virtual environments. The solution is deployed both on-prem and in the cloud. We use Rubrik to protect virtual, physical, and cloud-native environments. The types of systems and applications protected by the solution include VMs, SQL, NOS servers, and Office 365.

I use this solution to back up virtual machines and databases. We started to use Rubrik because we wanted more ease of management and fewer issues on an ongoing basis. The solution is deployed on-premises. We have physical nodes at our main data centers and virtual nodes at our remote sites.

We are able to use this solution to perform HANA backups, full backup integration and incremental backups, log backups, and the file system backups.

I am a reseller and systems integrator. This is used as a backup solution that already has a hardware appliance associated with it. So you don't need to buy a separate appliance from another vendor since Rubrik would already have hardware that's compatible with its backup software.

The use case is for backups of virtual environments, so it covers all IT areas. Whether it's infrastructure, virtualization or database platforms, our organization uses it for backups and storage. The solution is deployed on-premise. The version I'm running is 5.3.1.

I am a reseller in Sweden. Rubrik is a specific backup solution for the environment.

We have been using Rubrik to backup everything in the infrastructure, except the mainframe. For example, we were using it to do our DR, long-term archive, and some surveys on different cloud tiers.

We are using Rubrik for our server backups.

Rubrik is for ransomware and stuff like that. Rubrik Polaris is an application as a service. So it's in the cloud and the version is V 2021817-9. Rubrik Backup and Recovery and Polaris also help in case of recovery to identify ransomware and vulnerabilities. We use it to back up our virtual environment, which consists of VMware, and we have some Cisco HyperFlex appliances there. It's an all-in-one appliance for storage. We just actually started using Polaris just a couple of weeks ago. We primarily use it for reporting. We are not using Polaris for backing up cloud environments. We don't use Rubrik to backup our cloud environment.

Our primary use case is to back everything up. Rubrik backs up all of our servers on a schedule that takes the bulk of every bit of the mundane tasks out of our hands. It automates everything and frees us up to be able to look at issues where something may not have backed up correctly. We can then investigate those servers to see if they need to be updated or if there's a problem. A lot of times, admin will drop new servers out without telling anybody. We have SLA domains set up in order to catch those so that we're not completely caught off guard by them. We can put them in the proper SLA for the correct backup schedule and proper retention if it needs to be replicated automatically right away and from one site to the other. From there, if it needs to be kept longer, it'll go up to the cloud for cold storage.

Our primary use case is on-premises backup and cloud DR. We're using the Rubrik appliance with their CDM technology for our on-premises solution. We are also using their CloudOut technology to leverage their cloud DR as part of their offering. We're backing up Windows infrastructure and on-premises applications such as SQL and Exchange file servers, and we're storing that locally on their appliance. Then, we replicate our environment to the cloud so that in the event of a true disaster, where we lost our physical infrastructure, we'd be able to spin up in the cloud, using their CloudOut technology. This would allow us to be up and running in the cloud until we were able to get infrastructure back online. The environments that we are backing up are physical and virtual. We don't have any cloud-native environments, so we're not doing any cloud backups right now. We use the cloud, although it is a DR target. Our main task is VM backup, which is between 75% and 80%. We have a few physical boxes that we're backing up, as well. For example, I have the actual hypervisors to back up, and then a few miscellaneous other servers that haven't been virtualized. The applications and servers that we protect include Microsoft Hyper-V for our virtualized infrastructure, Microsoft SQL server for the SQL side, and all of the other infrastructure, in terms of applications, that is Windows-based. We are very invested in the Microsoft platform and using Rubrik to back all aspects of that up. We do have a couple of Linux-based services running, but I would say that we're 95% Windows-based, whether that's Hyper-V VMs or Microsoft SQL, or Microsoft file servers or IAS app servers.

We primarily use it for data backup for VMware as well as AIX, which is an IBM platform. We also use it for the value-adds that Rubrik brings, including Live Mount. We are on version 5.2 right now. We upgrade every little while. The version of the appliance is the r500 series. Our environments are virtual and physical. We don't protect anything in the cloud currently. Rubrik protects AIX versions 6 and 7, then primarily Windows and Linux hosted on VMware vSphere. We also do some standalone Linux and Windows boxes. As a subset of the Windows, we protect a lot of SQL Server databases. We do some IBM databases as well, but primarily SQL Server on Windows.

We have the r6000 series as the physical appliance. We also have the Rubrik Edge, which is a virtual appliance, depending where it is deployed. So, we have three strategic data centers where we are placing physical appliances. For test purposes and some branch offices, we are using the virtual appliance. Most of our workloads (98 or 99 percent) are virtual on-prem, then half a percent are physical and half a percent are in the cloud. In the cloud, we have both AWS and GCP, but it is still very light. We are in the process of migrating a percentage of our on-prem workloads into the cloud. We are in a telecom environment, so we have a lot of homegrown applications based on the Linux operating system. We have MSSQL and MySQL as well on the Linux environment. We are also protecting Windows Active Directory. We don't have a lot of proprietary applications, like SAP, but we have Oracle, MySQL, SQL Server, Active Directory, a couple of file servers, and the rest are mostly home-developed applications.

We came from two different systems. We had one product that was for our campus side and a different product for the hospital side. We wanted to bring those together and not have too many products in one environment. Rubrik covers everything in our VMware, for both campus and hospital. It does all of our backups. Anything that gets backed up for either side now goes through it. We were siloed out into many different teams on both sides and we had a backup team on campus and a backup team on the hospital side. When those were brought together, the backup teams were dissolved and they were put into the VMware side where they're now managing hardware and server hardware refreshes. My team is now the storage and backup team and we've taken on that task. Backups are offered as part of pretty much any ticket requesting a new server, for campus or hospital, that is a request for a new server. We spin up the backup at the server creation. Our Rubrik is all on-prem. We back up our VMware environment and we also do a few physicals. We do some SQL and we do some Oracle.

This is our main backup system. All of our VMs, our hardware hosts; everything is backed up using Rubrik. Disaster recovery is one of the options we have explored, so that in case of a big disaster we could utilize their image conversion to run our VMs on AWS, but that is just a proof of concept at this stage. We have tested it. It works. But we don't have a proper plan in place for that. We have only one physical server that we are protecting with it and the rest are all virtual servers. We have around 400 server VMs and all of them are protected using Rubrik. Most of our environment, around 90 percent, is VMware, while 10 percent of our environment is Hyper-V. With the VMs we are also taking backups of our CIFS shares. We have our file clusters running Windows Servers so we are taking backups using the SMB mount. We have NFS clusters as well, for the Linux side, which we're backing up using the built-in NFS connectors. We explored SQL backups, but right now we are using our SQL Server to dump the data and then the files are being backed up. We're not directly backing up SQL using Rubrik.

We are a financial company and we have redundant data centers, with a VMware Metro Cluster staged between the two locations. We have Rubrik running in our data center and it is used for backing up our on-premises infrastructure. We keep the backup of the environment on-premises for two weeks, just to be able to restore in case we lose or corrupt part of the virtual infrastructure. We also send copies of some of the data into the cloud for long-term archiving because we're under a regulatory requirement to store certain parts of the business data for up to seven years. At this point, our environment is probably close to 90% virtual. We use physical servers for market data and essentially, there is nothing to back up on those systems because there's no data that's worth saving there. Should one of these servers fail, we just put a new one in place. It would be deployed, including the operating system, and it would start processing market data for us. We consider these as compute nodes and there is no persistent data on them. We are highly virtualized, so Rubrik is used to back most of the VMs up. We are running VMware ESXi for our VMs, and application-wise, we are a Microsoft shop so we backup SQL Server, Exchange Server, and Microsoft file shares. We also back up a lot of business data, which is contained outside of that server.

We have been mainly using Rubrik's backup and recovery solution for our microservice-based products, which we have for different trading applications. We have a trading application, where the customer makes use of any workflow through the GUI of the trading application. The request goes through our microservices server REST API. These microservices server REST APIs are sometimes using DynamoDB as a database solution. Our applications are quite scalable and user-friendly. We wanted our database solution to be highly scalable. Since all the trades being carried out between customers are highly secure in nature and carry sensitive data, we wanted this in case there was some type of application crash due to a timeout or downtime. Our database should not crash and the data should not be lost. For that purpose, we needed to use Rubrik's backup and recovery solution. So, on a weekly basis, we take regular snapshots of our databases via Rubrik's solution in case of any downtime, especially during the week from Monday to Friday when trading is being done at a high peak level. At that time, we take snapshots. In case there are any issues, then we will simply roll back our database to the previous snapshot which we had captured. We are protecting VMs. They are all virtual.

We use Rubrik for VM backups, NAS backups, and SQL backups. Most of what we protect is virtual. It's AHV and VMware, primarily. We have a half dozen physical machines, but most of it is virtualized. We don't do any cloud-native protection yet, although we're about to start doing Office 365. We have the Brik as an on-prem piece and we offload all our data to Azure.

The primary use cases of Rubrik are to back up critical files, servers, documents, VMs, and partition drives from servers. We protect our Linux and Unix OSs. I am using both their physical appliances and software. We are using it on SaaS.

We have it onsite and in the cloud. We also make use of their SaaS offering as well. Primarily, we back up our VMware estate. We back up Azure VMs and Office 365 as well as some physical boxes. We used to be on r348, so now we're on r6408.

Our use cases are for backing up all critical databases on our SQL servers. It also backs up critical virtual machines in our VMware environment.

We use this solution extensively - it helps with fast recovery scenarios and some ransomware issues. The solution is used by the operations department and I believe there are more than five people involved in maintenance, most are storage or network admins. I'm an engagement architect.

We use it as a backup for our memory store. It protects virtual and physical environments for us, all on-prem. The applications being protected include VMware VMs, Microsoft Exchange, Microsoft SQL, SharePoint, our file services, and operating systems.

This project initially started out as a replacement for our legacy backup system, IBM Tivoli, which was backing up our VMware environment. Since our environment is almost entirely virtualized, protecting those assets was the primary goal. We also knew that we wanted to get to a state where our backups were protected against ransomware via immutability or air gapped backups, which we've now accomplished with Rubrik. Shortly after the initial deployment, we realized the full capabilities of Rubrik. We are utilizing Rubrik's backup integration with Oracle databases and SQL databases. There are several other business critical applications, like Tableau, that are also being protected via Rubrik. Due to Rubrik's ability to execute in protecting our on-premises assets in the data center, we decided to utilize Rubrik's Office 365 and AWS Cloud Native solution to protect our data in the cloud.

We use it for backup and recovery; system protection is an even a better way to describe the use case. We not only have a backup of our data but it also provides disaster recovery. While having your data is important, having the ability to return to production, within minutes of an issue — which means standing up the whole VM at a point in time — is way more important in today's world than it is to just have a copy of your data. It's protecting both physical and virtual environments. It protects Windows, Linux — multiple flavors — as well as Microsoft SQL and Oracle Databases. We have two bricks and we're protecting about 175 machines, both physical and virtual. It has been about 98 percent VMs, and probably even higher than that. We're a VM shop. We are protecting all of our SQL databases with the native SQL tools within Rubrik, through which we can do all of our table restores at a point in time, depending on the database itself. We are using multiple different archives with multiple different SLAs, both on-premise and to AWS. Our deployment of the solution is primarily on-prem.

We use it to back up of all of our infrastructure and file servers. The environment we're protecting with Rubrik is 99 percent virtual. We back up file servers, databases — SQL. Most of them are virtual machines in vSphere. The deployment model is a hybrid where we have the solution on-prem, plus we back up to the cloud, on AWS.

The primary use case for Rubrik is backup and restore and as an archival system. We use it for backup and restore for virtual machines, managed volumes that are mounted and which we use for snapshots from Rubrik to endpoint devices, NAS shares from our Isilon system, as well as SQL databases, Oracle Databases, and Windows and Linux. We may have some failover cluster Windows shares going to it. It's for backups and restores of pretty much everything. It works really well in concert with Pure Storage technology. We have a really large Pure Storage environment and they play really well together. The solution is on-prem and it's protecting environments that are on-premises exclusively at this point, although we have plans to push towards the cloud. Most of it is virtual but I'd be surprised if we didn't have at least half-a-dozen physical machines connected to it.

* Daily backups at different intervals * Audits * Live mounting of production servers * DR We are a 90 percent VM environment. We have a different OS environment, as well as databases.

As a financial company, we are under stringent data compliance, availability, and integrity rules. We use Rubrik to enhance governance of data archiving, as well as the backup and restore production environment consisting of multiple converged systems. We are also looking into the feasibility of using Rubrik as part of the firm's BCDR efforts and enhancement of the development environment.

We are an MSP and offer Rubrik as a backup service to customers on private and public cloud environments and internally managed environments. We run the solution against VMware and Hyper-V with minimal physical systems. Currently, there is no support for image-level backups on systems in Azure and AWS from Rubrik. Presently we use agent-level backups however this is not ideal for fast whole system recovery. The next version (4.2) has support for image backups, and this will be investigated for functionality when released.

We use the Rubrik solution to back up our private cloud environment with hundreds of virtual machines.

We use Rubrik for daily VM snapshots at local sites, but it is also used for replication in our DR sites because Rubrik has the ability to run a VM on its hardware in case of a failure.

We are searching for a new backup product that reduces man hours and helps us automate more of the backup and recovery process for our MSP team.

We use this solution for IaaS customer environment backup in cloud and for internal purposes. We're planning on offering a GUI to the customers so that they'll be able to restore by themselves.

We use Rubrik as a secondary recovery method for our Tier 1 applications and the primary recovery method for our Tier 2 and below applications.

We use it to backup our virtual machines, specifically file-based backup and backup of our SQL Database. We also use it to archive data on NFS Share and the cloud.

We were operating more than 10 different backup products company-wide and none of them were doing the job correctly. While reviewing the market, I found Rubrik. They were small at the time, and have since acquired a lot of credibility. The first PoC was a real success. We decided to start with them at the end of 2017. We were amazed by the product's simplicity and performance.

We use it for backup and recovery of VMware servers, physical Windows servers, SQL Databases, and Microsoft Exchange.