Networks allow us to preserve this data off of virtual machine at any point in time and let us know
Gundlach if need to be rolling back and indeed that may have been made since the snapchat was taken.
This makes it easy to undo Jinny's or to test different conditions without having to manually undo what
indications are installed in the system in order to get back to a known state
he didn't cheat and we can work with snapshots on the many other window when the guest is selected by
clicking over the snapshot area.
Here we can take a snapshot with that grand state by passing along the Kembla button.
When we do that we can give the snapshot a name and write a description of it if we want to as well.
That's going to help us to remember detail about the state of the machines.
Man this neighborhood was taken.
I've been called this one myself short and press OK.
We're going Dictionnaire Schwarzman a guest is running or when it's shipped off to Goldberg in through
we need to shut down the guest and choose a point from which to the store.
Not that we have a snapshot of this guest.
Let's make a team.
I will change the background image of my guest because that's easy and it's visible difference.
All right.
That's Tiede.
I make a snapchat of this machine as well.
But this time I'm going to use the machine and take a snapshot option.
I really click.
I been call this one blue blue background and I even click OK I've been checked on the guest and then
I will go in and choose to restore the previous state with the gamelike on with the blue at all I have
already made a snapshot of the team at stake so I don't need to create a snapshot of a current machine
state.
Had a not created a snapshot with a blue background all of those changes would be lost.
I will choose these two.
And then I will start my virtual machine.
And this how the guest was before the teaching of the background was made I can switch back and forth
keeping in mind that changes made in an oddly oddly snapshot.
I want to paint the state of little snapshots.
Snapshotting basically Falk's your virtual machine.
You want to keep an eye on how many snapshots you are making and how complicated data not is snapshots.
Don't take up as much space as the Holy Ghost but they do take up a little space so it's a good idea
to
unneeded snapshot occasionally delete unneeded snapshot and occasionally and keep in mind snapshots
are not backup.
We can also make duplicate copy or clone of the virtual machine of the state of the machine at a given
snapshot.
A clone is a different virtual machine rather than a copy of moment in a time.
Once the clone is made you have effectively two identical ghast.
There are two kinds of clones.
A full blown and a link Glaum are full of them and makes a copy of this for the lonely little machine
and a link clone uses the same basic file for both ghast Bustos anything is in the separate fine tuning
in one against want to affect the other one.
And they they each have their own set of data sources.
Cloning is a good approach.
If you have one what's your machine you want to use as a starting point for a handful of different machines
to make a clone.
I can either select guest on a snapshot and right click to find that clone option or look for the little
cheap button and get it.
I guess I can set a name and if the clone machine is going to be on the same network as regional it's
a very good idea to make sure that MAC address is different.
We can do that with this option here or change it manually in the setting later on on the next screen.
I can choose whether to make a full on a linked clone.
In this case I will use a full clone then I can choose whether I want snapshots to be cloned with the
new machine.
I can keep start it up alongside the other one if I want to.
There's my clone and I can see that it's running right here next to reason.
But for now I've known this on and saved some space.
I really don't need this.
Might I come to the remove and to delete all files.