This is the solution video for the SCD Back and Restore Lab.
So for the first question, we have to find out the number of deployments that exist in this cluster.
So let's try and still get deployment's, and as you can see, we have two deployments, one called
blue and the other red.
So the answer is to.
What is the vision of a city which is running on the closer to the city part of the process?
So let's inspect the city board.
So if you remember from the lecture, it city is deploying as a port and it should be in the coop system
namespace.
And that's because this cluster has been deployed using Badme.
And if you look at the image and you can see that it is running at three point four point nine.
So let's look that.
At what address do you raise the concern from your master or control plane load?
So in this case, the CD is running as a part on the control plane known and to reach it from the same
note, we can use the local horse and he put two three seven nine.
So if you look at the list like you or else command, which is run within the FTC report, you can see
that one of the address and the port combination where it is reachable as 127 DOT 0.01, which is localhost
and they put us two three seven nine.
As you can see, there's another option, which is SCDP is one twenty seven zero zero one and put two
three eight zero, and that is responsible for other nodes to join the same cluster in case of a multi
cluster scenario.
But in this case, we are connecting to exit from the node so we can use two three seven nine.
Where is the NCD silver certificate file located?
So let's go back to the same command that we ran before, which is describe it to the control plane.
And here we can see that this old file is located under a DC cabinet is speaking I it's KDDI.
So we're not CRT.
Where is the CDC certificate located?
So if you look at the option for us to see a file, you can see that it is also located in the same
directory, which is when it is at CD and the name of the certificate of CRT.
All right, so the massive in August are planned for a regular maintenance reboot tonight, while we
do not anticipate anything to go wrong.
We are required to take the necessary backups, take this snapshot of its database using the CDC data,
and we have to save it under the static.
We would just slash obesity.
And the name of the snapshot should be snapshot, dash, pre dash, blue dot DB.
All right, so let's go back to the dome now and we're just going to clear the screen and to do this,
we'll use the actual tool which is installed in the control node.
And we'll make sure that we are using the CDC deal with the usual three.
So you can see the client is three and the EPA as three point four.
And the command that they're going to use as a snapshot, see?
But here I'm using the dash dash help to see all the options which we need to make use of while running
this command and the global options, you can see all the options that are required to connect to the
CD, which is running on the controlled plane as a pod.
The first thing that we have to add is the certificate file.
We also have to pass on the certificate and the key.
So let's do that now.
I'm just going to commend this command and Lagann referred to the capacity of the scrub command that
used earlier to find out all the body parts for the certificate's.
Now, one thing to note here is that I'm not specifying the endpoint option, and that is because we
are running this command on the same server where it is installed.
In this case, the snapshot has been saved.
Let's run snapshot status.
And for running snapshot status, we do not need the certificates.
Let's move on to the next question.
All right, so let's wait for the maintenance window to finish.
So for this next question, we have to find out what exactly went wrong during the upgrade process.
So there are a few options here.
Deployments are not prison services and our prisons, all of the above or pods are not prison.
So let's go back to a terminal and check the status of these objects.
So if you remember earlier, we had two deployments and now there are none, so let's also check if
there are any services related to this.
But there's just the default component of service.
There's no deployment.
Bovis or Pod?
Luckily, we took a backup, so let's restore back, be closer to its original state to do this, really
run the snapshot, restore calm on.
And let's restore it to a different directory.
So, again, we can make use of the dash dash help option to see all the possible options that we need
to pass in along with this.
Come on.
So in this case, we just have to give the family and the where we want to restore the snapshots in
this case file name as the snapshot file.
And we have to provide the data that ACRI.
So let's save this to a new directory.
Or liber.
KDDI.
From back up.
Now, before I run this command, I just want to quickly show you the contents of this factory and the
original snapshot directly.
So this doctor does not exist at this point in time.
And what it is where it KDDI database is currently stored.
So let's run this command again.
And you'll notice that are not making use of the options for passing in the U.S. certificate.
The silver certificate and the key, and that's because the snapshot is already created in OBD and we
do not need to connect to the silver at this point in time.
As you can see, this new directory has been created under its code from back up.
This is where the snapshot has been restored to.
However, our exit closer is still configured to connect to this directory, which is the original CD.
So you'll have to change that.
And to do that, we'll have to update the YAML file for the support for.
So here is the YAML file for its KDDI.
So if you look at the configuration for this container, you'll see that the dash dash data directory
is currently pointing toward Liberty City and this is within the container.
And if you scroll all the way to the bottom, so I'm pressing Shivji here so that I can scroll all the
way to the end, you'll see that this is actually a volume.
And this also makes use of the hotspot are live at KDDI, which is from the host.
So in order to mount the newly created and the newly restored directory, which is one CD from backup,
we can just make a change here and overwrite this directory to a CD from backup.
So currently, we are making use of this data from the House to mount within our container.
To this, but so as you can see, the name data, which is from this volume here and which makes use
of the hotspot CD from backup, is mounted under Exelis on the container.
So this means that once we see an exit, this file, the report will be recreated as it's a static port
and it will make use of the new iPad or sighting of the database.
So as you can see, the old container for the CD has been destroyed and will be recreated.
There you go and has been recreated.
So if you just copy the Docker container.
And see that the server is now coming up as the static bot.
And here you can see that it is using this wall directly on the container, but remember that this is
a hotspot mount from what it could from back up from the control plane load.
Now, if you're on Kubasik, you'll get Pott's.
Deployments and service.
You'll see that all of them have been recreated.
Thank you for joining me for the solution we do.
I hope that you find it useful.
I'll see you in the next one.