WEBVTT

0:00:03.120000 --> 0:00:07.600000
 Hi, in this video, I want to take a
 look at the options for provisioning

0:00:07.600000 --> 0:00:11.020000
 and configuring Recovery
 Services Vault.

0:00:11.020000 --> 0:00:14.320000
 We're going to start out by looking
 at the options for provisioning a

0:00:14.320000 --> 0:00:16.060000
 Recovery Services Vault.

0:00:16.060000 --> 0:00:19.200000
 We'll talk about backup
 infrastructure.

0:00:19.200000 --> 0:00:23.740000
 We'll talk about restore options and then
 I'm going to demonstrate provisioning

0:00:23.740000 --> 0:00:26.840000
 and configuring a Recovery
 Services Vault.

0:00:26.840000 --> 0:00:29.440000
 Let's go ahead and jump into this.


0:00:29.440000 --> 0:00:32.380000
 The first thing is provisioning
 a vault.

0:00:32.380000 --> 0:00:35.840000
 There's really not that much to do
 when you're provisioning a vault.

0:00:35.840000 --> 0:00:41.820000
 This is actually a screenshot
 from the portal.

0:00:41.820000 --> 0:00:43.780000
 You see pretty much four things.

0:00:43.780000 --> 0:00:47.600000
 Pretty standard for anything you get in
 a provision, subscription, resource

0:00:47.600000 --> 0:00:50.520000
 group, name of resource
 and location.

0:00:50.520000 --> 0:00:54.340000
 Likewise, if I'm going to provision
 it from the command line, this is

0:00:54.340000 --> 0:00:58.000000
 an example of the PowerShell,
 the Azure PowerShell.

0:00:58.000000 --> 0:01:03.900000
 Commandlet, of course, there's a corresponding
 Azure CLI command as well.

0:01:03.900000 --> 0:01:05.520000
 Pretty straightforward
 stuff there.

0:01:05.520000 --> 0:01:08.980000
 Now, what about backup
 infrastructure?

0:01:08.980000 --> 0:01:15.060000
 What backup infrastructure you need really
 kind of depends on what you're

0:01:15.060000 --> 0:01:21.260000
 doing. The reality is you need little
 to know back up explicit backup

0:01:21.260000 --> 0:01:26.020000
 infrastructure. You'll see a backup
 infrastructure option, but really

0:01:26.020000 --> 0:01:32.600000
 if I've got Azure and then in Azure,
 I've got an Azure Vault.

0:01:32.600000 --> 0:01:35.320000
 My Recovery Services Vault.

0:01:35.320000 --> 0:01:42.560000
 That Recovery Services Vault has its
 own intrinsic storage and there's

0:01:42.560000 --> 0:01:45.720000
 an option or two for that.

0:01:45.720000 --> 0:01:50.580000
 That's for backing up Azure VMs.

0:01:50.580000 --> 0:01:53.020000
 That's really all the infrastructure
 you need.

0:01:53.020000 --> 0:02:02.280000
 If you're backing up from on-prem, say
 OP, if you're backing up from on

0:02:02.280000 --> 0:02:05.760000
-prem and you're backing up Windows files
 and folders, you need an agent

0:02:05.760000 --> 0:02:16.460000
 installed. You need the agent that's
 going to communicate over to the

0:02:16.460000 --> 0:02:22.540000
 vault. Or if I want more options such
 as backing up entire machines or

0:02:22.540000 --> 0:02:31.380000
 backing up workloads, then I
 need the Azure Backup Server.

0:02:31.380000 --> 0:02:36.420000
 I'm going to install that on a machine
 and then that's really it.

0:02:36.420000 --> 0:02:41.680000
 In reality, there's not that much infrastructure
 that is required for

0:02:41.680000 --> 0:02:47.200000
 backing up. I will tell you that you
 go through the process and if you,

0:02:47.200000 --> 0:02:51.820000
 let's say, create a vault and then you
 use it and at some point you realize

