Infrastructure Backup Service reference
Azure backup infrastructure
Azure Stack Hub consists of many services that comprise the portal (Azure Resource Manager) and the overall infrastructure management experience. The app-like management experience of Azure Stack Hub focuses on reducing the complexity exposed to the operator of the solution.
Infrastructure Backup Service is designed to internalize the complexity of backing up and restoring data for infrastructure services, ensuring operators can focus on managing the solution and maintaining an SLA to users.
Exporting the backup data to an external share is required to avoid storing backups on the same system. Requiring an external share gives the admin the flexibility to determine where to store the data based on existing company BC/DR policies.
Infrastructure Backup Service components
Infrastructure Backup Service includes the following components:
- Infrastructure Backup Controller
The Infrastructure Backup Controller is instantiated with and resides in every Azure Stack Hub Cloud.
- Backup Resource Provider
The Backup Resource Provider (Backup RP) is composed of the user interface and APIs exposing basic backup functionality for Azure Stack Hub infrastructure.
Infrastructure Backup Controller
The Infrastructure Backup Controller is a Service Fabric service that gets instantiated for an Azure Stack Hub Cloud. Backup resources are created at a regional level and capture region-specific service data from AD, CA, Azure Resource Manager, CRP, SRP, NRP, Key Vault, RBAC.
Backup Resource Provider
The Backup Resource Provider presents a user interface in the Azure Stack Hub portal for basic configuration and listing of backup resources. Operators can do the following actions in the user interface:
- Enable backup for the first time by providing external storage location, credentials, and encryption key.
- View completed created backup resources and status resources under creation.
- Modify the storage location where Backup Controller places backup data.
- Modify the credentials that Backup Controller uses to access external storage location.
- Modify the encryption key that Backup Controller uses to encrypt backups.
Backup Controller requirements
This section describes the important requirements for Infrastructure Backup Service. We recommend you review the info carefully before you enable backup for your Azure Stack Hub instance, and then refer back to it as necessary during deployment and subsequent operation.
The requirements include:
- Software requirements - describes supported storage locations and sizing guidance.
- Network requirements - describes network requirements for different storage locations.
Supported storage locations
|SMB file share hosted on a storage device within the trusted network environment.||SMB share in the same datacenter where Azure Stack Hub is deployed or in a different datacenter. Multiple Azure Stack Hub instances can use the same file share.|
|SMB file share on Azure.||Not currently supported.|
|Blob storage on Azure.||Not currently supported.|
Supported SMB versions
Infrastructure Backup Service supports transferring backup data to an external storage location with SMB encryption enabled on the server side. If the server doesn't support SMB Encryption or doesn't have the feature enabled, Infrastructure Backup Service will fall back to unencrypted data transfer. Backup data placed on the external storage location is always encrypted at rest and isn't dependent on SMB encryption.
Storage location sizing
We recommend you back up at last two times a day and keep at most seven days of backups. This is the default behavior when you enable infrastructure backups on Azure Stack Hub.
|Environment Scale||Projected size of backup||Total amount of space required|
|4-16 nodes||20 GB||280 GB|
|ASDK||10 GB||140 GB|
|SMB file share hosted on a storage device within the trusted network environment.||Port 445 is required if the Azure Stack Hub instance resides in a firewalled environment. Infrastructure Backup Controller will initiate a connection to the SMB file server over port 445.|
|To use FQDN of file server, the name must be resolvable from the PEP.|
Make sure to setup firewall rules to allow connectivity between ERCS VMs to the external storage location.
|ERCS VM 1||Storage location||445/SMB|
|ERCS VM 2||Storage location||445/SMB|
|ERCS VM 3||Storage location||445/SMB|
No inbound ports need to be opened.
Starting in 1901, the Infrastructure Backup Service will use a certificate with a public key (.CER) to encrypt backup data and a certificate with the private key (.PFX) to decrypt backup data during cloud recovery.
- The certificate is used for transport of keys and isn't used to establish secure authenticated communication. For this reason, the certificate can be a self-signed certificate. Azure Stack Hub doesn't need to verify root or trust for this certificate so external internet access isn't required.
The self-signed certificate comes in two parts, one with the public key and one with the private key:
- Encrypt backup data: Certificate with the public key (exported to .CER file) is used to encrypt backup data.
- Decrypt backup data: Certificate with the private key (exported to .PFX file) is used to decrypt backup data.
The certificate with the public key (.CER) isn't managed by internal secret rotation. To rotate the certificate, you need to create a new self-signed certificate and update backup settings with the new file (.CER).
- All existing backups remain encrypted using the previous public key. New backups use the new public key.
The certificate used during cloud recovery with the private key (.PFX) is not persisted by Azure Stack Hub for security reasons. This file will need to be provided explicitly during cloud recovery.
Backwards compatibility mode Starting in 1901, encryption key support is deprecated and will be removed in a future release. If you updated from 1811 with backup already enabled using an encryption key, Azure Stack Hub will continue to use the encryption key. Backwards compatibility mode will be supported for at least three releases. After that time, a certificate will be required.
- Updating from encryption key to certificate is a one-way operation.
- All existing backups will remain encrypted using the encryption key. New backups will use the certificate.
Infrastructure Backup Limits
Consider these limits as you plan, deploy, and operate your Microsoft Azure Stack Hub instances. The following table describes these limits.
Infrastructure Backup limits
|Backup type||Full only||Infrastructure Backup Controller only supports full backups. Incremental backups aren't supported.|
|Scheduled backups||Scheduled and manual||Backup controller supports scheduled and on-demand backups.|
|Maximum concurrent backup jobs||1||Only one active backup job is supported per instance of Backup Controller.|
|Network switch configuration||Not in scope||Admin must back up network switch configuration using OEM tools. Refer to documentation for Azure Stack Hub provided by each OEM vendor.|
|Hardware Lifecycle Host||Not in scope||Admin must back up Hardware Lifecycle Host using OEM tools. Refer to documentation for Azure Stack Hub provided by each OEM vendor.|
|Maximum number of file shares||1||Only one file share can be used to store backup data.|
|Backup App Services, Function, SQL, mysql resource provider data||Not in scope||Refer to guidance published for deploying and managing value-add RPs created by Microsoft.|
|Backup third-party resource providers||Not in scope||Refer to guidance published for deploying and managing value-add RPs created by third-party vendors.|
- To learn more about the Infrastructure Backup Service, see Backup and data recovery for Azure Stack Hub with the Infrastructure Backup Service.