Merge pull request #36771 from ramakoni1/ramakoni1/patch-10

Enhance Error 3063 solution with max backup size details

Author: prmerger-automator[bot]

docs/relational-databases/backup-restore/sql-server-backup-to-url-best-practices-and-troubleshooting.md

@@ -222,7 +222,7 @@ To resolve this issue, create a configuration file that allows the Backup to URL
 
 | Issue | Solution |
 | --- | --- |
-| **Error 3063:** Write to backup block blob device `https://storageaccount/container/name.bak` failed. Device has reached its limit of allowed blocks. | To fix this issue, [stripe your backup](/archive/blogs/sqlcat/backing-up-a-vldb-to-azure-blob-storage) target with multiple files and make sure to use the following parameters in the backup command: `COMPRESSION, MAXTRANSFERSIZE = 4194304, BLOCKSIZE = 65536`. |
+| **Error 3063:** Write to backup block blob device `https://storageaccount/container/name.bak` failed. Device has reached its limit of allowed blocks. | To fix this issue, [stripe your backup](/archive/blogs/sqlcat/backing-up-a-vldb-to-azure-blob-storage) target with multiple files and make sure to use the following parameters in the backup command: `COMPRESSION, MAXTRANSFERSIZE = 4194304, BLOCKSIZE = 65536`. This error can also occur if the backup reaches the maximum supported size. For example, in SQL Server 2022 and earlier, the maximum backup size is 12.8 TB, calculated as 64 stripes × 50,000 blocks × a 4‑MB MAXTRANSFERSIZE. |
 | **Error 3035:** Differential backup fails for one or multiple databases. | This happens if you configured [Azure Backup service](/azure/backup/backup-overview) to back up SQL databases or a virtual machine (VM) snapshot, which doesn't create a copy-only backup, causing your maintenance plan or SQL agent job on-demand backups to fail. To fix this, [add these registry keys](/azure/backup/backup-azure-vms-troubleshoot#troubleshoot-vm-snapshot-issues) to the VMs hosting SQL Server instances at the registry key `[HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\BCDRAGENT]` and add `"USEVSSCOPYBACKUP"="TRUE"`. |
 | **Error 3201:** Backup fails with - Operating system error 50 (The request isn't supported). | Regenerate the shared access signature (SAS) token using Storage Explorer: You can [create a new policy](/azure/storage/blobs/storage-quickstart-blobs-storage-explorer#manage-access-policies) using Azure Storage Explorer and create a new SAS token with that policy from Azure Storage Explorer. [Re-create the credential](sql-server-backup-to-url.md#credential) using this new SAS token generated from Azure Storage and try backing up again. For more information, see [known issues with BACKUP TO URL](#troubleshooting-backup-to-or-restore-from-url). Make sure your network security group (NSG) and/or firewall allows inbound and outbound connection on ports 1433 and 443. |
 | **Error 3271:** Backup fails due to TLS error - Backup to URL received an exception from the remote endpoint. | This can happen on SQL Server versions 2012, 2014, and 2016. Backing up to a Microsoft Azure Blob Storage service URL isn't compatible with TLS 1.2 and can be fixed by following the instructions in [KB4017023](https://support.microsoft.com/topic/kb4017023-sql-server-2012-2014-or-2016-backup-to-microsoft-azure-blob-storage-service-url-isn-t-compatible-for-tls-1-2-e9ef6124-fc05-8128-86bc-f4f4f5ff2b78). |