Skip to content

Commit a7d38fe

Browse files
author
vrvkrajesh
committed
Updated hyperlink in UserErrorVMInternetConnectivityIssue section
1 parent 3c5c7d9 commit a7d38fe

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/backup/backup-sql-server-azure-troubleshoot.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -143,18 +143,18 @@ Operation is blocked as the vault has reached its maximum limit for such operati
143143

144144
| Error message | Possible causes | Recommended action |
145145
|---|---|---|
146-
The VM is not able to contact Azure Backup service due to internet connectivity issues. | The VM needs outbound connectivity to Azure Backup Service, Azure Storage or Azure Active Directory services.| - If you use NSG to restrict connectivity, then you should use the AzureBackup service tag to allows outbound access to Azure Backup to Azure Backup Service, Azure Storage or Azure Active Directory services. Follow these [steps](https://aka.ms/nsgrulesforsqlbackup) to grant access.<br>- Ensure DNS is resolving Azure endpoints.<br>- Check if the VM is behind a load balancer blocking internet access. By assigning public IP to the VMs, discovery will work.<br>- Verify there is no firewall/antivirus/proxy that is blocking calls to the above three target services.
146+
The VM is not able to contact Azure Backup service due to internet connectivity issues. | The VM needs outbound connectivity to Azure Backup Service, Azure Storage or Azure Active Directory services.| - If you use NSG to restrict connectivity, then you should use the AzureBackup service tag to allows outbound access to Azure Backup to Azure Backup Service, Azure Storage or Azure Active Directory services. Follow these [steps](https://docs.microsoft.com/azure/backup/backup-sql-server-database-azure-vms#allow-access-using-nsg-tags) to grant access.<br>- Ensure DNS is resolving Azure endpoints.<br>- Check if the VM is behind a load balancer blocking internet access. By assigning public IP to the VMs, discovery will work.<br>- Verify there is no firewall/antivirus/proxy that is blocking calls to the above three target services.
147147

148148

149149
## Re-registration failures
150150

151151
Check for one or more of the following symptoms before you trigger the re-register operation:
152152

153153
* All operations (such as backup, restore, and configure backup) are failing on the VM with one of the following error codes: **WorkloadExtensionNotReachable**, **UserErrorWorkloadExtensionNotInstalled**, **WorkloadExtensionNotPresent**, **WorkloadExtensionDidntDequeueMsg**.
154-
* The **Backup Status** area for the backup item is showing **Not reachable**. Rule out all the other causes that might result in the same status:
154+
* If the **Backup Status** area for the backup item is showing **Not reachable**, rule out all the other causes that might result in the same status:
155155

156156
* Lack of permission to perform backup-related operations on the VM.
157-
* Shutdown of the VM, so backups can’t take place.
157+
* Shutdown of the VM, so backups cannot take place.
158158
* Network issues.
159159

160160
![re-registering VM](./media/backup-azure-sql-database/re-register-vm.png)

0 commit comments

Comments
 (0)