Tagged in

Compliance

Rubrik -  - Top 3 Mistakes to Avoid When Automating Your Business

Business

Top 3 Mistakes to Avoid When Automating Your Business

Businesses worldwide are leveraging automation to deliver services at a lower cost with a higher level of customer satisfaction. The return on investment for automation is well documented, both in financial benefit and higher customer retention rates. But not all efforts to implement automation are created equal, and many companies stumble to meet their goal. Integrating automation into a business requires planning and strategy. This post walks through the top pitfalls to avoid when implementing automation. Recreating the Workflow The first mistake many businesses make is automating the steps of an existing workflow. This may seem like a shortcut since the workflow provides a blueprint for the steps needed to achieve the end result. But workflows created around manual processes focus more on previously performed tasks than on the entire problem. I experienced this firsthand while developing a process to automate billing based on cloud usage. The existing workflow had many steps that required manually altering the output of the previous step and reformatting it before sending it to the next person in the chain. This process created a significant margin of error, as even minor changes caused the entire chain to break. This leads to our next major pitfall.…
Rubrik -  - Let’s Talk About Security

Product

Let’s Talk About Security

Today, Rubrik announced the r528, the industry’s first security-enhanced converged data management appliance. So, let’s talk about security. Not just the kind that you set in place to keep your actual devices safe, but also what you do to protect the data on them. All of your data. Including your backups. Remember when one of the largest regional banks in the United States “lost” computer back-up tapes containing personal information including social security numbers and bank account information for over 260,000 of its customers? That was in 2012. With the amount of digital data generated annually projected to grow to 44 ZB (1 zettabyte = 1 trillion gigabytes) by 2020¹, and a growing trend in data breaches, it is even more imperative to apply the highest security standards to all of our data, even backups. Often times we think of data security as something applied to the information generated via transactions. We encrypt data in-flight to ensure data is secure against eavesdropping or manipulation as it travels across a network. We even put in place checks on data in our primary systems to ensure the data we really care about can’t be hacked into. What about data that’s been backed…
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…