0:02:51.820000 --> 0:02:55.660000
 you don't want that vault, then you're
 going to have to go and delete

0:02:55.660000 --> 0:03:02.060000
 not only the backup items, but there will
 be probably some backup infrastructure

0:03:02.060000 --> 0:03:02.880000
 that is defined.

0:03:02.880000 --> 0:03:06.820000
 Even though you don't really explicitly
 add the backup infrastructure,

0:03:06.820000 --> 0:03:10.180000
 there are times that you're going to
 have to go back and delete the backup

0:03:10.180000 --> 0:03:15.860000
 infrastructure before you can
 delete your actual vault.

0:03:15.860000 --> 0:03:20.420000
 The only other thing is not really
 infrastructure, but you do need for

0:03:20.420000 --> 0:03:26.540000
 backups is you need to define within
 your recovery services, you need

0:03:26.540000 --> 0:03:28.380000
 to define backup policy.

0:03:28.380000 --> 0:03:32.860000
 Really what policy does is it defines
 when you're going to take the backup,

0:03:32.860000 --> 0:03:35.580000
 whether it's going to be daily or weekly
 and at what time, and it also

0:03:35.580000 --> 0:03:39.140000
 defines retention
 for your backups.

0:03:39.140000 --> 0:03:45.620000
 That's really it as far as any backup
 infrastructure that you need.

0:03:45.620000 --> 0:03:50.720000
 Now what I'm going to do is we're going
 to take a look at provisioning

0:03:50.720000 --> 0:03:55.500000
 and configuring recovery services vault
 and really during that demonstration,

0:03:55.500000 --> 0:04:00.340000
 we're going to cover everything that
 I'm going to show you including the

0:04:00.340000 --> 0:04:05.100000
 configuration of recovery services
 vault for backups.

0:04:05.100000 --> 0:04:08.320000
 Let's go ahead and let's
 jump into this.

0:04:08.320000 --> 0:04:16.340000
 I've got my Azure portal and I'm going
 to go in and I'm going to create

0:04:16.340000 --> 0:04:25.080000
 a resource and I'm going
 to create a recovery.

0:04:25.080000 --> 0:04:27.960000
 Now again, it's kind of interesting
 even though it's recovery services,

0:04:27.960000 --> 0:04:31.800000
 when you search for it, it's still labeled
 backup inside recovery until

0:04:31.800000 --> 0:04:35.720000
 you get to the actual create
 recovery services vault.

0:04:35.720000 --> 0:04:37.920000
 It's really not a big deal.

0:04:37.920000 --> 0:04:42.140000
 It's just something that could potentially
 throw you off if you are not

0:04:42.140000 --> 0:04:46.160000
 looking for it. All right, I'm going to
 go ahead and put this in a resource

0:04:46.160000 --> 0:04:57.500000
 group and I'm going to give
 probably creative approach.

0:04:57.500000 --> 0:05:03.840000
 It's called demo vault and review
 and create and create the vault.

0:05:03.840000 --> 0:05:04.920000
 That doesn't take too long.

0:05:04.920000 --> 0:05:06.340000
 It'll take a moment or
 two when it's done.

0:05:06.340000 --> 0:05:12.360000
 We'll come back and we'll take
 a look at the vault itself.

0:05:12.360000 --> 0:05:15.560000
 All right, my vault has
 been provisioned.

0:05:15.560000 --> 0:05:22.880000
 Let's go take a look at this resource
 and I can see that you can see it's

0:05:22.880000 --> 0:05:25.940000
 actually got a way of walking through
 backup and site recovery.

0:05:25.940000 --> 0:05:29.300000
 But what I want to show you, because
 this is a little bit hidden, as far

0:05:29.300000 --> 0:05:35.060000
 as configuration, most of your actual
 configuration are a lot of it, not

0:05:35.060000 --> 0:05:38.440000
 most of it. You'll find
 under properties.

0:05:38.440000 --> 0:05:44.060000
 And configurations such as diagnostics,
 if I want to run diagnostics,

