SPEAKER: In this video, we're going to onboard some Compute
Engine instances into Google Cloud Backup
and DR. Our journey begins here in the Backup and Recover menu
by selecting Backup.
We then choose Compute Engine as our source application type.
What this panel is showing is that we're
going to use this selected backup and recovery appliance,
and look in this selected zone in this project using
this service account to add GCE instances into the system.
If we're happy with all of these selections, we can hit Next.
Remember, if you've added the service account
to multiple projects, all of them
will be shown in this dropdown here.
What's shown now are any GCE instances that
have never been seen before.
You can see the dropdown here shows New.
I can change that to Manage, which is basically
GCE instances that are currently being protected
with a backup plan; Unmanaged, ones
that were discovered previously but were never protected
with a backup plan; or ones that were added previously and then
marked as being ignored.
In this case, I've got three new ones, and I'm happy with that
because they're what I'm looking for.
I'm going to add all three.
If you don't see the ones you're looking at,
they're probably in a different zone, in which case,
you can repeat this process later in the correct zone
or hit Previous and change the zone,
and then search in the zone that you obviously
need to be looking in.
I'm going to hit Next.
At this point, we can select the action
we want to take against each of these instances.
In this case, I'm going to select all three.
And then from here, I'm going to say, Apply a backup plan.
Obviously, at this point, it wants
to know what backup plan I'm going to apply.
And the one that I'm going to apply
is the one that I created earlier.
And then I'll choose the backup plan that I want to apply,
which is this one here.
This one says that I'm taking all instances from Sydney,
which I know these three are in because that's
the region that we're looking in,
and back them up into Melbourne.
The profile is simply choosing a matching profile
for the appliance that we chose.
We hit OK.
We can preview the window here.
And we can see that this window is from 7:00 PM to 7:00 AM.
And the retention is seven days a week
and that the snapshots will run daily.
I'm happy with this.
I'll now hit Next.
And I'll hit Finish to apply the backup plan.
At this point, the onboarding will complete,
and all of those new instances will be protected
using the selected backup plan.
Once the Onboard Wizard has finished,
you will get a tick on every box.
Now, at this point, the snapshots
will begin to run according to the schedule set
by the backup plan.
If for some reason I want to manually run
a snapshot before the backup plan will kick off,
because in this case, I've said run it from 7:00 PM to 7:00 AM,
the local time here is currently 3:21,
so it's not going to start yet.
So what I can do is go to my App Manager
and find my application.
Here are my three apps.
I can right-select each one and go Manage Backup Plan.
I can then open the snapshot policy up and say, Run Now.
This effectively is what we call an on-demand job
and will run a snapshot on demand,
as in it's not a scheduled job.
The other thing you can do is if you go to Policy Overrides,
if you remember, my backup plan was set to take source Sydney,
target Melbourne.
So this is why we're going to australia-southeast2.
I could for this specific VM send it back to Sydney
and not have it back up into the default location.
That won't affect any other GC instance protected
with this backup plan.
This is an override on this specific one.
Now that we've applied our backup plan
and checked our policy overrides,
and even in this case run an on-demand job,
one of the things we might want to do
is actually monitor those jobs, whether they're
on demand or scheduled.
So to do that, we can go to Monitor Jobs.
And what we can see here is a list of running
and succeeded and failed jobs in this case because that's
the three filters I've set.
There are filters you can set on the left-hand side here.
You can also filter by application name,
which I've done here.
So I've filtered by prod1.
So you don't see all the other applications on this system.
And you can see that I've got one job currently running.
And if I click on that job, I'll be
able to bring up details about it.
Obviously, the main thing here is
that I have jobs that have run, which
means that I have backups that have been created,
which means I have backups I can now use.
So in the next video, we'll talk about how you actually
make use of the backups that you're creating.