As a senior consultant I deal with customers across numerous industries and maturity levels. I am often engaged in conducting risk assessments or gap analysis aligned with common frameworks such as the National Institute for Standards and Technology’s (NIST) Cybersecurity Framework (CSF). Most, if not all, the frameworks have a few controls that focus on the organization’s backup processes and disaster recovery plans.

When the well-renowned Oracle database started penetrating the enterprise, database administrators typically backed up to tape and disk, with the former being the preferred target. To support the various tape and disk vendors in the marketplace, Oracle came up with the concept of a media management layer that allowed vendors to provide front-ends to their tape or disk devices.

Load balancers are an integral component of any production environment. They allow the distribution of traffic across multiple available backend servers so that no single server becomes overwhelmed due to traffic. A load balancer can be configured for workloads running on AWS through the Elastic Load Balancer (ELB) service. At a high level, an ELB consists of 3 main components: AWS offers 3 different types of Elastic Load Balancers.

Rubrik is on a mission to secure the world’s data, and our position as an innovator has been reaffirmed in this 4th consecutive year being a Leader and furthest on Vision in the 2023 Gartner Magic Quadrant for Enterprise Backup and Recovery Solutions. This recognition validates our commitment to helping customers achieve complete cyber resilience.

Most people are under the impression that backing up their data is a one-time event. They save all their files to a designated hard drive or USB stick and consider the job done. This is why many organizations rely on their existing IT department to handle them. But what happens during server failure or if your drive is breached by ransomware? All of your data will be gone in an instant if your team isn’t equipped to stop everything else to address it immediately.

Velero is the most popular tool for backing up and restoring Kubernetes cluster resources and persistent volumes. However, there may be situations where you need to restore Velero backup data without using Velero itself. For example, if Velero is not installed and configured correctly, or if more fine-grained restore control is required. In this post, we will explore how to do this when either Restic or Kopia was used by Velero to store the persistent volume (PV) data.