Skip to main content
commvault.com commvault.com

According to documentation, both azure files and azure disk supports snapshots of filesystem.

https://documentation.commvault.com/2024e/essential/system_requirements_for_kubernetes.html
But I’ve tested the backups of AKS now with two different clusters. and both of them defaults with an warning in the log:
Will be mounting live volume epvc] to worker pod dcontainer] since it does not support volume snapshots

Are there any other configuration that needs to be made to ensure azure files uses snapshots?

 

Regards,

John Robert

Hi ​@John Robert 

 

Did you perform the steps in the validation page of the documentation? - Ref: https://documentation.commvault.com/2024e/essential/validating_your_kubernetes_environment.html

 

I’d suggest validating the following: 

 

In order for the Container Storage Interface (CSI) driver to perform provisioning, attach/detach, mount, and snapshot activities, CSI drivers must be installed, functioning, and registered, and they must support the Persistent mode.

kubectl get csidrivers

 

The PersistentVolumeClaims (PVCs) that you want to protect must be presented by a registered, CSI-enabled StorageClass. Verify that the StorageClasses that have PersistentVolumeClaims that you want to protect use the Container Storage Interface (CSI).

kubectl get storageclasses

 

After installing a CSI driver, you can verify that the installation was successful by listing the nodes that have CSI drivers installed on them.

kubectl get csinodes


A CSI-enabled VolumeSnapshotClass is required for Commvault to orchestrate the creation of storage snapshots. Verify that your environment includes a VolumeSnapshotClass that has a CSI driver.

kubectl get volumesnapshotclass

 

If you have the VolumeSnapshotClass present, run a “kubectl describe volumesnapshotclass volumesnapshotclass_name” and verify that your installed external-snapshotter supports the snapshot.storage.k8s.io/v1 API.

 

Best Regards,

Michael

 

​@MichaelCapon Thanks. I read it a little to fast, and skipped a step. It was the missing volumesnapshotclass that was the culprit for azure files. 

Still makes me curious, why do we need it for azure files, but azure disk seems to handle it without an snapshotclass?

Reply


Terms & ConditionsCookie settings