Tagged in

RPO

Rubrik -  - The Challenges of DR: Achieving Near-Zero RTO

General Tech

The Challenges of DR: Achieving Near-Zero RTO

As the Director of Sales Engineering at Rubrik, I am privileged to meet many customers across different geographies and all verticals. I witness a variety of challenges, but there are some common themes. One challenge nearly every customer battles is how to effectively manage disaster recovery (DR). To provide disaster recovery, businesses often utilize several options, including various forms of replication (array based, application based, hypervisor based), DR automation tools (i.e. VMware Site Recovery Manager), and backups. These approaches are typically costly and complex; they require similar hardware at Production and the DR location site, and users must manage multiple tools. A good DR plan provides multiple layers of protection from a myriad of failure types. This can be accomplished with tools such as snaps, data replication, and data protection. Rubrik can play a key role in your DR plan. With our solution, customers reduce their RPO to 1 hour and achieve a near-zero RTO. Rubrik leverages components of a modern data center like converged architecture, flash, and deduplication to efficiently replicate data from Brik to Brik and instantly recover VMs. Each Brik provides 30k IOPs, which allows workloads to temporarily run directly from Rubrik until production issues are rectified.…
Rubrik -  - The Interesting Challenge of Backing Up NAS

Company

The Interesting Challenge of Backing Up NAS

Rubrik is pleased to announce support for Network Attached Storage (NAS) backups such as NetApp and Isilon with our 3.0 Firefly release. Given that NAS support is one of the most common customer requests in 2016, we are offering an innovative solution for managing NAS data that provides faster Recovery Point & Recovery Time Objectives (RPO & RTO), incremental-forever backups, and cloud archive capabilities. We’re delivering these capabilities without sacrificing storage efficiency or tying the customer to a complex NDMP-based (Network Data Management Protocol) solution. What makes NAS backups so difficult? Two characteristics make NAS backups difficult:  Agents – It is impossible to install an agent since NAS is sold as an appliance.  Dataset Size – NAS systems and datasets have grown in size with the industry. When NDMP was first introduced, a very large NAS dataset might have been 10 TB. Today, NAS datasets typically tend to be huge, running into 100s of TBs or PBs. For these reasons, traditional backup vendors using ancient approaches like NDMP have failed to keep pace in providing fast, incremental-forever backups with efficient storage usage and short RTOs. What are the advantages and differentiators of our NAS approach? Vendor Agnostic – Our approach works with all…
Rubrik -  - Managing and Monitoring SLA Domains at Global Scale

Architecture

Managing and Monitoring SLA Domains at Global Scale

In my previous post, I went into the complexities that funnel into building Service Level Agreements (SLAs) that exist between consumers and providers of an IT service. This friction can be greatly assuaged by decoupling the agreed upon policy’s intent from the actual execution of backup jobs. It allows administrators to abstract away much of the low-end fuss required to build and maintain data protection, instead focusing on adding value at a more strategic level across the organization. Let’s now move the story forward to discuss how consumers can easily determine if their SLAs are being honored. At a high level, SLA Domains are constructed using Recovery Point Objective (RPO) and retention values. The RPO is essentially asking how much data loss the consumer is willing to tolerate, while the retention input determines where the provider will store data (on-premises or elsewhere). To understand SLA compliance, it’s important to look at the entire set of backup jobs to ensure all facets of the RPO are being met for an application. This goes beyond looking at the number of total backups held by the system, as an RPO is often expressed as a quantity of hourly, daily, weekly, monthly, and yearly…
Rubrik -  - Decoupling Policy from Execution with SLA Domains

Architecture

Decoupling Policy from Execution with SLA Domains

Successful enterprise architects are able to pull functional design elements from key stakeholders to abstract requirements, constraints, and risks. Much of this work involves translating business needs into technology decisions and then deciding upon the right vendor solutions to provide for the design. In this blog post series, I’m going to focus on addressing Service Level Agreements (SLAs) to ensure that the business is equipped with the runway it needs to tackle operational challenges and protect applications. Many organizations that I’ve consulted with were forced to take a good, hard look at their SLAs (or lack thereof) in order to craft a strategic plan for the future. At the heart of any quality SLA is fairness. Both parties – the consumer and the provider of a service – must agree on a mutually beneficial statement for long term success. The end goal is to abstract the minutiae of a technical design away from the consumer. Such as this WordPress platform: I really don’t concern myself with the back end infrastructure, I just want to consume the service and know that it’s being protected. An SLA is a method for me to define guard rails around data loss and availability while…