Backup And Data Protection

Question 1

Recovery Services Vaults and Backup Vaults

Answer 1

Home for all backup jobs

Question 2

3 steps to back up data whether in cloud or on-prem

Answer 2

1. Create recovery services vault
2. Define your goal/your workload (on-prem or cloud/Azure VMs, SQL in Azure VMs, SAP HANA in Azure VMs, Azure file shares, etc.)
3. Configure backup policy (Specifies when a backup job runs and how long the recovery points are stored. Default is backup once a day and save recovery points for 30 days)

Question 3

MARS agent

Answer 3

Backup and restore files, folders, and the volume or system state on physical or virtual Windows OS (VMs can be on-prem or in Azure)

No separate backup server required

Not application aware; files and folders, system, and volume-level restore only

No support for Linux

Question 4

Implementing On-Prem File and Folder Backup

Answer 4

1. Create the recovery services vault
2. Download the agent and credential file
3. Install and register agent
4. Configure the backup

Question 5

Options for Backup

Answer 5

1. Snapshots
2. Azure backup
3. Azure site recovery

Question 6

Snapshots

Answer 6

Managed snapshots provide a quick and simple option for backing up VMs that use Managed Disks

Question 7

Workload Protection Needs

Answer 7

Many backup options are available

How workload is being protected today?

How often the workload is backed up?

What types of backups are being done?

Is disaster recovery protection in place?

Question 8

Implement VM Backups

Answer 8

1. Create vault
2. Define backup
3. Backup the VM

Question 9

Azure Backup Server (MABS)

Answer 9

App-aware backups, file/folder/volume backups, and machine state backups (bare-metal, system state). .Install on-prem or on a VM

Question 10

Backup Component Comparison

Answer 10

Azure Backup (MARS) agent

vs

Azure Backup Server (MABS)

Question 11

Soft Delete

Answer 11

Backup data is retained for 14 additional days

Recover soft deleted backup items using an ‘Undelete’ operation

Natively built-in for all the recovery services vaults

Question 12

Azure Backup Center

Answer 12

Single pane of glass to manage backups across a large and distributed Azure environment

Datasource-centric management focused on what you are backing up

Connected experiences with native integrations that enable management at scale

Question 13

Azure Site Recovery

Answer 13

For business continuity. Keeps business apps and workloads (like Active Directory, Sharepoint, etc.) running during outages (as opposed to just keeping data safe like Azure Backup)

Replicate business apps and workloads on physical or virtual machines from a primary site to a secondary location to keep them running during outages.

Question 14

Azure to Azure Architecture

Answer 14

1. VM is registered with Azure Site Recovery
2. Data is continuously replicated to cache
3. Cache is replicated to the target storage account
4. During failover the virtual machine is added to the target environment

Question 15

Explain Locally Redundant Storage, Geo-Redundant Storage, and Zone-Redundant Storage.

Answer 15

Locally Redundant Storage: protects data against server rack and drive failures. Replicates your data three times within a single data center in the primary region.

Geo-Redundant Storage: protects against region-wide outages. Replicates your data to a secondary region (default setting when creating a new Recovery Services Vault)

Zone-Redundant Storage: guarantees data availability within the same region. Replicates your data in availability zones.

Question 16

What are the 2 backup agents?

Answer 16

MARS:
Backs up files, folders, and system state on individual on-prem Windows Servers and Azure VMs
Runs on DPM/MABS servers to back up the DPM/MABS local storage disk to Azure.

Azure VM Backup Extension:
Runs on Azure VMs (no on-prem) to back them up to a vault. This is the primary method for backing up VMs. Backs up the entire VM, unlike MARS agent, which can get more granular.

Question 17

First backup job on a VM

Answer 17

Creates a full recovery point. Each backup job after this initial backup creates incremental recovery points. Incremental recovery points are storage and time-efficient, as they only transfer changes made since the last backup.