You must have at least one access node for Kubernetes. For faster backups and restores, you can add more access nodes.
Network interface for backup data
Scale the Kubernetes access nodes horizontally for consistent scaling and performance.
For resilience scaling, add an additional access node. If the recovery point objective (RPO) cannot be met within the backup window, add additional access nodes.
Generally, approximately 32TB data can be transferred in a standard 8 hour backup window, on a 10GbE network configuration.
In addition, the read speed from disks, the network throughput from worker nodes, and the network throughput on your access nodes affect the amount of data transferred in the backup window.
Red Hat Linux 7.x, 8.x: Commvault supports all 7.x and 8.x GA releases. For information, see Red Hat Enterprise Linux Release Dates on the Red Hat customer portal.
CentOS 7.x, 8.x: Commvault supports all actively supported CentOS releases. For information, see CentOS Manual on the CentOS website.
Microsoft Windows Server 2019 Editions
Microsoft Windows Server 2016 Editions
Automatic Load Balancing Across Access Nodes
To manage your growing Kubernetes data, instead of increasing the hardware specifications of your access node, add more access nodes (with identical hardware specifications) to your Kubernetes hypervisor.
The Commvault software performs automatic load balancing across the access nodes.
Certain third-party software and service releases (together, "Releases") may not be supported by Commvault. You are solely responsible for ensuring Commvault’s products and services are compatible with any such Releases.