All posts by user


Rubrik (Swedish for New Standard) is a web scale, appliance-based, data backup and recovery platform started by Bipul Sinha and Arvind “Nitro” Nithrakashyap. This appliance is called a Brik. It consists of 4 dual processor compute nodes (commodity) in a 2U chassis. Each node can provide up to 30k IOPS and 1.2 GBps of throughput. Each node consists of 1 SSD and 3 HDDs. The most dense config currently provides 30TB of raw capacity. Compression (Inline), Dedupe (Inline and Global), and encryption are supported and they average about 75-80% data efficiency in the field. Extraction of snapshotted data is nearly instantaneous thanks to some proprietary algorithms developed around flash architecture parallelism.

Backup software that handles catalogs and data movement runs natively on the platform saving organizations money on 3rd party backup software such as Commvault or Veeam.  No additional servers to run that software are required either. No additional storage device. Generally, you buy some software, some servers to run it on, and some storage to send the data to. This is all that in one…and then some.

Another big difference with this solution is the elimination of the RTO generally associated with restoring from backup or even the time spent making your remote replica writable. This appliance basically makes your backup device act as a primary storage device until you can get your primary storage back online and ready for a migration of the data back on to that primary storage. Are we allowed to say Hyper-converged?

Leveraging policies (instead of traditional jobs) along with a resource scheduler and algorithms developed in house that optimizes data extraction, they are able pull data using VADP and CBT with minimal impact to the production environment. Using the SLAs and policies, data can then be moved off to an object storage solution (think Amazon but many are supported). They claim that it virtually eliminates your RTO since recovery simply means bringing up the VM or SQL DB in the remote location. This would be done with the data living on the Rubrik itself until the data can be moved (vMotioned) back to primary storage.

One other cost saving feature is the indexing of all snapshot data. If a single file is needed for a restore (say a 50 GB MDF), but it lives on a volume that is 400 GB and contains other data, instead of incurring the cost of the 400 GB transfer out of <insert cloud storage provider here>, you only incur the cost of the 50 GB MDF. This is also possible with a single file restore out of a VMDK.

Hardware Summary:

2U “Brik”

4 Dual Proc Nodes per Brik

30K IOPS per Brik

1.2 GBps throughput per Brik

30 TB RAW (most dense config)

Scales to over 40 nodes easily

Software Summary:

Web-Scale architecture

Atlas Scale Out file system


Global Inline Dedupe


Single File Restore

Supports all cloud providers and object stores


Throughout my career I have been on many interviews and interviewed a few as well. I realized quickly that its about your mind more than it is about your brain. One interview stuck in my head. I was the one being interviewed. Best interview ever. I replicated that interrogation method when hiring my teams and the folks that were hired as a result of that process, flourished. They all went from generic break/fix Sys Admins to well respected architects and directors/VPs in our industry.

As a systems engineer, we are required to have to have technical prowess. We should know how to navigate our way through some pretty challenging scenarios. Quite often, its under a tremendous  amount of pressure (“get the site back up, we are losing 1000s of dollars every minute!”). Any engineer that has been in the trenches knows what that feels like. They also know how many things are learned…and eventually forgotten. Nobody knows it all. We have all discovered a lot, resolved complex issues as a direct result of our better than average reading comprehension skills, potentially picked up some “good habits” along the way, and again, probably forgot a lot of the minutia involved in resolving the issues. The more of them we fix, the more we realize the minutia is unimportant. Do you remember the KB/TR  number of an issue you fixed 3 years ago? Probably not. However, we all remember how DNS works all the time though, right? Well yes…because that’s fundamental to computing. See my point?

I recently interviewed at a company and was mostly embarrassed at the questions I was being asked. This is a very well known company with a market cap in the billions and growing every day. The position was a middle manager of systems engineering. Nothing I couldnt handle. Unfortunately, two minutes in, I felt like I was 25 again trying to get a job as a desktop support guy when the questions began. No matter how well I did, I didnt want this job.

My point here is that the questions that are asked during an interview process are crucial to the level of talent that is acquired. Be smart with them. A lot of times, the question will be, “what are the 7 layers of the OSI model”. Bad question. Why? You end up with a guy that knows how to memorize things. It has no reflection on the candidates critical thinking skills. Going back to my “best interview ever”…what was the question that was asked that gave me the ability to showcase my talent?

“Tell me everything that happens between the time you type in ‘’ in your web browser to the time you see the logo and search box”.

Bingo. He not only was able to determine that I understood the OSI model, but that my understanding of applications, proxy servers, DNS, html, tcp/ip and web servers (“the internet”) was up to snuff. I understood the order of operations and clearly, my troubleshooting skills would allow me to isolate and pinpoint the problem. Memorizing the layers of the OSI model doesnt really help you figure out why users cant get to the application.

As an interviewer, dont play Jeopardy with your candidates. As an interviewee, if you see someone playing Jeopardy during an interview, keep faith that you are a professional with industry standard skills and talent. Not knowing the specifics of a google search which enlightened someone a few days prior, doesnt make you a bad candidate. It just means they have an amateur hiring manager without any vision or leadership skills. Keep searching for someone that values your mind.

Good luck out there.




Journey to the Cloud

This is my second shot at hosting my blog “in the cloud”. I ran my own infrastructure for quite some time out of my garage. I decided it was too much to maintain on a daily basis when I had kids. I moved some “services” and sites off to vCloud AIR at some point a couple of years ago and after a painful experience, decided to give the industry some time to mature. So I am back at it. So far, my experience with Lightsail is going well.

UPDATE (8/6/2018):

My journey to the cloud is in full swing. While my blog is still hosted on a lightsail instance, my www/homepage is on an EC2 instance, using S3 and Cloudfront for storing/serving images and other static content. I have also created a code deployment pipeline and am using tools like GitHub, Jenkins, and VisualStudio Code more than I ever thought I would. I have created some automation scripts to promote my code from dev (local) to prod (aws) and have plans to introduce configuration management to my environment soon along with additional security measures  (IAM) and building a DB-driven application and perhaps messing around with MicroServices at some point. So far the experience has been great. Its nice to click around and get whatever I may need deployed quickly. The monthly bill completely stinks though. Ill have more later but wanted to provide an update on my “Journey”. Cheers!