Merge pull request #245439 from AbhishekMallick-MS/Jul-19-2023-VMts

VM TS updates

Author: prmerger-automator[bot]

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

@@ -3,10 +3,10 @@ title: Troubleshoot backup errors with Azure VMs
 description: In this article, learn how to troubleshoot errors encountered with backup and restore of Azure virtual machines.
 ms.reviewer: srinathv
 ms.topic: troubleshooting
-ms.date: 12/23/2022
+ms.date: 07/20/2023
 ms.service: backup
-author: jyothisuri
-ms.author: jsuri
+author: AbhishekMallick-MS
+ms.author: v-abhmallick
 ---
 
 # Troubleshooting backup failures on Azure virtual machines
@@ -133,7 +133,12 @@ Error message: Snapshot operation failed because VSS writers were in a bad state
 
 This error occurs because the VSS writers were in a bad state. Azure Backup extensions interact with VSS Writers to take snapshots of the disks. To resolve this issue, follow these steps:
 
-Step 1: Restart VSS writers that are in a bad state.
+**Step 1**: Check the **Free Disk Space**, **VM resources as RAM and page file**, and **CPU utilization percentage**.
+
+- Increase the VM size to increase vCPUs and RAM space.
+- Increase the disk size if the free disk space is low.
+
+**Step 2**: Restart VSS writers that are in a bad state.
 
 * From an elevated command prompt, run `vssadmin list writers`.
 * The output contains all VSS writers and their state. For every VSS writer with a state that's not **[1] Stable**, restart the respective VSS writer's service.
@@ -145,13 +150,13 @@ Step 1: Restart VSS writers that are in a bad state.
 > [!NOTE]
 > Restarting some services can have an impact on your production environment. Ensure the approval process is followed and the service is restarted at the scheduled downtime.
 
-Step 2: If restarting the VSS writers did not resolve the issue, then run the following command from an elevated command-prompt (as an administrator) to prevent the threads from being created for blob-snapshots.
+**Step 3**: If restarting the VSS writers did not resolve the issue, then run the following command from an elevated command-prompt (as an administrator) to prevent the threads from being created for blob-snapshots.
 
 ```console
 REG ADD "HKLM\SOFTWARE\Microsoft\BcdrAgentPersistentKeys" /v SnapshotWithoutThreads /t REG_SZ /d True /f
 ```
 
-Step 3: If steps 1 and 2 did not resolve the issue, then the failure could be due to VSS writers timing out due to limited IOPS.<br>
+**Step 4**: If steps 1 and 2 did not resolve the issue, then the failure could be due to VSS writers timing out due to limited IOPS.<br>
 
 To verify, navigate to ***System and Event Viewer Application logs*** and check for the following error message:<br>
 *The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.*<br>