Architecture

Rubrik -  - Instant Recovery with SQL Live Mount

Instant Recovery with SQL Live Mount

Rubrik Alta, our ninth and largest product release, expands our focus on creating the complete enterprise data management solution. With this goal comes the need to offer instant data access and recovery wherever that data resides. That’s why we at Rubrik are excited to introduce SQL Server Live Mount, a groundbreaking capability that no other solution has ever offered. SQL Server Support Overview Before diving into our Live Mount technology, it’s important to understand how Rubrik supports SQL Server. Just like many other facets of Rubrik, our SQL support is designed around simplicity and efficiency. To protect databases with Rubrik, the user merely installs the Rubrik connector onto the SQL Server host. The connector is lightweight, requires no restarts upon installation, and will automatically upgrade itself in the future as needed. Once installed, the connector auto-discovers all SQL Server instances and databases on the host. From then on, databases can be assigned SLA Domains, have manual snapshots taken, and be easily recovered. Because our connector is highly integrated within the host, we can use an initial full backup along with intelligent block mapping inside the connector to provide incremental forever backups. This method utilizes the network as efficiently as possible…
Rubrik -  - Scala: Concise, Clean Code for Humans

Scala: Concise, Clean Code for Humans

Let me ask you a simple question: which do you think is a more natural way of thinking? I am going to go home and take a nap. My present location is “office,” and my state of wakefulness is “awake.” I am going to change my location to “home” and then change my state of wakefulness to “asleep.” The answer is probably a unanimous and resounding “the first one!” But when we write code, it is almost always an example of the second one. Here at Rubrik, while expanding the frontiers of Cloud Data Management, we are also passionate about the psychology of programming and shortening the learning curve for new developers. So, we look for innovative methods to reduce the cognitive load that programmers deal with. That’s where Scala’s magic shines! In this post, I am going to walk you through how we leverage Scala’s expressiveness to write cleaner, leaner, and more meaningful code. For this example, we’ll write a simple simulation for modeling backup operations and how they consume space. For starters, let’s simulate, using a toy program, what happens to occupied storage space when we take a snapshot: [crayon-5a1112f7019eb545229418/] No code is done without unit tests, right?…
Rubrik -  - Erasure Coding or: How Rubrik Doubled the Capacity of Your Cluster

Erasure Coding or: How Rubrik Doubled the Capacity of Your Cluster

At Rubrik, we’re big believers in data protection. But until we’re able to take consistent snapshots of our brain state and upload them to the promised hierarchical neural interconnect, we’re going to focus on backing up the more traditional machines — the ones whose smooth functioning will enable this cause. Any complete backup solution needs a distributed, scalable, fault-tolerant file system. Rubrik’s is Atlas, which made the switch from triple mirrored encoding to a Reed Solomon encoding scheme during our Firefly release. To help you understand the motivation behind this change, this post introduces erasure coding and compares the two methods. Introduction Suppose we want to store a piece of data on a fault-tolerant and distributed file system. In this case, the loss of any single drive should not result in data loss. The only way to achieve fault tolerance is through redundancy, which refers to storing extra information about the data across different drives to allow for its complete recovery in the event of a failure. The more redundancy we add, the greater the fault tolerance. However, the cost of redundancy is increased storage overhead. Every file system needs to make this tradeoff between availability and overhead. At Rubrik, the team chose a…
Rubrik -  - Proactive, Real-time Monitoring and Alerting for Customer Engagement

Proactive, Real-time Monitoring and Alerting for Customer Engagement

One of our main values is to deliver world-class customer experience. This entails actively engaging with customers to better understand their needs and to build products with the user in mind. An important tool for this type of engagement is a system reporting framework that allows our software to actively report data and to ensure we take the best possible course of action to continuously improve customer experience and the quality of our product. The Importance of Proactive Customer Engagement While proactive monitoring is not a new concept, many companies still rely on reactive support. Reactive customer engagement is expensive and time-consuming while proactive engagement focuses on non intrusive, metric-based optimizations to the performance of a product. At its core, it emphasizes an ongoing, elevated customer experience. Additionally, a proactive strategy requires cross-functional collaboration to drive success. At Rubrik, we monitor data in real-time and leverage analytics to: Predict customer needs before they even happen Optimize and analyze the performance of our software Alert for abnormal behavior to improve product quality. In summary, it allows us to understand how our services are performing, identify potential areas of risk, and obtain a holistic view on the overall health of our systems…
Rubrik -  - Do No Harm: How We Schedule Backups Without Impacting Production

Do No Harm: How We Schedule Backups Without Impacting Production

