Today we will see how we can backup and restore
persistent volume that are
part of your AKS Azure Kubernetes cluster.
Azure backup service has announced the support
for backup and restore of AKS persistent volume.
Using this feature,
now you can configure protection for
your stateful set application that stores
data in your persistent volume of your AKS cluster.
Now in this demo, we will see the flow of how to
configure backup for one or more persistent volumes
in your AKS cluster,
as well as we will see how to restore
these persistent volumes that
are part of your previous backups.
Let us go to the demo.
Here I have a simple Contoso AKS cluster.
In this cluster, I have
a namespace e-commerce and I
have my deployment shopping cart.
This deployment shopping cart happens to
have a persistent volume claim
that uses a persistent volume.
And it is solved by Azure Disk and it
uses CSI driver for the Azure Disk.
Now let us go to backup center.
Backup center is the single pane of glass for
all your backup administration requirements.
ISO backup admin, come here to backup center and
do any of my backup activity
by simply clicking past backup here.
I select among various services
that I can protect on Cloud,
I select Kubernetes Service here and continue.
How to select my backup vault.
Note the backup vault and the cluster
shall be in the same Azure region and then now I
select my Cluster, a Contoso Cluster
which has persistent volume that needs to be protected.
Next, I've already pre-selected a backup policy.
A backup policy tells me how frequently you want to
perform backup and how
long you want to retain your backup.
To just show the support backup frequency both daily,
once a day backup which is 24 hour
RPO as well as more frequent backup
in terms of hourly, providing 4,
6, 8 and 12 hourly backup for your persistent volume,
meeting the demands of
the RPO for your Business Critical Application.
As well as here, we can choose
to retain the data for a period of a month
or even for weeks or for
your first backup of the day
if it's the first backup of the week, etc.
These options are configurable based on
your RPO and retention requirements.
Going back, I have already picked up
a backup policy that is required for my application.
Here, I will now select what are
the workloads in which my persistent volumes are part of.
Here, I'll select my shopping cart,
which is the e-commerce namespace.
I will also select
resource group in which my disk snapshots,
incremental snapshots that are taken
during the periodic backup job ought to be stored.
I click on "Validate" button to make
sure all the roles and prerequisites
permissions are available for
the backup operation to go seamlessly.
For the simplicity of this backup,
I will skip the stage and I
will show you what a backup items look like.
Once you have configured backup,
you can come to backup center and in
the backup instances you will see
this Contoso Cluster e-commerce namespace,
the shopping cart requirement has been protected.
In this backup instance,
I see I have already planned backup job in the past days.
You will see this stuff all past
backups in the last 30 days.
Let me go and restore another past backup.
In this restore,
the unique thing that you will find here
is you can choose to restore
all the persistent volume that
are part of your backup or
you can pick and choose specific persistent volume.
Let's say you have a MySQL database
on one of your persistent volume you can choose
that persistent volume specifically
and perform a restore operation.
Here, I can either restore back to
the same Contoso Cluster from
where I performed the backup from,
or if I want to restore to a dev testing environment,
I can choose another cluster within
the region to perform
the replication in the test environment.
I will now restore to a test restore namespace
and I will choose
my storage class which is Managed CSI.
This is the CSI provisioner
that uses disk provisioner as a CSI driver.
Similar to backup experience,
here we have validate experience that we
check any permission prerequisites that are
needed on the target environment
for us to perform seamless a restore operation.
For the simplicity of this demo,
I will skip this step,
and I will show you how
the restore experience looks like.
In here, note that we did perform the restore on
ecommerce test restore namespace in my Contoso Cluster.
If you go here, you will see
that same PVC under the name Azure Disk DB PVC
has been restored in the target namespace and it
is bound in a healthy state with a persistent volume.
You will find the same persistent volume in here.
So in this demo we saw how we can configure protection for
your stateful application that stores data in
the persistent volume of your AKS cluster.
The value proposition is this is easy to use.
You don't have to install and maintain
any server environment, we don't install any [inaudible] cluster.
It is cost-efficient,
it is highly secure and more than anything,
it is a native backup solution that is offered
by Azure. Thank you.