Azure Backup and Site Recovery (Business Continuity Center) Flashcards

1
Q

I want to back up the on-prem VM (Windows) to Azure; how can I achieve this?

A

You can install the MARS agent that when configured will backup to Azure Backup Vault?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

I want to backup Azure VM (Windows) to Azure , how can i achieve this?

A

In the Azure Portal on the VM there is a option to enable backups

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Can you move vaults between subscriptions?

A

Yes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the redundancy model for Azure Backup and Recovery?

A

You chose at vault creation if you want you data in a single zone, multiple zones or in a geo-replicated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is Business Backup center?

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is a backup policy?

A

An Azure Backup Policy is a set of rules that define how and when backups are taken for Azure resources such as virtual machines, SQL databases, and file shares. It helps automate the backup process and manage data retention and recovery. Here are the key components of an Azure Backup Policy:

Backup Schedule: Defines when backups are taken (e.g., daily or weekly) and the frequency of backups (e.g., once a day, twice a day).

Retention Policy: Determines how long each backup is kept. Azure supports retention based on days, weeks, months, or years, allowing for long-term or short-term retention as needed.

Backup Type: Specifies the type of backup, such as full backups, incremental backups, or differential backups, depending on the resource being backed up.

Recovery Points: The policy specifies how many recovery points (snapshots or restore points) to keep and how they are maintained over time.

Instant Restore: For certain services like Azure VMs, the policy can include an option for instant restore, which allows rapid recovery from a snapshot.

Geo-Redundancy: You can choose the type of redundancy (local, geo-redundant) for storing backups, ensuring that they are available across regions if needed for disaster recovery.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

When backing up an AKS cluster, what data is been backed up?

A
  1. Cluster Metadata: This includes the AKS cluster configuration, such as resource settings, identity settings, network configuration, and other metadata related to the AKS control plane. The metadata allows for recreating or restoring the cluster configuration.
  2. Persistent Volumes: Azure Backup focuses on backing up data stored in persistent volumes that are attached to the AKS cluster. These persistent volumes store the stateful data used by the applications running within the Kubernetes cluster. Azure Disks (used as persistent storage) are a key component here.
  3. Application Workloads: While Azure Backup doesn’t directly back up application containers or pods, it ensures that the stateful workloads (i.e., applications with data stored in persistent volumes) can be restored.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

When backing up an AKS custer are you backing up, the container images?

A

No, images are not able to be backup container images.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Can you use Azure Backup to backup Azure Storage Blobs?

A

Yes, you can use Azure Backup to backup Azure Storage Blobs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Can you use Azure Backup to backup Azure Storage Tables?

A

No, you can not use Azure Backup to backup Azure Storage Tables.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Can you use Azure Backup to backup Azure Storage Files?

A

Yes, you can use Azure Backup to backup Azure Storage Files.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Can you use Azure Backup to backup Azure Postgres DB?

A

Yes, you can use Azure Backup to backup Azure Postgres DB.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the supported backup redundancy tiers for storing data?

A
  1. LRS
  2. ZRS
  3. GRS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Do you need to provision storage when using Azure Backup?

A

No, you just create a vault and Azure takes care of provisioning the storage you need.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

When would you use LRS with Azure Backup?

A

To protect agenized server rack or drive failures, data is replicated with in a single zone three times.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

When would you use ZRS with Azure Backup?

A

To protect agenized a regional wide outage.

17
Q

When would you use GRS with Azure Backup?

A
18
Q

I have 3 Hyper-V clusters; what is the minimum number of Azure Site Recovery agents I need?

A

Three, one for each cluster

19
Q

Can Windows server backup be used on its own without other agents, services, and software to backup to Azure?

A

No.

Windows Server Backup is a feature built into Windows Server that provides a solution for backing up and restoring data. It allows you to create backups of your entire server, individual volumes, files, system state, and applications, which can be used for recovery in case of data loss, corruption, or hardware failure.

Here are the key components and features of Windows Server Backup:

  1. Backup Options:
    Full Server Backup: Captures the entire server, including all volumes, applications, system state, and files. It is useful for disaster recovery, allowing you to restore the server completely.
    System State Backup: Focuses on backing up critical system files, including the registry, boot files, Active Directory (on domain controllers), and other essential system components.
    Volume Backup: Allows you to back up specific volumes (partitions) on your server, which can be useful when only part of the data needs to be restored.
    File and Folder Backup: Targets specific files or folders for backup. This can be used to back up important data without needing to back up entire volumes.
  2. Backup Destinations:
    Local Disk: Backups can be saved to another local disk or partition on the server.
    External Disk: Backups can be saved to external USB or eSATA drives, providing portability and physical separation for disaster recovery.
    Network Share: Backups can be saved to a network location, such as another server or NAS device.
    Virtual Hard Disk (VHD): Backups can also be saved as a VHD file, which can be mounted and accessed later.
  3. Backup Scheduling:
    Windows Server Backup allows you to schedule backups to run automatically at specific times. You can set up daily or weekly backups depending on your needs.
  4. Incremental Backups:
    Windows Server Backup supports incremental backups. After the first full backup, subsequent backups will only capture the changes made since the last backup, reducing the time and storage space needed for backups.
  5. Recovery Options:
    Bare Metal Recovery: You can restore an entire server to a new or existing machine, including system state and all data, from a bare metal backup.
    System State Recovery: Allows you to restore just the system files without affecting the application data or user files.
    File and Folder Recovery: Enables the restoration of specific files or folders from a backup.
    Application Recovery: If you have application-aware backups (e.g., using Volume Shadow Copy Service), you can restore application data such as Exchange or SQL databases.
  6. VSS (Volume Shadow Copy Service) Integration:
    Windows Server Backup integrates with VSS, which allows it to take snapshots of applications and system files that are open or in use during the backup process, ensuring data consistency.
  7. Command-Line and PowerShell Support:
    Wbadmin Tool: Windows Server Backup includes the wbadmin command-line tool, which can be used for advanced backup and restore operations. It allows for automation and scripting of backup jobs.
    PowerShell: You can also use PowerShell cmdlets for more granular control over your backup and recovery processes.
  8. Limitations:
    It doesn’t support tape backups natively (you would need a third-party tool for that).
    Limited flexibility in handling more complex backup scenarios, like incremental and differential backups across multiple servers.
    Common Use Cases:
    Disaster Recovery: Ensures your server and its critical data can be restored in case of hardware failure or data corruption.
    Data Protection: Protects specific files, folders, or applications against accidental deletion or data loss.
    System State Protection: Critical for protecting Active Directory Domain Controllers, allowing for recovery in case of system corruption.
    Windows Server Backup is a simple yet effective tool that is useful for small to medium-sized businesses that need basic backup and recovery solutions.
