Skip to content

Commit 1ff3574

Browse files
authored
Merge pull request #97053 from dcurwin/dcurwin-nov25
Update SQL Server Failover Cluster Instance info
2 parents 8cd6a98 + 8112a21 commit 1ff3574

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/backup/backup-azure-sql-database.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,15 +45,15 @@ Before you start, verify the below:
4545
* SQL Server backup can be configured in the Azure portal or **PowerShell**. We do not support CLI.
4646
* The solution is supported on both kinds of [deployments](https://docs.microsoft.com/azure/azure-resource-manager/resource-manager-deployment-model) - Azure Resource Manager VMs and classic VMs.
4747
* VM running SQL Server requires internet connectivity to access Azure public IP addresses.
48-
* SQL Server **Failover Cluster Instance (FCI)** and SQL Server Always on Failover Cluster Instance are not supported.
48+
* SQL Server **Failover Cluster Instance (FCI)** is not supported.
4949
* Back up and restore operations for mirror databases and database snapshots aren't supported.
5050
* Using more than one backup solutions to back up your standalone SQL Server instance or SQL Always on availability group may lead to backup failure; refrain from doing so.
5151
* Backing up two nodes of an availability group individually with same or different solutions, may also lead to backup failure.
5252
* Azure Backup supports only Full and Copy-only Full backup types for **Read-only** databases
5353
* Databases with large number of files can't be protected. The maximum number of files that is supported is **~1000**.
5454
* You can back up to **~2000** SQL Server databases in a vault. You can create multiple vaults in case you have a greater number of databases.
5555
* You can configure backup for up to **50** databases in one go; this restriction helps optimize backup loads.
56-
* We support databases up to **2 TB** in size; for sizes greater than that, performance issues may come up.
56+
* We support databases up to **2 TB** in size; for sizes greater than that performance issues may come up.
5757
* To have a sense of as to how many databases can be protected per server, we need to consider factors such as bandwidth, VM size, backup frequency, database size, etc. [Download](https://download.microsoft.com/download/A/B/5/AB5D86F0-DCB7-4DC3-9872-6155C96DE500/SQL%20Server%20in%20Azure%20VM%20Backup%20Scale%20Calculator.xlsx) the resource planner that gives the approximate number of databases you can have per server based on the VM resources and the backup policy.
5858
* In case of availability groups, backups are taken from the different nodes based on a few factors. The backup behavior for an availability group is summarized below.
5959

0 commit comments

Comments
 (0)