Merge pull request #239771 from sooryar12/patch-4

Update backup-azure-mars-troubleshoot.md

Author: prmerger-automator[bot]

articles/backup/backup-azure-mars-troubleshoot.md

@@ -247,6 +247,10 @@ Backup operations could fail if there isn't sufficient shadow copy storage space
 
 [!INCLUDE [antivirus-scan-exclusion-rules](../../includes/backup-azure-antivirus-scan-exclusion-rules.md)]
 
+### Backup or restore job is displayed as *in progress* in Azure for many days but is not visible in the console
+
+If a MARS Agent backup or restore job crashes during execution, it is marked as failed in the MARS console, but the status might not get propagated to Azure. Hence, the job might be displayed as "in progress" in the Azure Portal even when it is not running. This stale job entry will be removed from the Azure Portal automatically after 30 days.
+
 ## Common issues
 
 This section covers the common errors that you encounter while using MARS agent.
@@ -286,4 +290,4 @@ If you've ongoing Import/Export jobs created from older MARS agents, you can sti
 ## Next steps
 
 - Get more details on [how to back up Windows Server with the Azure Backup agent](tutorial-backup-windows-server-to-azure.md).
-- If you need to restore a backup, see [restore files to a Windows machine](backup-azure-restore-windows-server.md).
+- If you need to restore a backup, see [restore files to a Windows machine](backup-azure-restore-windows-server.md).