One of our principal tenets is to “do no harm” to production systems. The act of taking a backup requires several resources from the primary environment, including CPU, I/O, and network bandwidth. Rubrik’s objective is to minimize the impact to production and VM stun as much as possible. We achieve this for both virtual and physical workloads by using the following three methods: Flash-Speed Data Ingest: One way we adhere to our “do no harm” principle is through a high-speed data ingestion engine that can easily handle large volumes of data. Data enters Rubrik through the flash tier and lands on spinning disks, minimizing the time that we spend communicating with production infrastructure. Policy-driven Automation. The user specifies when and how often Rubrik takes backups by setting up SLA policies to signal the times when production systems have the least load. This SLA-based backup scheduling makes creating a backup faster, taking advantage of idle cycles on a primary system. Intelligently Distributed Workflow Management: Lastly, Rubrik only takes backups when it detects that the production system is not loaded. Users can set thresholds for certain metrics, such as CPU utilization and I/O latency, globally, or on a per-object basis. Rubrik monitors…
Rubrik -  - How We Built More Efficient Data Archival with Cloud

How We Built More Efficient Data Archival with Cloud

The move to cloud is no longer a question of if but rather when. However, enterprises are still confused on how to adopt a cloud strategy within their own environments. As our CEO Bipul Sinha stated at the Looking AHEAD Tech Summit, in order to increase cloud adoption, “companies need to create killer applications to leverage the cloud.” At Rubrik, we create applications that help enterprises transition to cloud seamlessly. The first step in the path is to archive the backups. The challenge of archiving to public cloud is ensuring that data can be pulled down into an on-premises location without breaking the bank or your recovery time objectives. This is where Rubrik works its magic. When Rubrik manages your data, it keeps a record of the metadata that is quickly accessible without data rehydration. You can locate VMs and files instantly with Google-like search. Just type a few letters into Rubrik’s predictive search engine, and you’ll get served results instantly. In this post, I will describe how Rubrik archives data and makes data rehydration fast and efficient. Snapshot Upload We have jobs running per VM that archives snapshots depending on the configured SLA policy for that VM. When an…
Rubrik -  - If I Could Build Anything (Datacenter Edition)

If I Could Build Anything (Datacenter Edition)

As a field engineer at Rubrik and a former customer, I have seen data centers (DCs) containing all types of vendors and products. However, I have never been able to build an environment from a blank slate—or what’s known today as “greenfield.” In this post and subsequent webinar, I’ll explore the characteristics of a greenfield data center using two of my favorite companies and their products. Objectives: As guiding principles, I’m aiming to do three things in each area of the DC: Simplify: Deliver the most bang with the least overhead Soar: Accelerate business-critical unencumbered Shrink: Represent the smallest physical and environmental footprint Below, I walk you through all aspects of the DC, incorporating each of these principles to create simple, modern, and scale-out architecture. Applications and Compute Technology exists to enable business needs. Without the business, the bits, bytes and architectures are fun, but lack a unifying reason to live. Thus, for our purposes here, I’ll assume we’re cutting and pasting a modern, virtualized environment into this ideal data center. It runs services like Oracle, SQL, and Exchange, and holds terabytes of files and application data that are core to the enterprise. Following Moore’s Law, the compute layer has…
Rubrik -  - A How-To Guide on Rubrik’s vRealize Automation Integration

A How-To Guide on Rubrik’s vRealize Automation Integration

As the modern data center becomes increasingly more software-defined, it is critical to select technology platforms that will support this new architecture even if you aren’t providing IT-as-a-Service today. The best way to prepare for the future is choosing to implement modern API driven solutions into your environment that automate consumer-oriented services. Rubrik’s API-First Architecture Lets You “Backup-As-A-Service” The Rubrik platform was purpose-built to address this need. Rubrik is an API-driven solution. In fact, the Rubrik UI is simply a consumer of the underlying REST APIs exposed by every Rubrik system. What does this mean? It means that everything in Rubrik is easily automated by REST APIs. Since just about every automation platform supports RESTful APIs, you are free to use whatever software you like or even write your own homegrown solution for Rubrik. Now you can add Backup-as-a-Service into your ITaaS portfolio! An Example Let’s say you have an Infrastructure-as-a-Service (IaaS) solution in place (vRealize Automation or vRA for example) where users can self-provision systems. You’re still likely using a manual or semi-manual process by which people request data protection for those self-provisioned systems. In a typical workflow, this would be a form the user would submit, and that form…
Rubrik -  - How We Built a Suite of Automated End-to-End Tests

How We Built a Suite of Automated End-to-End Tests

Last week, I covered the importance of quality and why we employed automated end-to-end testing. In this post, I explain how we implement this approach. We do so through a release pipeline orchestrated by Jenkins to efficiently run a large suite of end-to-end tests. These tests leverage our custom testing framework which integrates with support tooling. As we receive customer feedback, we continuously update the framework and test cases to keep up with the latest requirements. Below, I describe in more detail our release pipeline, testing framework, and product support functions that ensure our testing is faster, more efficient, and always high quality. Jenkins Continuous Integration Like many engineering organizations, we use Jenkins as our continuous integration tool. As engineers check in new code, Jenkins is continuously running the suite of tests we built, including both unit tests and end-to-end tests. This allows us to quickly detect and correct issues. Release Pipeline If we ran every full test for every code check in, we would quickly exhaust all our test resources and file duplicate bugs. Although we can easily add more test resources, duplicate bugs waste engineering time by requiring extra triage and diagnosis work. Instead, we define a release…

    Close search icon

    Contact Sales