WEBVTT

0:00:02.940000 --> 0:00:08.340000
 This video is an overview of
 Azure Recovery Services.

0:00:08.340000 --> 0:00:11.980000
 We're going to talk about, first of
 all, what Azure Recovery Services

0:00:11.980000 --> 0:00:17.340000
 are, and then we'll dive down a little
 bit into the options that we can

0:00:17.340000 --> 0:00:22.640000
 have for backups, and also the site
 recovery options that we have with

0:00:22.640000 --> 0:00:25.300000
 Azure Recovery Services.

0:00:25.300000 --> 0:00:29.400000
 To get started, I'm going to
 go ahead and dive right in.

0:00:29.400000 --> 0:00:35.440000
 As the name suggests, Azure Recovery
 Services are a basic service that

0:00:35.440000 --> 0:00:43.420000
 provides both backup and also replication
 capabilities for your workloads.

0:00:43.420000 --> 0:00:46.340000
 I'm going to draw this out and there's
 a couple layers to this, but let's

0:00:46.340000 --> 0:00:49.360000
 start out with just really
 the very basic.

0:00:49.360000 --> 0:00:56.480000
 I've got Azure. I'm going to draw a
 very big box over here, and I've got

0:00:56.480000 --> 0:00:58.280000
 my on-prem environment.

0:00:58.280000 --> 0:01:08.260000
 We'll label these
 Azure and on-prem.

0:01:08.260000 --> 0:01:15.220000
 Now, in Azure, I am going to provision
 what is called an Azure Recovery

0:01:15.220000 --> 0:01:16.640000
 Services instance.

0:01:16.640000 --> 0:01:22.240000
 Now, you may see this as backup and
 site recovery, vault Azure Recovery

0:01:22.240000 --> 0:01:24.440000
 Services. It's all the same thing.


0:01:24.440000 --> 0:01:27.940000
 They've just evolved the name over
 time and haven't really necessarily

0:01:27.940000 --> 0:01:32.520000
 gotten rid of the old versions, but
 we're going to create a vault.

0:01:32.520000 --> 0:01:35.160000
 It's really what we're creating, and
 it's going to be an Azure Recovery

0:01:35.160000 --> 0:01:40.680000
 Services vault. The vault has both
 functionality and its own intrinsic

0:01:40.680000 --> 0:01:44.100000
 storage. Now, where do we going
 to use that vault for?

0:01:44.100000 --> 0:01:51.920000
 Well, it's going to provide both backup
 and replication, as I mentioned.

0:01:51.920000 --> 0:01:59.360000
 I could have virtual machines, for
 example, a VM in Azure, and I could

0:01:59.360000 --> 0:02:04.740000
 choose to back that VM up.

0:02:04.740000 --> 0:02:09.500000
 There's many ways that
 you can do this.

0:02:09.500000 --> 0:02:12.980000
 I can go into the portal from the VM
 and say, I want to back it up and

0:02:12.980000 --> 0:02:15.960000
 you can actually create the vault,
 or you can go into a vault.

0:02:15.960000 --> 0:02:18.700000
 I want to back up a
 bunch of Azure VMs.

0:02:18.700000 --> 0:02:27.100000
 Now, when it comes to backup, I also
 can back up on premises machines.

0:02:27.100000 --> 0:02:29.880000
 I could say, you know what?

0:02:29.880000 --> 0:02:32.700000
 I want to go ahead by default.

0:02:32.700000 --> 0:02:35.300000
 I want to back up
 from on premises.

0:02:35.300000 --> 0:02:41.400000
 By default, I can't back up directly
 all of the content, but I can do

0:02:41.400000 --> 0:02:43.380000
 a file and folder backup.

0:02:43.380000 --> 0:02:45.380000
 I can install an agent,
 a Windows agent.

0:02:45.380000 --> 0:02:48.900000
 This only works for Windows.

0:02:48.900000 --> 0:02:53.980000
 I can really set up a backup the way
 you would with pretty much any other

0:02:53.980000 --> 0:02:58.220000
 backup system. It's just that you're
 backing up to the cloud.

0:02:58.220000 --> 0:03:03.940000
 Now, if you need more functionality
 than that, in terms of backup, then

0:03:03.940000 --> 0:03:10.140000
 you can actually install
 the Azure Backup Server.

0:03:10.140000 --> 0:03:14.680000
 This is software that you're going to install
 on a machine, could be virtual,

0:03:14.680000 --> 0:03:19.820000
 could be physical, in your
 on premises environment.

0:03:19.820000 --> 0:03:22.520000
 And when you do that, then you
 have all kinds of options.