0:05:44.060000 --> 0:05:49.840000
 I can go in and this is really
 standard diagnostic settings.

0:05:49.840000 --> 0:05:52.080000
 Go and add diagnostics.

0:05:52.080000 --> 0:05:55.340000
 You'll see I can archive to a storage
 account, archive to an event hub,

0:05:55.340000 --> 0:05:58.060000
 or send to log analytics.

0:05:58.060000 --> 0:06:02.940000
 And then I have things such as Azure
 backup report and a number of other

0:06:02.940000 --> 0:06:05.160000
 logs that I can generate.

0:06:05.160000 --> 0:06:08.300000
 I'm not going to generate any
 of those from here right now.

0:06:08.300000 --> 0:06:16.680000
 But again, really the standard backup
 or excuse me, the standard diagnostic

0:06:16.680000 --> 0:06:19.700000
 logging that's many resources.

0:06:19.700000 --> 0:06:24.360000
 Now the other thing that I can do is
 under backup configuration, there's

0:06:24.360000 --> 0:06:27.100000
 really only one option, geo redundant
 or locally redundant.

0:06:27.100000 --> 0:06:32.200000
 It is recommended that you stay in geo
 redundant, which is the default,

0:06:32.200000 --> 0:06:35.960000
 but you can also decide to use storage,
 locally redundant storage.

0:06:35.960000 --> 0:06:40.480000
 For example, you're just doing this for
 development or demonstration purposes,

0:06:40.480000 --> 0:06:45.540000
 security settings,
 a couple of things.

0:06:45.540000 --> 0:06:48.260000
 Have you configured multi
 factor authentication?

0:06:48.260000 --> 0:06:50.860000
 Yes or no? Soft delete.

0:06:50.860000 --> 0:06:55.840000
 Soft delete for Azure virtual machines
 means that when you delete a virtual

0:06:55.840000 --> 0:07:02.060000
 machine, it is not actually going to
 fully delete for, I believe it's

0:07:02.060000 --> 0:07:07.360000
 about 14 days. And then you also have
 a number of security features which

0:07:07.360000 --> 0:07:10.480000
 notice I don't actually
 have an option here.

0:07:10.480000 --> 0:07:13.240000
 Once it's started, you
 can't disable them.

0:07:13.240000 --> 0:07:14.600000
 They are enabled by default.

0:07:14.600000 --> 0:07:19.400000
 In fact, the only way you could start
 them out disabled is if you were

0:07:19.400000 --> 0:07:23.940000
 doing this from the command line.

0:07:23.940000 --> 0:07:28.040000
 All right. Security pin, some operations
 require security pin, security

0:07:28.040000 --> 0:07:31.380000
 pin, you generate that and then an operation
 that requires that you would

0:07:31.380000 --> 0:07:33.260000
 then put that in.

0:07:33.260000 --> 0:07:38.120000
 Recovery services agent, that's going to
 be both for backup and site recovery.

0:07:38.120000 --> 0:07:40.680000
 Of course, we're talking
 about backup here.

0:07:40.680000 --> 0:07:43.240000
 You would download that and install
 it on the machine if you're running

0:07:43.240000 --> 0:07:48.720000
 this directly on a machine's, for example,
 for file and folder backup.

0:07:48.720000 --> 0:07:52.800000
 And once you do that, then what you
 do is download a set of credentials

0:07:52.800000 --> 0:07:56.940000
 because the credentials are going to
 be used when you set up the recovery

0:07:56.940000 --> 0:07:59.880000
 services agent on
 a virtual machine.

0:07:59.880000 --> 0:08:03.880000
 All right. So again, that's under properties
 and this is a fairly unusual

0:08:03.880000 --> 0:08:05.800000
 portal experience.

0:08:05.800000 --> 0:08:10.760000
 You don't typically have a lot of interactivity
 under the properties window

0:08:10.760000 --> 0:08:16.240000
 in the blade, but for the recovery
 services, you just do.

