Everyone, and welcome back now into this, we will be discussing about the of a story, Virginny.
Now if you have used it, you'll understand the benefits that devotion control system provides to us
now in a similar way, the feature of moistening is typically absent within these storage devices,
due to which there can be a lot of issues that would be faced and to overcome.
This device has released the feature of warning for S3 storage.
Now, before we go ahead and discuss more in detail about Varshney, let's look into the typical challenge
that might be faced, considering that the warning is not available in a storage device.
So let's assume that you have a storage device on the right and you have the file on the left hand side.
The name of the file is a dot.
So now what you do, you go ahead and store this file into this storage devices and the file gets to
everyone is happy, things are working fine.
Now, let's say some other user from your team only also has created the file with the same name, but
with the different contents altogether.
And he also decides to store the file in the same storage device.
So now what will happen, considering that the folder structure is seen, the older file of it will
be removed and it will be replaced by the newer contents of either the failure.
The second primary challenge is related to the accidental deletion of objects.
So let's assume that either takes these stored and the user has sent the delete file operation and this
file gets removed.
Now in case if there is a need to recover this file back from the storage devices, this is something
that does not really work well.
So in order to overcome these two primary challenges, you have the feature of versioning within the
S3 storage.
So at a high level overview, versioning allows users to keep multiple variants of an object in the
same S3 bucket.
So now you see you have a three bucket.
And considering that the worsening is enable, both the versions of either text are stored within these
two, this system.
Now, along with that, you can also make use of merging to preserve, retrieve and restore every version
of every object that is stored within your S3 bucket.
So let's do one thing.
Let's go ahead and basically jump into practical and understand mode in detail about so currently within
the Estragon.
So let's go ahead and create a new bucket list.
This is Mike Epilepsies hyphen version.
Make sure to use a different name from your site and let's create a bucket list so our budget is ready.
Let's open this up now.
By default, the worsening is not really enabled within the S3 bucket here.
Now, before we continue, let's quickly look into how Windows File system behaves for the objects with
the same name.
So currently I have a new file with the name of it.
Now, if I try to create another text file with the same name, let's try to use the same name here
and immediately see it states that is already a file with the same name in this location.
So apparently you cannot really have two different files with the same name Aurier.
No similar would happen in the bucket as well.
Now in an extra bucket, let's go ahead and try it out.
Let's do an upload, highlight a file and let me add a dot.
The exterior and Alduin upload.
Perfect.
So our file got uploaded.
It will quickly look here.
This is I don't know if you look into the contents of the adobe, it basically has a simple content
of words than now.
Let's assume that we change this file content and we make it to version two, similar to what we were
seeing.
You have DBS file of origin one, and someone from your team also creates the same file and tries to
upload it to the storage device.
So now let's Gordon upload the version to.
Let's upload it.
Great, so the file got uploaded and this specific file, this is the version to file.
So now what happened?
The version one got replaced with the version two of the file, and there wasn't one of the files lost
in these storage devices.
And along with that, if you go ahead and decide to delete this content, let's go ahead and try it
out.
So let's say permanently delete.
So now there is no way in which you can retrieve the file back.
So these are the two challenges that we have seen.
And in order to overcome this, we make use of the feature of Virginny.
Now, if you go to the bucket properties and within a year you have bucket bourgeoning feature available.
Let's go ahead and enable it.
So by default, there you see it is disabled.
So let's go ahead and enable the worsening here and reconceive.
Perfect.
Let's go back to the objects and now let's go ahead and upload that object yet again.
So I'll do an upload.
Let's add that 846 here and we'll do an upload.
So currently, one thing that you will see is that you got a new option, offshore versions over here.
And if you select it here, along with the name of the object, it also shows you the virginity.
So this is the virginity that is associated with the object.
So the Virgin ends with or X. So now let's go ahead and modify our aid or the state will change it towards
the entry and let's upload to fight.
So I add a file, let's upload the same ID or the exterior.
Perfect.
So you see, you have a lot DHT.
If you click on Georgian's you're using it basically shows you two versions of the file.
One is the or X, which basically was the version two and you have the FH and this is the latest version
that was uploaded in the S3 console in case if you really required the previous version, that is also
something that can be retrievable easily.
All right.
So that is the solution associated with the challenge where you can have multiple virgin objects of
the same.
The second challenge that we were discussing is related to the accidental deletion of objects.
So let's deselect the short version.
Let me go ahead and delete it here and let me Tapert delete.
Now, do not that this is delete and not permanent delete.
All right.
So now it's take that deletion is successful.
Now this it does not release to any object, but if you will select the short version.
So here you will see that you have a deletion marker that is associated and it is also showing you the
versions.
You have oiks and effort so that when will you go ahead and delete the object?
There is a deletion marker that is associated with it.
And this is the reason why if you select the short version is the object will not really appear.
But in case, if you want to retrieve it, this is something that can also be done.
Now, along with this, you also have the option to permanently delete the file.
So considering that the short version is enable and you select the appropriate version and you click
on delete, this time it will be a permanent delete and this file cannot be read.
It is also giving you a warning stating that deleting the specified objects cannot be undone.
So there is a difference between a delete and permanent delete.
And this is something that needs to be noted.
Delete will happen considering that the short version is deselected, but delete will happen considering
that the short version is selected and you try to delete often.
Great.
So with this basic, let's also discuss some of the important pointers for versioning for the important
point is that once you version enabler Buckett, it can never return to the convergence date.
You can, however, suspend the worsening on the box.
This is very important to remember.
You cannot go ahead and remove the worsening of the S3 bucket completely.
So let's also look into it so it will quickly look into the bucket properties oilier.
Currently the bucket versioning is enable.
Let's go and try to disable it.
So when you try to disable it, it basically does not have option.
The only option that is present is suspect.
So if you read the description, it states this suspends the creation of object of for all operations,
but preserves any object vergence over here.
So let's go ahead and try it or let's look into what it tries to do.
So let's do a safe change.
So now what really happens here is that you will still have the show Vergence option and if you click
here, you will still see that data over here.
But for the newer file that you upload, let's try it out.
Let's applaud the new extirpate.
And now for this new file, you do not really have the worsening enable, so if I can show urgency here,
you will see that for this new text file the virginities, because there is no warning associated with
this specific object.
Only the older object will have the worsening grid.
So that is what the first point is all about.
The second point states, the warning state applies to all of the objects in the bucket and it does
not work on the map.
So if you have enabled the worsening in the history bucket, all of the objects that you upload will
have the Virgin ID and award winning capabilities associated with the grid.
So this will conclude today's video.