Skip to main content

Hi All,

 

When reading documentation for Commvault CSI Volume Snapshot-Based Backups for the backup process :  Backup Process for Kubernetes (commvault.com)

I can find that : …/…

Backup process creates a temporary pod and mount the temporary Persistent Volume Claim to read the data.

 

I understand that the Persistent Volume Claim is mounted on the CV Pod (temp). But what is the data path for the backup? Is it a egress trafic from CV Pod(temp) to Access Node?  (egress : process of data sharing externally through a network’s outbound traffic from a pod). Could you please explain?

If so, is is possible to use a dedicated backup network between the CV pod and the Access Node?

Thanks in advance for any explanation!

Best regards,

Luc

Hi @luhenn ,

Good day!

Commvault performs backup and recovery control and data plane transfers via the kube-apiserver. Commvault requires no more than 1 millisecond round-trip time (RTT) latency between the access node and the kube-apiserver endpoint.

Ref : https://documentation.commvault.com/2024e/essential/system_requirements_for_kubernetes.html#network-and-firewall-requirements-for-on-premises-access-nodes

Regards,

Sureshkumar S

Hi Sureshkumar,

Thank you! 

So if we set up a dedicated network interface for backup on the worker node, is it possible to change the temporary CV pod so that it can use the dedicated interface to send data to the Access Node (Data Interface Pair for the temporary pod)?

Regards,

Luc

Reply


Terms & ConditionsCookie settings