General Tech

Rubrik -  - Understanding RPO and RTO

Understanding RPO and RTO

As enterprises utilize more and more business-critical digital services, information technology infrastructure and applications have become key strategic imperatives. Downtime and data loss translate to a huge business and financial impact that  must be minimized with an effective data protection strategy. When planning for a data protection strategy or a disaster recovery plan (DRP), there are several criteria to consider in order to align with the business impact of various applications and workloads. A Business Impact Analysis (BIA) can help assess and weigh the impact and consequences, both financial and non-financial, of an interruption in business operations. These findings can help organizations determine their availability Service Level Agreements (SLA), or the level of service expected by the customer from the entity that provides the service. Most often, multiple SLAs are defined to match the various levels of criticality that were determined during the BIA. For example, the following SLAs are commonly utilized: 99%, or two 9s, corresponds to 3 days 15 hours and 36 minutes of downtime per year. 99.9%, or three 9s, corresponds to 8 hours 45 minutes and 36 seconds of downtime per year. 99.99%, or four 9s, corresponds to 52 minutes and 34 seconds of downtime per…
Rubrik -  - Tips for Migrating Your App to the Cloud

Tips for Migrating Your App to the Cloud

In this age of falling cloud computing costs and hybrid cloud infrastructures, many businesses are trying to find a path to migrate their apps to the cloud. There are a myriad of reasons why app migration is top of mind: Potential cost savings Disaster recovery uses App refactoring or modernization Access to burstable resources Integration with SaaS platforms or new cloud-based tools (e.g. Amazon RDS, Azure App Services, and Google Cloud Spanner) In this blog post, I will explore some of the concepts and requirements needed to migrate an app from an on-premises data center to another location. This secondary location is typically a cloud provider, but many of the concepts apply when moving to a DR site, or even a developer’s laptop. In our example, we’ll use one of the most ubiquitous three-tier apps available: WordPress. The diagram below describes the components of our app. Understand Your App Let’s be honest—apps can be complex. If you’ve amassed technical debt in regard to documenting your apps or have little understanding of how they connect with other apps or business processes, you will have some homework to do. You’ll need to document and fully comprehend all aspects of your app, including:…
Rubrik -  - How to Get Started with Open Source Projects

How to Get Started with Open Source Projects

So you want to start dabbling in open source? There are tons of reasons why contributing to open source projects is a rewarding use of time–from advancing your career to supporting a community you like. But contributing to an open source project for the first time can be incredibly intimidating. Like many, I was apprehensive about contributing to open source projects at first. I kept putting it off, thinking that I would eventually help out when I had more to offer. But you don’t need to be an expert to support an open source project–you don’t even need to write code to be a contributor. The opportunities are often quite broad and many communities, like Rubrik Build, accept code and non-code contributions. Here are some easy ways to get started with open source: Join the Conversation The simplest and fastest way to get started with open source projects is to contribute your thoughts. No code required! Join in the conversation and offer your experience or use cases. This can be done with Slack conversations or providing input on issues associated with projects on GitHub. Alternatively, start the conversation by filing an issue for a project. Tell us if something isn’t…
Rubrik -  - How to Throw a Disaster Recovery Tabletop Workshop

How to Throw a Disaster Recovery Tabletop Workshop

Ransomware and destructive malware. You either groan with media fatigue or cringe at the thought of getting blown off the map by bitcoin bandits…perhaps both. For many organizations, creating a multi-leveled disaster recovery plan to accommodate this potential threat is now a top priority. The problem is, many organizations create a DR plan but don’t test each year. It’s easy to procrastinate DR testing, as it’s a costly activity in terms of both hours and infrastructure. But failure to test in a complete and realistic scenario can leave an organization woefully unprepared for some of the ancillary activities like communication and ownership of action. Essentially, the first time the crisis team meets should never be during a crisis. Simulating an attack around a table with a few colleagues doesn’t replace live testing, but it does uncover things you may not otherwise think of. This blog series will help walk through the setup and execution of a tabletop exercise for testing your DR plan. In true RPG style, this post will show how to simulate an unfolding disaster and apply your DR strategy in response. The advantage of running a tabletop exercise is its lightweight impact in terms of time and…
Rubrik -  - Using Automation for Faster Cloud Adoption

Using Automation for Faster Cloud Adoption

Most work conversations I’m involved in go something like this: blah cloud adoption blah agility blah. It’s true that public cloud provides an innumerable list of benefits, but to me, the most attractive aspect is a uniform, API-driven method of provisioning resources. This makes it inherently automatable, unlike so many frustratingly simple and tedious data center tasks. I always encourage organizations to use cloud as a gateway to automation. There are two primary avenues for automation: infrastructure provisioning and application-delivery aspects of the business. While easy in concept, automation requires a lot of initial investment before its value is returned. I like to start with focusing on the management aspect and automate most of the back-end operations tasks. For example, my team often builds and destroys Rubrik Cloud Cluster deployments as part of our testing, so this is something that made sense to automate. Across the team, some like to use automation tooling such as Terraform, while others prefer native template tools like AWS CloudFormation. We’ve made these use cases available on Rubrik Build so that you can use some of the same tools that we use internally. Terraform Modules We previously announced the Rubrik Provider for Terraform, which simplifies…
Rubrik -  - Extending Cloud Data Management to vCloud Director Tenants

