Still Restoring Entire VMs Just to Get One File Back? KubeVirt + Kasten v8.5 Fixed That

🔍 File-Level Recovery in Kubernetes with Veeam Kasten v8.5

The question I hear most in real-world Kubernetes projects:

"Do I really have to restore the entire workload just to recover a single file?"

For a long time, the honest answer was "yes, or pretty much." With Veeam Kasten v8.5, that changed.

🧩 Why is FLR in Kubernetes different?

Persistent volumes can easily be tens or hundreds of GB. Restoring an entire PVC just to get one file back isn't viable in production, especially in KubeVirt environments where VMs share namespaces and dependencies get complex fast.

✅ What's new in v8.5?

Previous versions required Veeam Backup & Replication (VBR) as an export destination to enable FLR. Now it's fully native, you remotely mount individual PVCs directly from a Kasten restore point, browse the filesystem, and recover only what you need. No full data copy back to the cluster. No VBR dependency.

Supported filesystems: ext4, XFS, FAT, and NTFS, covering both Linux and Windows workloads, for containers and KubeVirt VMs alike.

🔗 Bonus: Restore Point Validation 😎

Before doing an emergency FLR at 2AM, you can now validate that your backup is actually intact, full checksum verification included. No surprises when it matters most.

The granularity we've always had in traditional Veeam environments has finally arrived in the cloud-native world natively, without workarounds.