20
Q

Using Azure backup, how would you define a daily schedule to back up a VM?

A

Create a backup policy.

21
Q

What is the purpose of disaster recovery?

A

To ensure the availability of applications, services, and data during a planned or unplanned outage.

22
Q

How can I configure Azure Backup for differential backup?

A

It depends on if the backup has been performed on a VM or SQL Server:

VM: differential is not supported

SQL: differential is supported but limited to once per day.

23
Q

Does Azure Backup support full Azure Backup?

A

Yes, 100%. Full backups are implemented differently for Azure VM and SQL Server backup types:

VM: backup is just prefrom on initial backup and then incrementail

SQL: backup is performed at most ones per day.

24
Q

Explain how an Azure Bacup - Full backup works.

A

A full database backup backs up the entire database. It contains all the data in a specific database or in a set of filegroups or files, and it also contains enough logs to recover that data.

25
Q

How often can you prefrom an Azure Full backup for virtual machines?

A

A full backup is not scheduled but happens on the initial backup.

26
Q

What is transaction log backup?

A

This is for SQL and is supported by backing up the transaction log; this is limited to every 15 minutes.

27
Q

Can you back up the SQL server transaction log every five minutes?

A

No, the SQL server transaction log is limited to being backed up every 15 min at best.

28
Q

Can you use Azure Backup to backup on-prem or data center VM?

A

Yes, 100%; you can back up on-premises Windows machines directly to Azure by using the Azure Backup Microsoft Azure Recovery Services (MARS) agent. Linux machines aren’t supported.

29
Q

Can I back up Linux machines to Azure?

A

No, directly, the MARS agent does not support Linux.

30
Q

What is MARS agent?

A

The Azure Backup MARS (Microsoft Azure Recovery Services) agent is a software tool that:

  1. Allows users to back up files, folders, and system state from on-premises Windows machines and Azure VMs directly to a Recovery Services vault in Azure[
  2. Can be installed directly on Windows machines, Azure VMs, or on Microsoft Azure Backup Server (MABS) and System Center Data Protection Manager (DPM) servers[
  3. Provides features like scheduled backups, data compression, and encryption to ensure secure and efficient backup of critical data to the cloud[
31
Q

I have a VM with Trusted Launch, can is use Azure Site Recovery?

A

No, Azure Sitew Recovery is not supported by a VM using Trusted Launch

32
Q

When using a backup vault, can it be in a separate region form the virtual machines?

A

No, it must be in the same region, unless one dis an odd not recommended to install agent and use the agent to backup the VM.

33
Q

Does Azure backup provide application-consistent backups for Windows and Linux?

A

Yes, Azure Backup provides application-consistent backups for both Windows and Linux virtual machines (VMs).

Windows VMs: Azure Backup integrates with the Windows Volume Shadow Copy Service (VSS) to capture application-consistent snapshots. By default, it performs full VSS backups, ensuring that applications are in a consistent state during the backup process. If an application-consistent snapshot isn’t possible, Azure Backup defaults to a file-consistent snapshot.

Linux VMs: For Linux VMs, Azure Backup utilizes a pre-script and post-script framework to achieve application consistency. Administrators can configure custom scripts that quiesce applications before taking a snapshot and resume operations afterward. This approach ensures that applications are in a consistent state during backups.

34
Q

What services can be backed up with a Backup Vault

A

Azure Disks
Azure Storage Blobs
Azure Database for Postgress
Azure Database for Postgress Flexible
Azure Kubernetes Services
Azure Database for MySQL Flexible

35
Q

What services can be backed up with a Recovery Service Vault

A

Azure Virtual Machines (VMs):

Full VM backup (Windows and Linux)
Encrypted VMs (supports Azure Disk Encryption)
On-Premises Servers:

Windows and Linux machines using Microsoft Azure Backup Server (MABS) or the MARS agent
Azure File Shares:

Backup of Azure Files in Storage Accounts with integration in the Recovery Services Vault
SQL Server in Azure Virtual Machines:

Automated backup of databases hosted on SQL Server in Azure VMs
Azure Database for PostgreSQL Servers:

Backup for Azure Database for PostgreSQL single server (within supported limits)
Azure Managed Disks (limited scenarios):

Incremental snapshots to restore Managed Disks
SAP HANA Databases in Azure VMs:

Backup of SAP HANA databases within Azure VMs, specifically optimized for SAP workloads
Blob Storage (via integration with Azure Backup):

Backup of specific blobs with soft delete and versioning (primarily for data protection)
System State and Files/Folders for Windows:

Files and folders on Windows machines using the MARS agent
System state backup for recovery of critical system files and configurations
Microsoft 365 Data (using third-party solutions integrated with Azure):

Emails, files, and other data from Microsoft 365 (via third-party services)