One of the benefits of application modernization, containers, and orchestrating your data-center with Kubernetes is the ability to move to 'fully programmable' infrastructure.
Now while this makes the developers day much much easier, as they provision apps / storage whenever and wherever they need it - what impact does that have on backup & recovery?
Well for Metallic (and Commvault) it is simple...
Commvault is cloud-native, and we use Kubernetes Label Selectors to automatically discover applications based on the 'labels' that developers apply to their apps.
Let's take a look at a standard application definition:
- port: 5432
- name: postgres
- containerPort: 5432
- name: postgredb
accessModes: [ "ReadWriteOnce" ]
In this case the developer has flagged this application as
environment = production in longer form ...
Now we just tell Commvault about this setting in the Application Group definition
We support searching within a single namespace
env=prod -n some_namespace
But now, from 11.23 we can now search for labelled applications across all namespaces in the cluster
This means Kubernetes backup is effectively - set and forget...
Let's click PREVIEW and see what our label selector has found....
We found a number of production applications across the cluster... which we will now protect on the next backup run.
Commvault performs this check at backup time, meaning with adjust data protection to the developer - we get out of the way of the developer and let the business dictate what data is protected - the IT-Ops team simply needs to define plans for each data / label type:
Now that's truly simplified, intelligent data management.....