0:03:22.520000 --> 0:03:28.560000
 For example, you can back up entire
 machines, and also back up files and

0:03:28.560000 --> 0:03:32.840000
 folders. I also can back up workloads,
 such as SQL Server Exchange and

0:03:32.840000 --> 0:03:36.320000
 SharePoint, not just such as,
 but those are the ones I can.

0:03:36.320000 --> 0:03:41.900000
 I could have SQL Server here, and I
 can run a direct backup into Azure

0:03:41.900000 --> 0:03:45.560000
 Backup Server, which can
 hold the content locally.

0:03:45.560000 --> 0:03:49.620000
 I don't know why I drew that outside,
 but, or it can go ahead and send

0:03:49.620000 --> 0:03:52.100000
 that content into the vault.

0:03:52.100000 --> 0:03:57.320000
 Now, Azure Backup Server is actually,
 bit for bit, the same product as

0:03:57.320000 --> 0:03:59.580000
 System Center Data
 Protection Manager.

0:03:59.580000 --> 0:04:04.480000
 In fact, a lot of the documentation
 for Azure Backup Server is going to

0:04:04.480000 --> 0:04:08.560000
 be branded System Center Data Protection
 Manager, just Data Protection

0:04:08.560000 --> 0:04:14.300000
 Manager. All right, now from a backup
 perspective, that's what you get.

0:04:14.300000 --> 0:04:17.540000
 Those are some of the options you
 get big picture with the vault.

0:04:17.540000 --> 0:04:20.900000
 Now, I'm gonna clear that,
 and do this again.

0:04:20.900000 --> 0:04:25.180000
 What about recovery services?

0:04:25.180000 --> 0:04:31.400000
 Well, whereas backup is going to take
 a point in time backup of an entire

0:04:31.400000 --> 0:04:38.020000
 system or the entire data structure,
 with recovery services, still have

0:04:38.020000 --> 0:04:43.040000
 a vault, in fact, I could have the
 same vault performing both actions.

0:04:43.040000 --> 0:04:50.180000
 With a vault, what I'm gonna
 have is replication.

0:04:50.180000 --> 0:04:56.040000
 And I can replicate my virtual machines,
 my Azure virtual machines, I

0:04:56.040000 --> 0:05:08.440000
 can replicate those into the vault,
 and they actually will be sent to

0:05:08.440000 --> 0:05:13.300000
 another region where they're going
 to be kept for a warm backup.

0:05:13.300000 --> 0:05:16.920000
 I can also replicate from on-prem.


0:05:16.920000 --> 0:05:20.480000
 Now, when I replicate from on-prem,
 there's really two models.

0:05:20.480000 --> 0:05:22.780000
 One is the Hyper-V model.

0:05:22.780000 --> 0:05:27.780000
 So if I've got Hyper-V, whether I'm
 running just a standalone Hyper-V,

0:05:27.780000 --> 0:05:31.720000
 or if I'm running a System Center Virtual
 Machine Manager Cloud, both

0:05:31.720000 --> 0:05:41.940000
 of those have options, I also can run
 VMware, and I can use VMware, the

0:05:41.940000 --> 0:05:46.580000
 architecture for VMware, to
 work with physical as well.

0:05:46.580000 --> 0:05:52.480000
 And the idea is that I'm replicating
 my machines, my disks, really, into

0:05:52.480000 --> 0:05:59.040000
 Azure, and then they're being made ready
 so that if I need to fail over,

0:05:59.040000 --> 0:06:04.300000
 I can fail over with minimal downtime,
 and that's really the idea behind

0:06:04.300000 --> 0:06:05.800000
 recovery services.

0:06:05.800000 --> 0:06:12.520000
 And recovery services is really not
 the focus of this course that this

0:06:12.520000 --> 0:06:16.940000
 is part of, but it's good to know
 it's all part of the same thing.

0:06:16.940000 --> 0:06:18.400000
 And there's other options as well.


0:06:18.400000 --> 0:06:22.460000
 Speaking of options, there's other
 options for recovery services.

0:06:22.460000 --> 0:06:28.720000
 I can actually replicate to an off-site
 data center under certain circumstances.

0:06:28.720000 --> 0:06:32.460000
 Speaking, as I said, of options, we'll
 talk about some of the options

0:06:32.460000 --> 0:06:35.920000
 that we have. What can
 we use for backup?

0:06:35.920000 --> 0:06:38.000000
 So for backup, we can
 do the following.

0:06:38.000000 --> 0:06:41.160000
 In Azure, I can backup virtual
 machines, right?

