Keep the MABS SQL instance local when planning an Azure Stack Hub installation

Source facts

Microsoft’s Azure Stack Hub installation guidance requires the SQL Server instance used by Azure Backup Server to be local; a remote instance is not supported. The backup server is intended for a dedicated, single-purpose virtual machine. The same guidance excludes installation on a domain controller, an Exchange server, an Application Server-role machine or a cluster node. Microsoft Learn.

Applicability

Apply this placement review to Microsoft Azure Backup Server on Azure Stack Hub. Validate the chosen operating system, MABS release and SQL combination against the current requirements; the installation page’s older sizing examples are not a general capacity recommendation.

DSE recommendation

Reject a shared remote-database design before starting installation. Document the backup server’s purpose, its local database dependency and the proposed cohosted roles. Have the infrastructure owner approve an eligible dedicated machine and the database-maintenance responsibility. Keep the placement decision separate from the organization’s ordinary SQL consolidation policy. Do not move an existing installation or remove another workload merely to make the proposed diagram fit; plan any migration as a separately supported change.

Verification

Review the proposed machine’s installed roles and the actual location of the selected SQL instance. During an approved installation rehearsal, retain prerequisite-check results and confirm that the backup service uses the intended local database. Resolve a placement mismatch before scheduling protected workloads. Record capacity assumptions for later measurement instead of copying the source’s historical virtual-machine examples into an operational guarantee.

Official references

Microsoft Learn: Install Azure Backup Server on Azure Stack Hub.