1
00:00:01,040 --> 00:00:02,030
Backup vault.

2
00:00:02,030 --> 00:00:06,860
Now here is a potential confusion because there's actually two hosted, or

3
00:00:06,860 --> 00:00:11,990
cloud‑hosted, solutions in Azure now. There's not just the Recovery Services

4
00:00:11,990 --> 00:00:16,680
vault. I define the Backup vault, it's also cloud hosted. It's a leaner

5
00:00:16,680 --> 00:00:19,440
solution that has no replication engine.

6
00:00:19,440 --> 00:00:22,610
Remember that the Recovery Services vault is not only

7
00:00:22,610 --> 00:00:25,210
backup and restore. That's just half of it.

8
00:00:25,210 --> 00:00:29,910
The other half is the failover, the orchestrated replication engine.

9
00:00:29,910 --> 00:00:34,100
Backup vault is leaner and meaner. It has far fewer capabilities.

10
00:00:34,100 --> 00:00:38,700
It's basically for a handful of selected workload types.

11
00:00:38,700 --> 00:00:39,740
In other words,

12
00:00:39,740 --> 00:00:44,120
Backup vaults have templates where you can back up Azure disks

13
00:00:44,120 --> 00:00:47,870
separately from the VM resource. In Azure Storage,

14
00:00:47,870 --> 00:00:49,450
you can back up the blob service.

15
00:00:49,450 --> 00:00:50,760
Now that's a really big deal.

16
00:00:50,760 --> 00:00:54,670
I've been waiting for a long time myself for a solution to automate

17
00:00:54,670 --> 00:00:59,190
blob backup, and the Backup vault is it. And then we have a template

18
00:00:59,190 --> 00:01:06,000
for the Azure Database for PostgreSQL servers. All right, so just keep that in mind.