Proper configuration of storage targets is necessary to ensure that key data and system states are preserved reliably and efficiently. In this article, we’ll delve into how to perform these configurations for the AZ-600 exam.

Table of Contents

Understanding Infrastructure Backup Service

Before we dive into the configurations, it’s important to grasp what the Infrastructure Backup Service is. The Infrastructure Backup Service is an internal service that is native to the Azure Stack Hub. It is crucial as it helps in backing up important metadata that is crucial to recovering your Azure Stack Hub environment in the event of data loss. This includes backing up the Azure Resource Manager (ARM), Key Vault Secrets, and the Identity Service among others. Crucially, this backup service does not back up IaaS VMs, PaaS services, or any tenant backup data.

Pre-requisites for Configuring Storage Targets

Before you can configure a storage target for infrastructure backups, there are a few prerequisites that you have to confirm.

  1. Backup Share: This is the location where the backups will be stored. The backup share must meet the following recommendations:
    • Sufficient size: Estimates range from 200GB minimum up to 1.95TB if maintaining 7 recovery points.
    • Preserves directory structure: Any changes to the backup directory structure may disrupt backup integrity and hinder restoration.
  2. Backup Account: An account with Read/Write access privileges to the backup share is required. This account doesn’t require domain credentials, workgroup credentials are enough.
  3. Firewall Settings: The Azure Stack Hub hardware lifecycle host and infrastructure VM’s IPs should be allowed through the firewall to the Backup Share.

Configuring Infrastructure Backup Service

After meeting the prerequisites, you can now begin to configure the Infrastructure Backup Service.

  1. Open the Azure Stack Administration Portal: The Azure Stack Admin Portal can be found at adminportal.local.azurestack.external.
  2. Navigate to Region Management: On the dashboard, find the ‘Region Management’ tile and click it.
  3. Open Infrastructure Backup Service: Under ‘Services’, find ‘Infrastructure Backup’ and click it.
  4. Configure Backup Service: Here, add your Backup Share location and Backup Account credentials. Set the backup frequency (daily or more frequent) and retention policy (number of days for maintaining recovery points). Lastly, verify and save these settings.

Please note that changes to these settings will affect future backups but will not retroactively change previous ones.

Validating the Configuration

Finally, after configuring your backup settings, you would want to validate the backup configuration. You can do this by manually triggering a backup on the ‘Infrastructure Backup’ blade on the Azure Stack Hub admin portal.

In conclusion, the configuration of storage targets for infrastructure backups is critical for any Azure Stack Hub environment. Properly configuring these backups ensures data integrity and improves the recovery process in the event of a failure. Therefore, understanding and practicing these steps is important for the AZ-600 Configuring and Operating a Hybrid Cloud with Microsoft Azure Stack Hub exam. Remember, always follow the best practices outlined in official Azure documentation for optimal results.

Practice Test

True or False: Azure Stack allows configuring storage target for infrastructure backups.

  • True
  • False

Answer: True

Explanation: Azure Stack offers the capability to configure storage targets for infrastructure backups, providing users with the means to secure their data.

True or False: Infrastructure backup can be configured to use a network file share.

  • True
  • False

Answer: True

Explanation: Azure Stack allows the use of a network file share as a storage target for infrastructure backups.

What are storage targets for infrastructure backups in Azure Stack Hub? (Select all that apply)

  • A. Blob storage
  • B. Physical Disk
  • C. Network File Share
  • D. Azure Storage Account

Answer: C, D

Explanation: A network file share or Azure Storage Account can be used as storage targets for infrastructure backups in Azure Stack Hub.

A single Azure Stack infrastructure backup can be scheduled to run at different intervals. True or False?

  • True
  • False

Answer: False

Explanation: Only one Azure Stack infrastructure backup can be scheduled and it cannot be configured to run at different intervals.

True or False: Azure Stack infrastructure backup does not support encryption.

  • True
  • False

Answer: False

Explanation: Azure Stack infrastructure backup does support encryption, provides an extra level of data security during storage and transfer.

True or False: Azure Stack infrastructure backup does not restore user data (tenant data).

  • True
  • False

Answer: True

Explanation: Azure Stack infrastructure backup is for the system data only. It does not recover any user data or tenant data.

What type of data does an Azure Stack infrastructure backup consist of? (Select all that apply)

  • A. System Data
  • B. Metadata
  • C. User data
  • D. Configuration data

Answer: A, B, D

Explanation: Azure Stack infrastructure backup contains system data, metadata, and configuration data, but not user data.

