Data protection is imperative as persistent storage becomes more prevalent in Kubernetes.
In this segment, I will give an overview of Kubernetes managed container backup
using Commvault Backup & Recovery.
Leveraging the HPE CSI driver for Kubernetes,
the Kubernetes cluster will be provided and managed by the HPE Ezmeral Runtime Enterprise.
Let's first go over our environment.
The HPE Ezmeral Runtime Enterprise was utilized
to provision and manage the lifecycle of the Kubernetes cluster.
Here we can monitor usage and view tenant details for each Kubernetes clusters
as well as launch the Kubernetes dashboard.
The HPE CSI driver for Kubernetes allows you to perform data management
operations on HPE Alletra storage resources, including Kubernetes persistent volumes.
The CSI driver exposes many array-specific features, including setting performance,
policy per volume, or taking snapshots by the volume or volume group.
The HPE CSI driver for Kubernetes is also utilized by Commvault
to enable rapid snapshots for application backup.
More on that in a moment.
Commvault Backup & Recovery is a world-class data protection platform where customers
can utilize, protect, and move data across on-premises and the cloud.
Let's begin by launching the new guided setup workflow for protecting Kubernetes.
Here we define an access node and then choose a backup plan, the default, in this case.
Next we populate the Kubernetes cluster API endpoint and supply a service account and token.
The guided setup is concluded by defining an application group.
By default, the application group is namespace-centric.
Here a specific namespace Commvault has been selected.
With Kubernetes Protection complete,
let's highlight what happens during application backup.
When a backup job begins,
Commvault takes a volume snapshot of each PBC by way of the CSI.
In this case, it's an array-based snapshot on HPE Alletra storage.
The snapshot is then mounted as a separate PVC to a temporary pod
that was spun up by the Commvault automation.
It is from this copy that the data is backed up to the storage defined in the Commvault server plan.
Now that restore points are available, let's move to a demo of a simple DevOps type use case.
Let's say a developer has a code change
they'd like to validate against a production application.
With Commvault restore points available, they can obtain their own copy of that application
by sourcing one of these restore points.
Let's see how.
We will start by identifying the restore point,
choosing the date and the time from the UI and click Restore.
The important designation for this use case is that, rather than overriding the production
application we will be performing an out-of-place restoration
to a new namespace and application name.
With the Commvault restore job launched,
we can watch progress on the Kubernetes dashboard UI where we see new PVCs being created
in the DML restore namespace and pods being deployed for the application.
This resource can then be tested against, completely separate from production,
and then removed when it is no longer useful.
And that's just one example of how container data protection can be utilized
by the combined solution of Commvault Backup & Recovery,
HPE Ezmeral Runtime Enterprise, and the HPE CSI driver for Kubernetes.
That concludes our demo. Thanks for watching.