[MUSIC] In this video, you will look at DR Considerations when you are using compute. So when you create a compute instance, remember the instance is created in a particular availability domain, or a data center in a specific file domain. Now, in case you want to edit a compute instance, and change its fault domain, that is supported for specific types of compute instances. If you click on edit here, it gives you the option to edit shape, any VM standard instance can be changed into another shape of virtual machine standard. And, you also have the ability to edit the fault domain in which you want it to be provisioned. But once you have done that, you are able to move a compute instance into any other hardware within the same AD. Now, let's say, you have a BASS instance available with you, and you want to use the same in another region, how would you use that? Or for that matter, if you wanted to use it within the same region, but in another AD image came in of help, wherein you see that the original instance BASS instance was created an AD one. I created a custom image, and provision the new instance in AD three within region is very much possible with custom images. When I have custom images created, I can export them, and when I export them, I need to put them into an object storage bucket. So let me first create a bucket, in the same region Frankfurt, and I will call the bucket as, images bucket, just for the purpose of naming, and I will use the standard tier for this, and I have a bucket created. Now let me come back to the custom images section, under compute and export this current image. It will take a while for it to export, you can export it to a given bucket which is available in the same region, or if you have pre authenticated request for any bucket, you can use that. We are not going to look into that here, and I will call this as custom image, as the name, and images that you export can be in different formats. Since we created with OCI this image, we will keep it in the OCI format, and export it. In a few minutes, this image will get exported into my object storage bucket, we will have to wait for some time for the image to be available. Whereas you also see over here, there is an option to import, we'll come back to exporting it and taking it to another region in a moment because it takes a while. In the meanwhile,let us look at importing images,it's quite possible ,you have On- Prem environment. And you want to lift and shift, your computers in your On- Prem into OCI. When you are considering doing that, you may want to bring images from your On Premise into OCI. Which means in your On- Prem environment, from the various computers that you use, you can create your own images. Then, push these images into object storage buckets, like how we exported here. We did not Upload the file, internally, the same is happening, the images getting uploaded into a bucket. Here, you will land up exporting the image in your On- premise, and upload it into an object storage bucket. So if I have a bucket in my OCI region, I could upload my On- premise images in here. And from there, I can import this custom image created in my On- premise, as a custom image into OCI. For that, obviously I should have had an image uploaded into the bucket. So if I have my On- premise environment, from where I can upload an image into the bucket, and once it is uploaded, I can choose to import the image. Give a name, for example from On- prem, for Linux 7.4 for example, and choose the bucket in which, the file has been uploaded. And what is the format in which you have created the image in your On- premise, there are different options available. We can see paravirtualized mode, good for virtual machines, for native mode, typically used when you're using it with, computers created within OCI, emulated mode, typically good for physical machines bare metal implementations. Each gives various options, standard system administration options, to be considered. If you use the qcow format, again these are how the images are created in your On- premise, from which you are going to import. And once this image is imported, I don't have an image I brought in. But if you have image created and uploaded into a bucket, you will be able to bring them in, and they will be available as an image inside OCI. So that's about how do you bring in your custom images from On- premise, which is there in the next slide, I will come back to DR as the export is happening. So if you wanted to bring your own images to, from your On-premise, or another tenancy into OCI, you can do that or bring it across regions. You push it through object storage, and get them into custom images section, and we have seen the various options. Thus, you can use images in OCI as custom images and move them across regions, or get your On- premise images into OCI. Now let's look at how do we take care of doing DR, If you have exported a custom image into object storage bucket which is still ongoing, look at it this way, you may be available currently with your computers in Ashburn. And you want to have a DR for your applications in Phoenix region, so you have set up your computers with the applications in Ashburn. And with the methodology given by me, you could have created custom images for them, exported them into object storage bucket. And then, from the object storage bucket, you can get them imported as images into the Phoenix region. This is going through the object storage service, which is accessible from anywhere, so cross region copies or taking it into your On- premises would all be doable. If I come back to my instances page, I had a BASS instance created, from which I created a custom image. And I'm waiting for this to be created, wherein the export of the custom images right now still going on, and once the image is brought in here, I can create a pre authenticated request, and import it into any region of my choice. Another option that you have, to take your boot volumes from one region to another, is the ability to go to boot volumes and take a backup. So as the custom images getting created, I'm showing you another option. So if I have a boot volume of an instance that is currently running, I can go and create a manual backup. So, Backup of BASS instance is the name. This backup is taken as of now, as of current point in time with which I can have a backup created, which will be available and reboot volume backups. Once this backup is available, I will be able to copy this backup into another region, and as this backup is getting created, I will also show you the ability to create replicas which is a new feature recently introduced. If you go to any particular volume that is available as a boot volume, you can go into this particular boot volume. And from here, you see there is an option to create a boot volume replica. There is no boot volume replicas available right now. And if you wanted to create a boot volume replica, you can go to any given boot volume that is available, and from the boot volume replicas what is happening is, it is going to continuously replicate the data considering a backup. It is a one time backup that is created, whereas a boot volume replica, is constantly updated with whatever changes that are happening. If I go into my boot volume PE, I see the option to edit the boot volume. And when I click on Edit, at the bottom there is the option to cross region replication to be turned on, choose the destination region, and into which AD you want this boot volume to be replicated, and give a name to the boot volume to be created. And clicking on this, OCI is going to create a new volume in the destination AD, in the destination region, and will keep it continuously level replicated. And as a result of that, you will have a storage level replication of the data, in your boot volume in Frankfurt, getting continuously replicated into London. If I go to the boot volume replicas over here ,we see that it is getting created. And whenever you want to do a DR, you can go and activate it right now it is provisioning, but once it is available, you can activate it so that you can failover your application to the new region which is London, in this case. In the meanwhile, if I go to my custom images and look at the object storage settings in Frankfurt, it is now in an available state. Which means if I go to my Frankfurt bucket, which I earlier created my custom image is already exported. It's about 1.3 gigabytes, I can create a bar, or I can come into custom images in the other region to which I want to import it. And import, when I want to import I will say custom image from Frankfurt. And what is the OAS from which it was created, Linux is what are used. I can choose the bucket in the same region only, so, if I have copied it into a bucket in the other region, which I could have done by copying this into a bucket in the destination region. Then I could have used over here the bucket in this region, or I can create a pre authenticated request at the object level. And choose to allow reads give a date when it will expire, and when I create a bar, a URL is given. Copy the URL then in there, and with the URL that you have, you give the URL, choose that it is an OCI created image, because that is what I have done, and import. By doing this, you have successfully, copied the image, from Frankfurt in to London. So in a few minutes it will be available, and once the import is complete, you will be able to create an instance in this region. Thus, we looked at how we can create boot volume replicas, which is replicated at a storage level. It is right now available here. And in case your application in Frankfurt goes down for whatever disaster that might occur in Frankfurt, your OAS data that was kept inside this is automatically replicated to the boot volume replica that is created in London. And will give you the ability to go and activate it, and use this boot volume in this region. Thus, that is another means to take care of cross region DR capability. You can either create custom images, which would be a one time image copy or take a backup of your boot volumes, which is something we saw earlier. Wherein a backup was fired for our boot volume in Frankfurt, wherein for this boot volume I created a backup which is available here, and I can copy it to one other region. And let's say I choose London and copy. Three ways in which you can take care of DR, option one is Create Custom Images, and Copy to another Region using Object store installed internally. Or option two is to use the new feature of Boot Volume Replicas that you can use, or make a Backup and Copy the backup to another region. And what you need to remember is, it is only the case of Boot Volume Replica where the data is constantly replicated at the storage level, if you create customer images, it is a static data. If you create backups, it is a static data, whatever time you find the backup that is the only data that is taken there. So let's go and see what God created in the Destination Region, London, where I asked the Boot Volume Backup to be created, so we see that the backup is available. I have a boot volume replica also getting constantly synchronized, both options along with the ability to use custom images. Gives us three ways to take care of DR, for our boot volumes specifically. So with this, we complete this topic on using custom images, which could be for creating a standard image to create new instances. Or for DR export, import cross region copy, for the purpose of, taking care of, availability of your application.