0:06:41.160000 --> 0:06:45.020000
 And that's just gonna take a snapshot
 backup once a day of virtual machines

0:06:45.020000 --> 0:06:46.320000
 that are in Azure.

0:06:46.320000 --> 0:06:51.320000
 I can also backup the file shares that
 are part of a storage account.

0:06:51.320000 --> 0:06:55.340000
 So if I'm using a file service or a
 file share from a storage account,

0:06:55.340000 --> 0:07:00.720000
 I can actually tie that directly and
 back that up directly using the Azure

0:07:00.720000 --> 0:07:05.840000
 backup. I can also directly backup SQL
 Server from an Azure virtual machine

0:07:05.840000 --> 0:07:07.520000
 directly in Azure.

0:07:07.520000 --> 0:07:10.520000
 Interesting. On premises,
 what can I do?

0:07:10.520000 --> 0:07:14.340000
 Well, you can see that I can
 backup files and folders.

0:07:14.340000 --> 0:07:19.120000
 You also notice that I've got virtual machine,
 physical machine and workloads.

0:07:19.120000 --> 0:07:20.500000
 Talk about those.

0:07:20.500000 --> 0:07:27.540000
 All of those require the installation
 of the Azure backup server.

0:07:27.540000 --> 0:07:29.840000
 And now what about site recovery?

0:07:29.840000 --> 0:07:31.780000
 What are my options
 for site recovery?

0:07:31.780000 --> 0:07:36.600000
 There are a number of different architectures
 that are supported with

0:07:36.600000 --> 0:07:40.560000
 site recovery. I've got the
 Hyper-V standalone server.

0:07:40.560000 --> 0:07:44.840000
 So if I have an individual server or
 multiple individual servers, then

0:07:44.840000 --> 0:07:50.640000
 I have the ability to protect
 those with site recovery.

0:07:50.640000 --> 0:07:53.700000
 If I'm using System Center, Virtual
 Machine Manager, and I'm creating

0:07:53.700000 --> 0:07:59.220000
 clusters or what's called a cloud in that
 parlance, although it's on premises,

0:07:59.220000 --> 0:08:05.660000
 I have that. VMware, both standalone
 and vCenter, and physical servers.

0:08:05.660000 --> 0:08:08.620000
 Now the physical servers actually use,
 as I said, the same architecture

0:08:08.620000 --> 0:08:11.580000
 as VMware vCenter.

0:08:11.580000 --> 0:08:12.960000
 What about failover?

0:08:12.960000 --> 0:08:15.600000
 You have really three
 options for failover.

0:08:15.600000 --> 0:08:18.520000
 The first very cool
 is test failover.

0:08:18.520000 --> 0:08:21.900000
 So I wanna make sure that this failover
 is gonna go right without impacting

0:08:21.900000 --> 0:08:23.760000
 my production workflow.

0:08:23.760000 --> 0:08:25.900000
 So I perform a test failover,
 very easy to do.

0:08:25.900000 --> 0:08:30.620000
 In fact, you'll get a warning message
 until you do perform your first

0:08:30.620000 --> 0:08:36.460000
 test failover. Then the common failover
 is on premises to Azure.

0:08:36.460000 --> 0:08:41.120000
 I realize I just left out there, Azure
 to Azure, but that would be one.

0:08:41.120000 --> 0:08:46.180000
 On premises to Azure, you can also, as
 I mentioned, fail between two different

0:08:46.180000 --> 0:08:47.320000
 on premises data centers.

0:08:47.320000 --> 0:08:50.320000
 So you don't actually even
 have to fail into Azure.

0:08:50.320000 --> 0:08:53.460000
 You can really just use
 Azure for orchestration.

0:08:53.460000 --> 0:09:01.500000
 And there is a failback option, but
 the failback option is limited to

0:09:01.500000 --> 0:09:05.340000
 either SCVMM or VMware vCenter.

0:09:05.340000 --> 0:09:10.620000
 Those both support, and there's more
 components to that, but that's what's

0:09:10.620000 --> 0:09:12.120000
 supported with recovery services.

0:09:12.120000 --> 0:09:15.880000
 So that's what recovery
 services are.

0:09:15.880000 --> 0:09:20.760000
 The combination of backups and real enough
 time, it's not quite real time,

0:09:20.760000 --> 0:09:27.380000
 it's not synchronous, but real enough
 time replication of your virtual

0:09:27.380000 --> 0:09:32.180000
 machines or physical servers so that if
 there is a problem, you can failover

0:09:32.180000 --> 0:09:33.340000
 with minimum downtime.