Hi, My name's Dean Pompilio. Welcome to Cyber Very. We're working with the virtual ization installation configuration Evangeline Course, and we're on module seven. Lesson four,
where we get to see how snapshots work.
So we'll see what's involved with taking a snapshot and how you manage
What's involved with deleting a snapshot and doing the consolidation?
We'll see what that means.
Also, we'll talk about deleting of'em and then wrap up by doing lab number 12.
Okay, so snapshot is a very useful bit of functionality.
we can preserve the state of the virtual machine
on the lab as you'll see as we go through that, that you could make changes to the machine.
Uh, take a snapshot,
and then revert back and forth to see those changes before and after a snapshot was created
so I can return to a snapshot
as many times as I want.
There are some limitations
and some considerations for how you manage your snapshots as you
deal with them in a production environment.
But theoretically I can create as many snapshots as I want and be able to go back and forth among them to different points in time,
so this is very useful. For instance, if you are
about to upgrade a machine or about to patch it
or you're about to make some other configuration change,
which could be, ah, problematical destructive, you can always take a snapshot. First,
do your work. And then, if everything doesn't work out as expected, you could revert back to that snapshot
captures the dot Envy RAM file, the BMX file and the power state of the BM.
So snap shotting of'em that's power down. Obviously, that would be preserved.
We can also preserve the state of the disc
and optionally the memory.
Uh, preserving the member state might not always be needed, so it's something that you can keep us an option.
When you create a snapshot, you have several different files that are
We have the VM name dot via Massa de that tracks all the snapshots of this being uses.
Then there's the Delta disc, and the Delta just tracks all the changes to the disk,
and it happened since the snapshot was created so that SVM name Dash Delta got B M D. K.
You have two very careful with the Delta disc files
if you create a snapshot
and you forget about it. For instance,
this dealt a disk file will continue to grow because it's continuing to track
all the changes to the disc. Since that snapshot was created
and there've been many times,
where someone creates snapshots, they forget about them, and all of a sudden your data stores filled up
and you have to go in and troubleshoot. You realize you've got adult of disk file
that might be many gigabytes and size,
so snapshots are not intended to be
something to keep Iran permanently. They're intended to be used when they're needed, and then you kind of clean up after yourself. Later,
the memory state is captured in Vienna, named asked
With a new miracle indicator,
This could rotate between zero through nine and then rotate again back around a zero. Depends how you got that configured, but you do have some options for how many of those files you can keep around.
Same thing with the snapshot description file and snapshot don't itself.
with some new miracle counter.
Uh, 000100002 and so on
with the dot vm kate
be indicate extension for the description file and then the dash delta for the V, M. D. K.
And these files Congrats. Just like the Delta disk file can grow. So you have to be careful with those. And don't forget they exist.
So you can probably imagine the storage within your data store
when you take a step, snapshot, weaken,
capture whether it's powered down or powered off or suspended. The VM can support snapshots and all three of those cases
remember, this is not a backup of your system,
even though it appears to function like a backup. It's on Lee capturing the changes between when the snapshot was made and what you've done since then.
So it's just those deltas that get captured, not the actual contents of the V M.
So make sure you have that that clear in your mind
when you make a snapshot, you want to give it a descriptive name.
You might even want to put a time stamp
in there so you can say, you know Saturday, December 25th
before patching or something of that nature. So now when I when I do other work, I wantto go back and revert back to that snapshot. I can see how this is the one that I created before I did my patching on this date.
And that way you can make your life easier by giving
snapshot e a name that's very descriptive.
We can also decide if you want a snapshot memory again. I said this was optional.
So there's a little check box and snapshot manager that allows you to decide that. And you can also have the option to qui es the guest file system.
So that means that the guest file system is quieted down to the point with a snapshot can capture as much information as possible
on the guest OS. This is another option, but you do need Veum were tools to use that particular option.
gives you a display that looks somewhat like what we see here,
and this allows you to create your difference snapshots in a hierarchy
and so I can go forward and backward or go to snapshot, go back to another one and so on,
and you have the option to delete an individual snapshot or delete all the snapshots.
So regarding deleting and consolidation, Snapshot manager shows you what we see here.
I've got my base disc with some amount of data. Five gigabytes in this case.
And then I've got ah, snapshot 01
that's captured one gigabyte of Delta information. So that means that there's a gigabyte of data here
that's different from what my base disk contained.
So the base disc plus the snap Snapple one data is what's in this?
I might have another snapshot 02 Now, I've got two gigabytes of Delta information.
When you're looking at the snapshot manager, you get a little target symbol here saying you are here
that way. You know, if you revert to this snapshot, you are here, will be on this spot, could revert here, and it will move back and forth that way. When you're looking at this, you have some idea of where you are within the
So some different since situations to keep
If you delete one of more levels above you are here. You can't return to that moment. So if I'm here and I still like this snapshot and delete it. I can no longer go back to that snapshot. That data is gone.
I basically am stuck with this snapshot
going forward until I take some other action.
If I delete my current snapshot,
currently here. If I delete this one
now, I revert back to whatever was the parent of that snapshot and I lose this data.
So keep that in mind where you are in the hierarchy. When you do, you're deleting.
If I delete a snapshot below, you are here.
you are you are here is in this location
now, whatever was previously saved
in snap 02 is now gone.
I can't use it any longer. Then maybe something you want to do on purpose.
where you are when you do a deletion.
That's another good reason why you don't want to use a name like snap 02 or Snapple one. That doesn't mean anything, right?
Picking name that's descriptive before patching after patching before upgrade after upgrade things of that nature arm or helpful down the road.
I can also do a delete all operation within the snapshot manager.
This would basically
get rid of these two snapshots and consolidate that data into my base disc.
I'm sorry it doesn't consolidate the day I convinced the changes to the disk.
The consolidation is a different operation.
You might get a warning. If you have snapshots for IBM
within the within the century might get a little warning of the top level
received warnings. Things like things like
VM or tools needs to be upgraded or some other messages of this nature. You might see a message saying consolidation is required,
and that means that you've got some kind of break in the linkage between your snapshots and you need to consolidate. The VM are the snap snap shot Manager
might not even show that the snapshots exist,
but the files that we talked about earlier
these files might still exist in your data store. So you need to
go browse the data store, see that you've got files there
and that that would correlate to the to the message that you're getting saying that consolidation is needed
when you do the consolidation.
get rolled up back into the base of desk.
And this is a way to clean up after the fact that you've got snapshots that haven't been managed properly.
So just be careful when you're working with these so that you use them as needed and then make sure to do your clean up when you're done.
Okay, so as a recap,
one last thing. Sorry we didn't talk about deleting bm
You can right click of the M
and select removed from inventory
that just removes it from be centers inventory. It doesn't change
anything on the data store for the bm lives. However, you can right click of be Emma's well and below removed from the Victoria, there is a delete option
when you delete you really do get rid of all the files on the data store. So be careful with that option as well to make sure that you know that you actually want to remove the files that you're not gonna need them later.
All right, so, to recap, we talked about what snapshots actually do. What kinds of settings are captured when you do a snapshot.
We also look at the different file types and be aware that these Delta files will continue to grow as long as that snapshot exists.
So don't don't create snapshots and forget about them. Stay on top of that and manage it properly.
We know we can have the V empowered on Off are suspended.
We know that it's not a backup,
so keep those things in mind.
And when you're managing your snapshots using man snapshot manager,
be aware of where you are in the hierarchy before you do a delete, delete all or consolidation.
where you'll unregistered machine from the inventory. Just removing it from the inventory and you'll put it back into the inventory to see how that works.
You'll delete virtual machine from a disc,
then take snapshots of the virtual machine, revert back and forth to those snapshots
and then delete an individual snapshot. And then all of the snapshot.
All right, that concludes the lesson. Thank you