Troubleshooting Backup Failure: Unstable Writers or Excluded Volumes Issue

Troubleshooting Backup Failure: Unstable Writers or Excluded Volumes Issue

KB ID: 501007
Issue:
Backup failed with the error message: "Unable to perform application-aware processing as the writers are not stable in the instance (or) all the volumes in the instance are excluded."
Cause:
This issue can occur due to the following reasons:
1. The writers responsible for performing application-aware processes are in an unstable condition.
2. During backup job configuration, all volumes in the app-aware confirmation are excluded.
3. Another application or service may be using the VSS Service Provider.
Solution:
To address the problem, consider the following suggestions:
Problem 1: Unstable Writers
1. Connect to the Backup-configured VM and check the log file at `C:\Program Files\Vembu\BackupForAWS\Server\BackupRestore\logs\<backup_name>\backup.log`.
2. If the error is "(The command status - True and command output - {"status": false, "error_msg": "writers are not stable"})," list the writers with the command `vssadmin list writers` in PowerShell or Command Prompt.
3. Identify any writers in an unstable state. Restart the Volume Shadow Copy Service in `services.msc` and check the stability of the writers. Proceed with the backup if stable.
Problem 2: Excluded Volumes
1. If all volumes were excluded in app-aware configuration, edit the job, remove the excluded volumes, and save the backup job.
2. Run the backup again.
Problem 3: VSS Operation Blockage
1. Check the log file at `C:\Program Files\Vembu\BackupForAWS\Server\BackupRestore\logs\<backup_name>\backup.log` for the error message "(The command status - True and command output - {"status": false, "error_msg": "StartSnapshotSet() is failed. hr=-2147212522"})."
2. If the error code is `-2147212522` or `-2147212529`, it indicates that the VM/Instance has a service performing VSS operations, blocking the shadow copy. Retrieve the provider ID from the Event Viewer log.
3. Use the command `vssadmin list providers` to get the providers running on the VM. Match the provider ID in the Event Viewer log with the listed providers.
4. Delete the identified provider in the registry editor (`Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\`).
5. Restart the machine and schedule the backup.
By following these steps, you can troubleshoot and resolve the backup failure with error code 501007. If further assistance is needed, please contact our support team.

    • Related Articles

    • Backup Failure due to Unstable Guest VM Writers (Microsoft Error Code: 0x80042301)

      KB ID: 104061 Description: This Knowledge Base article addresses the alert that occurs when backup operations fail due to guest VM writers being in an unstable state. The alert is associated with Microsoft error code 0x80042301. It provides solutions ...

    • Application Aware Process Error: Unstable Writers for Configured VM

      KB ID: 105061 Cause: The "Application Aware Process - One or more writers are Unstable for the Configured VM" error occurs due to instability in the Application VSS writer(s) (Exchange, MSSQL) within the Guest VM machine. Solution: To resolve the ...

    • MSSQL Backup Failure: SQL Writer Failed

      KB ID: 113 Problem: When attempting to perform an MSSQL backup, users may encounter a failure with the error message "SQL Writer Failed." Cause: The "SQL Writer Failed" error can occur to various reasons, including: 1. VSS (Volume Shadow Copy ...

    • SNAPSHOT_FAILURE - Hyper-V VSS Writer in Unstable State, Backup Rescheduling Required

      KB ID: 104064 Cause: Encountering a snapshot failure with error code 0x80042301, indicating that the Hyper-V VSS Writer is not in a stable state during the backup process. Solution: To resolve this issue, follow these steps: 1. Check the writers ...

    • Troubleshooting Snapshot Failure in BDRSuite

      KB ID: 104066 Cause: Users may encounter a "SNAPSHOT_FAILURE" error during snapshot initialization when attempting to back up virtual machines using BDRSuite. This issue arises for the following reasons: 1. The clustered volume (CSV) is not available ...