[MUSIC] In this chapter going through the slides, we are going to look at block storage specific features that are available. Specifically we look at backups, cloning, shared multi attach and performance as individual videos. There is one more video that you will have which is about blocked volume replicas, which is a new service available. In this video specifically, you are going to learn about the usage of backups for volumes. Block volumes are replicated within an ad and are highly available within the AD but then you can configure to have backups. Off your volumes, and whenever you fire a volume backup, it goes and sits inside object storage. Object storage is a regional service which is replicated in all areas in the region. And thereby, by having backups off a volume which is present in one availability domain You are having a backup as of a particular point in time, stored in object storage. And using that you can create new volumes in another area within the same region so that if you want to create a duplicate of an existing instance. You can take a backup of its book volume, block volume and use the backups to create new volumes In another AD and create a new instance. And thereafter if you want them to be in sync, you can use OIS level replication to replicate the data within them. When you look at taking backups, backups are going into object storage and they are encrypted and stored within it. Using the backups, you will be able to create new volumes. Apart from that block storage also gives you the ability to copy a backup from one region to another region, which means you have the ability to set up DR for your applications by taking backups. And copying them into another region. The backups that you take can be both manual or scheduled. When we look at taking backups, let me show you from both the block volumes and boot volume perspective. How do we take backups? Let me create a couple of volumes. For the purpose of this demonstration I will create a block volume in AD one for example here and I will also create a second volume for showing that it will be created in another ad block volume 81 and block volume AD two. I will choose AD two here and create them, two volumes are being created with the default performance and storage characteristics of one PV each. As these block volumes are getting provisioned, we see that this is already available. We can go and then take manual backups. When you take a manual backup, we are having the option to take a full backup or incremental backups. Incremental backups will take only the changes that have happened in the volume since the previous backup. So you have the ability to take backups. And when you have a volume created you notice that it is within an AD. So I'm going to take a manual backup for both these volumes. And we will see that, the individual volumes, as such are present in a given eighty. But if I go to block volume backups listing, I see two backups available. We just says it is in this region. Backups, are in object storage, so they are not tied to any specific availability domain. Similarly, if I come to the boot volume page of my compute instances, I can fire backups manually, and I will call it as with custom image, boot volume backup and maybe Base Linux image backup. These are again point in time backups of the boot volume itself. And they are also kept in object storage buckets, managed internally by OCI and you will be able to see the block volume backups available. Boot volume backups available in that region. And once you have backups available, you will be able to provision new volumes from them. For example, if I go to the block volume backups page, I see that there are these two backups. We saw that this backup was created from a volume that is an ad one I can go here and create a new block volume and say block volume in AD3, using backup from AD1, the just naming convention and following so that you understand from the look of it what it looks like. This is a walk volume, I'm creating an AD3 Using a backup of a volume that is present in AD1, and I can create the new volume. As a result of doing this, I will see that a new block volume is getting provisioned in AD3, using a backup of a volume that is currently present in AD1. In the same way, I could go and go to the boot volume backups that are available in the region and create a new boot volume in another AD, boot volume in AD2 from another AD if I give us the name, I can choose the AD in which I want to provision it. And create the boot volume. As a result, my base image instance which was available in AD1, I took a backup and brought it into AD2 by creating a new volume. Similarly, when I have block volume backups, I have the ability to copy the volume backup to another region. Remember, you don't copy the volume itself, you copy a backup. And when I choose to copy the backup, I choose the destination region to which I want it to be copied. And if I choose London, I can copy the boot volume to London. Similarly the boot volume backup to be precise, I can go to block volume backups and copy the backups to another region. And by doing this, I can take point in time backups of my boot volume and block volumes and copy them to another region. So that if I go to my London region and look into the volume backups, I see that from Germany. I am getting this backup copied into this region. So by doing this, both for good volumes and block volumes, I can get backups from another region and once the backup is available in the other region, I will be able to create a new boot volume it is right now creating the backup so it is not yet available. Once this volume is having its backup copied, you will see that the create boot volume will be enabled. This is a case of creating manual backups and using them within the region in another ad to create new volumes or copying them to another region and creating volumes. You also have the ability to use block volumes or both volumes to have their backup policies assigned. So when I take a particular block volume and edited, I can choose do I want a backup policy? By default there are three built in policies available, which I can see under backup policies, wherein each type of policy has a built in schedule. For example, if I look at a bronze policy monthly incremental backups and yearly full backups are available. Whereas if I go to gold, I will see whatever was there and bronze is anyway their yearly and monthly, my silver level would have had a weekly backup. Gold also has a daily incremental backup If you want to create your own backup policy, you can very well do that. And if I say custom backup policy, there is an option here to enable cross region replication of backups, but the other region to which it can replicate automatically he's tied to specific regions depending on where you are. For example, if I go to London and try to create a backup policy, the target region to which it can, replicate is Frankfort. It is already tied. You cannot choose a destination region when you create your own custom policies. And if you create a policy with cross region replication enabled, every time a backup is fired by the schedules in this policy, a copy of the backup is automatically fired to the other region which is enabled. And once you create a backup policy. It is telling me that you're going to have charges for this based on the cross region replication, network and storage cost. You can go into the policy and add schedules of what is the frequency of backups and how long you want the backups to be retained. Thus, if you have backup policies in place, you can assign these policies to your volumes based on your art requirement, thereby you can have policy-based scheduled backups or manual backups. And when you back them up, tag that is automatically added to the backup even if you use automatic backups in place. And as you saw, backups can be one off with manual backups, and they are typically point in time backups or automatic backups, three built in policies available, you can go and create your custom backups policies as required. Using this functionality, you are able to have a highly available environment of your block storage service. Because with manual backups or automatic backups based on policies, you can have backups in object storage automatically created, as well as replicated to other regions. So that even if an entire region goes down for a natural calamity or something like that you are able to protect your block storage content, that's about the features of backup that is available in block storage.
