Tagged in

backup scheduling

Rubrik -  - Do No Harm: How We Schedule Backups Without Impacting Production

Architecture

Do No Harm: How We Schedule Backups Without Impacting Production

One of our principal tenets is to “do no harm” to production systems. The act of taking a backup requires several resources from the primary environment, including CPU, I/O, and network bandwidth. Rubrik’s objective is to minimize the impact to production and VM stun as much as possible. We achieve this for both virtual and physical workloads by using the following three methods: Flash-Speed Data Ingest: One way we adhere to our “do no harm” principle is through a high-speed data ingestion engine that can easily handle large volumes of data. Data enters Rubrik through the flash tier and lands on spinning disks, minimizing the time that we spend communicating with production infrastructure. Policy-driven Automation. The user specifies when and how often Rubrik takes backups by setting up SLA policies to signal the times when production systems have the least load. This SLA-based backup scheduling makes creating a backup faster, taking advantage of idle cycles on a primary system. Intelligently Distributed Workflow Management: Lastly, Rubrik only takes backups when it detects that the production system is not loaded. Users can set thresholds for certain metrics, such as CPU utilization and I/O latency, globally, or on a per-object basis. Rubrik monitors…