---
title: "Your Next Backup Refresh Does Not Need Another Box | Blog "
type: "BlogPosting"
language: "en-US"
url: "https://www.commvault.com/blogs/your-next-backup-refresh-does-not-need-another-box"
date: "2026-11-18T17:19:31-05:00"
modified: "2026-11-18T17:25:49-05:00"
description: "Does your next backup refresh require new hardware? Explore how modern backup solutions simplify infrastructure, improve recovery, and enhance data protection."
image: "https://www.commvault.com/wp-content/uploads/2026/04/Thumbnail_Blog-Multicloud-Recovery-2026.png"
authors:
  - name: "Michael Fasulo"
    jobTitle: "Senior Director of Portfolio Marketing, Commvault"
breadcrumbs:
  - name: "Commvault Home"
    url: "https://www.commvault.com/"
  - name: "Blogs"
    url: "https://www.commvault.com/blogs"
  - name: "Your next backup refresh does not need another box"
---

# Your Next Backup Refresh Does Not Need Another Box 

I have been around backup long enough to know how this conversation usually goes. Capacity is tightening, hardware is approaching end of life, and retention keeps growing. So the answer was: budget and buy another box, install it, manage it, and start the refresh clock all over again.

---

That familiar cycle was already expensive and disruptive, and now it is colliding with a new reality: AI and cloud infrastructure are eating storage capacity at an unplanned scale. Hardware manufacturers are taking orders for 2027 capacity, while their largest customers are making commitments that stretch into 2028. The refresh you used to schedule around budget and end-of-life dates is increasingly becoming a question of allocation, lead time, and whether the hardware will be available.

---

The refresh cycle was never a strategy. It was a habit, and the habit just got harder to feed.

---

At Microsoft Ignite, Commvault is introducing Flex Direct to Cloud, a new way to protect on-premises workloads while writing the first backup copy directly to Azure. **Instead of building and operating another backup storage stack, customers get a simpler path from their existing workloads to an isolated, immutable recovery copy on Azure.** No dedicated on-premises backup storage target to buy or refresh. The data path runs on the hypervisor customers already own, management is delivered through Commvault Cloud, and backup data lands in isolated, immutable Commvault AirGap storage on Azure.

---

The idea is simple: keep the applications where they need to run but stop assuming their backup storage must remain beside them, especially when the next box may cost more, arrive later, and restart the same cycle.

---

### A hardware refresh should trigger a bigger question

---

When a storage array or backup appliance reaches end of life, the immediate question is usually, “What should replace it?” I think the better question is, “What do we still need on-premise?”

---

Of course, some recovery requirements still justify a local copy. Tier 0 systems with aggressive recovery targets need data close to production. Sites with limited bandwidth need a different design. But longer-retention copies do not need to consume scarce on-premises capacity for the next seven or ten years.

---

This is not a blanket argument to move every backup to the cloud. Given today’s infrastructure constraints, it is a practical way to decide where each copy belongs based on recovery speed, retention, bandwidth, security, and what your team needs, or is still able, to procure.

---

### Yes, we could always write backup data to the cloud. This is different.

---

Let me address the obvious question. Commvault customers have been writing backup data to cloud storage for years. Cloud as a destination is not the breakthrough here.

---

The breakthrough is the operating model. Historically, moving on-premise data to the cloud meant assembling and running much of the backup stack yourself: management infrastructure, data movement, storage configuration, security hardening, scaling, patching, and policies . The cloud was the target, but the customer still owned the architecture around it.

---

Commvault Flex Direct to Cloud collapses the operating model into three simple steps:

---

- **Commvault Cloud manages the experience.** Teams configure protection, monitor jobs, and run restores through a control plane delivered as a service. There is no hardware to patch, upgrade, or scale.
- **Commvault Flex** provides the on-premises data path. It processes data locally and applies deduplication and compression before data leaves the site. More importantly, it runs on hardened VaultOS instead of asking customers to build the data path on a general-purpose operating system.
- **Commvault AirGap on Azure provides the destination.** The first backup copy lands in isolated, immutable storage managed by Commvault on Azure, without requiring the customer to assemble and operate the underlying cloud storage.

---

That is the difference. This is not simply another connector pointed at Azure . It is a simpler, security-hardened path from the workload to an isolated recovery copy, with fewer customer-managed components in between.

---

During one of our conversations about the architecture, Aung Oo, Executive Vice President of Azure Storage at Microsoft, said something that gets directly to what we are trying to accomplish:

---

*“Organizations are looking to strengthen cyber resilience while managing infrastructure complexity. Commvault Flex Direct to Cloud uses Microsoft Azure to help customers modernize their backup infrastructure and support their data protection and recovery strategies.”*

---

That is really the point. Modernizing backup should remove infrastructure and complexity, not simply move both somewhere else.

---

### A recovery path separated from production

---

The hardware conversation gets attention because everyone understands refresh pain. But resilience is the stronger reason to rethink the design.

---

Attackers target backups because backups are the path back. If production systems and the primary backup copy share the same infrastructure and administrative blast radius, one compromise can put both at risk.

---

Commvault Direct to Cloud does not eliminate the need for sound security practices, but it removes hardware customers would otherwise have to secure, patch, and maintain themselves.

---

For lean IT teams, that is a meaningful change: fewer moving parts, less hardware lifecycle work, and a recovery copy designed to remain separated from the systems it may one day need to restore.

---

### Where I would start

---

The best starting point I’ve seen over the years is tape and offsite vaulting (you know the truck I mean). Get rid of the physical handling, the courier runs, and the vault dependencies, and the case pretty much makes itself. Otherwise, I’d start where there’s already a forcing function. The strongest candidates aren’t hard to spot:

---

- **A hardware refresh is coming.** An appliance or storage array is nearing end of life, and the team doesn’t want to compete for allocation, absorb higher costs, or fund another cycle.
- **Retention has outgrown the hardware cycle.** Data may need to be kept for seven to ten years, while the infrastructure beneath it turns over every three to five.
- **A data center or branch is shrinking.** The business doesn’t want new backup hardware in a facility that is consolidating or operating without local IT staff.
- **Azure is already part of the plan.** Backup is a steady, predictable workload to land there, and you can buy it through Microsoft Marketplace.

---

Not every workload should move first. Start where retention is long, local recovery requirements are reasonable, connectivity is sufficient, and the next hardware decision is already approaching.

---

And before you lock in the next design, ask yourself two things. Does it cover the workloads I actually run, or just one slice of the estate? And whose cloud does my backup data live in, and does it fit how I already buy cloud?

---

### The cycle is familiar. The answer should not be.

---

Your next backup refresh doesn’t have to be another box. It could be the point where you keep the workloads that need to remain on-premises, move their recovery copies to Azure, and step off the hardware refresh treadmill.

---

Talk with your Commvault or Microsoft account team to map your next refresh, identify the right first workload, and learn about early access opportunities for Commvault Direct to Cloud.
