You can back up contents of PersistentVolumeClaims (PVC) directly to the Backup Gateway, without transmitting via the API server. By default, the software uses the Commvault Cloud backup pod (cv pod) to backup PVCs directly to the storage, thereby improving backup performance especially with large volumes.
Important
-
Network-optimized backups are currently limited to clusters that have x86-64 nodes.
-
When you create a new cluster in Commvault Cloud, the software backs up PVCs directly to the storage. To disable network-optimized backups, use the Network Optimized Backups toggle key on the cluster and application group configuration pages.
-
For an existing cluster, if you enable network-optimized backups, the first backup job is marked as Incremental, but the Commvault Cloud software will backup all the files.
-
You must contact the SRE team to disable client-side deduplication and compression to reduce CPU impact on the cluster.
Benefits
-
Improved performance: Data transfer bypasses the Kubernetes API server, reducing overhead and improving speed.
-
Cloud-optimized: Backup data is sent directly to cloud storage from the backup pod running in the Kubernetes cluster.
-
Efficient data handling: Deduplication, encryption and compression occurs on the backup pod before transferring data to the Backup Gateway.
Before You Begin
Ensure that the cv pods can connect to the CommServe server, backup gateway, and Backup Gateway either directly or via network topologies configured for the Kubernetes client. If direct network connection cannot be established, then network gateway using a network topology must be configured.
Contact the Commvault Cloud SRE team to do the following:
-
Commvault pulls a Docker image for a temporary worker pod that performs data movement. Commvault Cloud uses the cvk8sfs image.
You can configure your Kubernetes clusters to pull container images from the Docker Hub. Or, if you have an air-gapped cluster, you can specify a private container registry that contains the image.
-
Configure the following:
-
A server group for the Kubernetes cluster pseudo client.
-
A server group for the network gateway clients which can be reached from the Kubernetes cluster and can connect to the CommServe server, backup gateway, and Backup Gateway.
-
A server group for the infrastructure clients that will initiate connections to the network gateway group.
For more information on how to create a server group and manually add servers to the group, see Server Groups.
-
-
Configure a network gateway topology using server groups that you created in the above step.
Enabling backups without using the API server (for existing clusters)
To enable backups of PVCs directly to the storage, you can configure the Network Optimized Backups setting on the cluster or application group.
Enable network optimized backups on an existing cluster
-
From the Command Center navigation pane, go to Protect > Kubernetes.
-
On the Clusters tab, click the cluster.
-
On the Configuration tab, in the Settings section, click Add.
-
Click Lookup.
-
Select the check box next to Network Optimized Backups, and then click Select.
-
Move the Value toggle to the right.
-
In the Comment box, enter an explanation for the change.
-
Verify that the Enable check box is selected.
-
Click Save.
Enable network optimized backups on an existing application group
-
From the Command Center navigation pane, go to Protect > Kubernetes.
-
On the Application groups tab, click the application group.
-
On the Configuration tab, in the Settings section, click Add.
-
Click Lookup.
-
Select the check box next to Network Optimized Backups, and then click Select.
-
Move the Value toggle to the right.
-
In the Comment box, enter an explanation for the change.
-
Verify that the Enable check box is selected.
-
Click Save.