0:08:16.240000 --> 0:08:20.120000
 Now I also want to take a
 look at backup policies.

0:08:20.120000 --> 0:08:22.680000
 And right now there's
 a default policy.

0:08:22.680000 --> 0:08:25.060000
 I can add my own policy.

0:08:25.060000 --> 0:08:28.820000
 And there's three options here, virtual
 machines, file shares and SQL

0:08:28.820000 --> 0:08:33.720000
 Server. I'm glad to see that, well,
 at least here, file share and SQL

0:08:33.720000 --> 0:08:36.840000
 Server and Azure VM are no
 longer marked as preview.

0:08:36.840000 --> 0:08:39.500000
 They have been, I'm not sure they're
 not preview, but they've been in

0:08:39.500000 --> 0:08:41.520000
 preview for several years.

0:08:41.520000 --> 0:08:42.940000
 Anyways, that's not the point.

0:08:42.940000 --> 0:08:52.560000
 I could create a policy here, which I'll
 demo policy, keep that consistent.

0:08:52.560000 --> 0:08:54.900000
 And frequency looks like, oh,
 I've got lots of options.

0:08:54.900000 --> 0:08:56.880000
 It's either daily or weekly.

0:08:56.880000 --> 0:09:02.200000
 And then when you want to do it and what
 time zone that is, then you have

0:09:02.200000 --> 0:09:06.880000
 retained instant recovery
 snapshots for two days.

0:09:06.880000 --> 0:09:12.360000
 So I can store snapshots to pull
 back recovery very quickly.

0:09:12.360000 --> 0:09:13.760000
 And then I have daily.

0:09:13.760000 --> 0:09:17.240000
 So it's going to retain daily
 by default for 180 days.

0:09:17.240000 --> 0:09:20.920000
 Weekly backups, what's always interesting
 to me is that the weekly backups

0:09:20.920000 --> 0:09:25.500000
 only store for 12 weeks.

0:09:25.500000 --> 0:09:28.780000
 And we'll say 52 weeks there.

0:09:28.780000 --> 0:09:31.200000
 And retention of monthly backups.

0:09:31.200000 --> 0:09:32.520000
 First Sunday of every month.

0:09:32.520000 --> 0:09:35.360000
 We want to keep that
 for 60 months.

0:09:35.360000 --> 0:09:39.040000
 And then retention of yearly, the first
 Sunday in January for each year,

0:09:39.040000 --> 0:09:42.740000
 we want to keep at this
 point up to 10 years.

0:09:42.740000 --> 0:09:43.640000
 And then I create that.

0:09:43.640000 --> 0:09:48.740000
 Now, that doesn't actually define the
 policy or doesn't apply the policy.

0:09:48.740000 --> 0:09:53.600000
 That's just giving me a policy that I
 can then apply to different backups.

0:09:53.600000 --> 0:10:01.700000
 And once I have that, backup infrastructure,
 really, I've got workload

0:10:01.700000 --> 0:10:06.400000
 in Azure VM, Azure Backup Agent
 will show me protected servers.

0:10:06.400000 --> 0:10:10.360000
 Now, there's not much I can do here in
 terms of actually do anything with

0:10:10.360000 --> 0:10:15.560000
 these. But if I've got data protection
 manager or backup server, I can

0:10:15.560000 --> 0:10:18.060000
 at least look into those,
 but I don't have any.

0:10:18.060000 --> 0:10:24.880000
 And you see the other options
 here for the infrastructure.

0:10:24.880000 --> 0:10:30.800000
 And if somewhere around here, oh, also,
 those are just the storage accounts

0:10:30.800000 --> 0:10:33.100000
 that are protected.

0:10:33.100000 --> 0:10:38.860000
 So there we go. That is your
 infrastructure for backup.

0:10:38.860000 --> 0:10:42.340000
 All right. So again, I know that's not
 terribly exciting, but that's really

0:10:42.340000 --> 0:10:47.280000
 what you have with Azure Backup
 provisioning and configuration.