Extending Cloud Data Management to vCloud Director Tenants

Last year, we proudly announced support for VMware vCloud Director and today, I am excited to further advance our integration with the Rubrik Extension for vCloud Director. Rubrik’s support for vCloud Director delivers simple and flexible multi-tenant self-service management. Our new plugin gives tenants the power to self-serve the same functionality that providers already enjoy from the vCloud Director user interface.   As of 9.1, the vCloud Director user interface (UI) plugin management allows for integration of custom, third-party modules directly into the context of the vCloud Director interface. This means that ecosystem partners, such as Rubrik, can integrate into vCloud Director by customizing the UI based upon HTML5 standards using Angular and Clarity. Once the Rubrik Extension for vCloud Director is installed, the following actions can be made available to allow for tenant self-service: On-demand Snapshots Assign SLA Protection Recover vApp File Recovery Export vApp Credential Management The following image demonstrates some of the Rubrik functionality available from the tenant: By leveraging the plugin registration process that is built into vCloud Director, service providers can dictate whether the plugins should be available to the provider portal or to the tenant portal. Additionally, the service provider can provide granular control…
Rubrik -  - How to Not Be A Victim of Infrastructure with Rubrik Live Mount

How to Not Be A Victim of Infrastructure with Rubrik Live Mount

Since day one, Rubrik was built with the user in mind, delivering ultimate simplicity and comprehensive data protection at enterprise scale. That’s why we leverage our own platform to manage and protect our mission-critical data, allowing us to experience firsthand how our technology accelerates product development and automation. However, just like any other organization, we at Rubrik are still susceptible to unpredictable hiccups and disasters. We recently encountered one of these issues during a product release cycle. With Rubrik, we were able to quickly meet our time-to-market goals and minimize business disruption and engineering productivity loss. Here’s our story of how Rubrik came to the rescue: At Rubrik, one of our core values is velocity, and that applies to our engineering teams as well. Our engineering teams use our home-grown orchestration layer to allocate precious infrastructure resources for functional/integration and regression tests, which enables us to deliver quality product at lightning speed. This orchestration layer and its services run on top of an enterprise SAN (hybrid flash-based array) for storing the test data and builds. However, recently, this storage layer behaved erratically, significantly slowing down our build times and release pipelines. Our IT infrastructure teams came to the rescue, quickly…
Rubrik -  - Scoping the Options for Your Cloud Disaster Recovery Solution

Scoping the Options for Your Cloud Disaster Recovery Solution

“Starting off, all options are always open, but as soon as you choose something, you inevitably limit yourself. If you go for B, A is out.” – Alva Noto, Musician and Artist For many of us in IT, we’ve operated under the mindset that our disaster recovery plan will save our bacon when an unfortunate incident hits. However, this attitude neglects one of the essential acts of due diligence that is incumbent for every DR design: continually evaluate and implement new and better options to ensure a solution is effective in the cloud era. Even if you are just starting to create your DR plan, it’s important to have a wide-windshield view of the offerings that cloud technology and different cloud providers can give you. Here are the ones that I will focus on in this post: On-premises to co-location or private cloud On-premises to a Managed Service Provider (MSP) or Cloud Service Provider (CSP) On-premises to multi-cloud (public and private) On-prem to Private Cloud Most traditional DR plans employ the warm/cold-like co-location design that sources the data in one data center (DC) the company owns and recovers in either another DC owned by the company (hopefully in a different geo…
Rubrik -  - Planning a Successful Disaster Recovery Strategy

Planning a Successful Disaster Recovery Strategy

Here at Rubrik, we strive to provide a strong suite of tools that make backup and disaster recovery (DR) as easy as possible. We’ve developed technologies like Live Mount, CloudOut, and CloudOn to help businesses recover quickly from a disaster and minimize downtime. In my experience, technology—no matter how advanced—is only a piece of the DR equation. A fully developed DR plan requires people, process, and technology in order to truly be successful. Here’s a look at some of the top considerations when developing your DR strategy: People First and foremost, you must have the right stakeholders and executive sponsorship sign off on your strategy so that they can go to bat for you when allocating people and resources. Successful DR planning requires time and input from many people across your organization—the larger the company, the more people involved. Your team should be representative of all key areas of your company, with smaller groups concentrated on logistics and operations where necessary. Here are some examples of how to effectively make up your team: Business Unit Stakeholders: Identify critical applications, success criteria, and potential roadblocks. Provide input to other teams as needed. Application Owners/Analysts: Own dependency mapping and success criteria for…