Which PowerShell commandlet is used to configure infrastructure backup in Azure Stack Hub?

  • A. Configure-Backup
  • B. Set-BackupSchedule
  • C. Configure-Storage
  • D. Set-InfrastructureBackup

Answer: B, Set-BackupSchedule

Explanation: ‘Set-BackupSchedule’ is used to configure the schedule for infrastructure backup in Azure Stack Hub.

Is it possible to back up to a network file share on Azure Stack Hub using SMB?

  • A. True
  • B. False

Answer: A. True

Explanation: Azure Stack Hub supports backups to a network file share using the SMB protocol.

True or False: Urgent backups can only be performed using the Azure Stack Hub user portal.

  • True
  • False

Answer: False

Explanation: Urgent backups can be initiated using either the user portal or the privileged endpoint (PEP).

Infrastructure backup in Azure Stack Hub can be configured remotely via PowerShell. True or False?

  • True
  • False

Answer: True

Explanation: Infrastructure backups in Azure Stack Hub can be configured using Azure Stack Hub’s PowerShell cmdlets.

What should a backup storage source in Azure Stack Hub meet? (Select only one)

  • A. Read-only rights
  • B. Should be Azure only
  • C. Max. latency of 5ms
  • D. Must have write access

Answer: D. Must have write access

Explanation: A backup storage source should meet the requirement of having write access to store backups.

Can scheduled infrastructure backups be paused in Azure Stack Hub?

  • A. Yes
  • B. No

Answer: B. No

Explanation: Azure Stack Hub doesn’t currently support the pausing of scheduled infrastructure backups.

True or False: Azure Stack Hub supports backing up to USB devices directly.

  • True
  • False

Answer: False

Explanation: Azure Stack Hub does not currently support backing up directly to USB devices.

During a scheduled backup in Azure Stack Hub, can the backup be manually stopped?

  • A. Yes
  • B. No

Answer: B. No

Explanation: Azure Stack Hub doesn’t currently support stopping a backup once it has begun.

Interview Questions

What is the first step to configuring the storage target for infrastructure backups on Azure Stack Hub?

The first step is to manually create Blob storage in a general-purpose v2 storage account to store your infrastructure backups.

How do you change the backup frequency in Azure Stack Hub?

After creating the backup, you can set the frequency of backups on Azure Stack Hub through the “Infra Backup Configuration” settings in the Azure Stack Hub administrator portal.

Is it possible to store infrastructure backups on-premise with Azure Stack Hub?

No, Azure Stack Hub does not support on-premise or physical storage backup methods.

What is the default frequency of infrastructure backup in Azure Stack Hub?

The default backup frequency in Azure Stack Hub is 12 hours.

How long does Azure Stack Hub retain successful backup data?

Azure Stack Hub retains successful backup data for a period of seven days.

What is the maximum retention period for successful backups within Azure Stack Hub?

The Azure Stack Hub does not support a retention period longer than seven days.

What happens if the backup storage quota goes over the limit in Azure Stack Hub?

If the backup storage quota goes over the limit, no further backups will be taken by Azure Stack Hub.

Which storage type is required to store infrastructure backups on Azure Stack Hub?

Azure Stack Hub requires a general-purpose v2 storage account in Blob storage for infrastructure backups.

What is the Prerequisite to configure storage targets for infrastructure backups?

The Prerequisite is to have operator permissions to access the Azure Stack Hub administrator portal and also to have a valid Azure Subscription.

Can we configure Azure Stack Hub to stop taking backups automatically after a certain period?

No, you need to manually stop the backup if you no longer want Azure Stack Hub to take backups.

What is the size limit for the backup share in Azure Stack Hub?

The backup share in Azure Stack Hub should be at least enough to accommodate 1.95*Tb, where T is the total number of TBs of physical memory across all scale unit nodes.

How do you validate a backup using Azure Stack Hub?

You can validate a backup in Azure Stack Hub through the Azure Stack Hub administrator portal by selecting the backup location and clicking the ‘validate’ button.

Why is it recommended to backup Azure Stack Hub data to the separate subscription?

This is to prevent the backup from being affected by accidental cleanup operations in the production subscription.

What should be entered in the “backup file prefix” box while configuring the backup in Azure Stack Hub?

It’s a unique identifier and it could be any string, there is no requirement to use the default ‘FRP’ prefix.

How does the Azure Stack Hub handle unsuccessful backups?

Azure Stack Hub re-attempts a failed backup two times. If it fails for the third time, no more re-attempts are made for that backup cycle.

Leave a Reply

Your email address will not be published. Required fields are marked *