Problem description
SQL Database Backup fails to create a snapshot. The following entries are logged in the Phoenix Agent logs:
[ERROR] Backup failed for shareFileName_old.mds with error:Vss Error: GetSnapshotProperties hr = 0x80010108L
[ERROR] Backup failed for share:FileName_old.ndf with error:Vss Error: GetSnapshotProperties hr = 0x800706baL
[ERROR] Error while backing up share FileName. Error: Vss Error: GetSnapshotProperties hr = 0x800706baL
ERROR] SqlAgent :SQL backup failed: Vss Error: GetSnapshotProperties hr = 0x800706baL
[ERROR] Error <class 'pyvss.VssException'>:Vss Error: GetSnapshotProperties hr = 0x800706baL. Traceback -Traceback (most recent call last):
You will also notice some events related to this conflict.
Log Name Application
Source: VSS
Date: 2/24/2017 10:23:45 PM
Event ID: 12291
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <ServerName>
Description:
Volume Shadow Copy Service error: Error on creating/using the COM+ Writers publisher interface: BackupShutdown [0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
Log Name Application
Source: BeVssProvider
Date: 2/24/2017 10:23:48 PM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: <ServerName>
Description:
Service started/resumed
Log Name Application
Source: VSS
Date: 2/24/2017 10:23:49 PM
Event ID: 8193
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <ServerName>
Description:
Volume Shadow Copy Service error: Unexpected error calling routine IVssAsync::QueryStatus. hr = 0x800706ba, The RPC server is unavailable.
You may also see
Log Name System
Source: volsnap
Date: 10/18/2018 3:06:34 PM
Event ID: 35Task Category: None
Level: Error
Description: The shadow copies of volume X: were aborted because the shadow copy storage failed to grow.
Cause
When the Phoenix agent tries to take a snapshot with the help of Windows Volume Shadow Copy, it fails with the VSS error. This occurs when there is an additional third-party VSS provider installed on the server that creates a conflict when VSS takes a snapshot of the database.
Resolution
There are a couple of approaches to resolve this issue, depending on the root cause:
1. Uninstall the Third-Party VSS Provider:
If the issue is caused by a conflicting third-party VSS provider, Druva recommends uninstalling the provider completely from the server. Here’s how to proceed:
Uninstall the third-party VSS provider from the server using the standard uninstallation procedure via the Windows Control Panel or any other method provided by the vendor.
Restart the server during a period of low server utilization to ensure that no critical processes are interrupted.
This should allow the native VSS service to regain appropriate access to the SQL writer and create a clean snapshot for backups.
2. Resolve Issues with VSS Shadow Copy Storage:
In some cases, the issue may be related to insufficient space for VSS shadow copies or misconfigurations in shadow copy settings. Follow these steps to troubleshoot:
Enable Shadow Copy:
Run the following command to enable shadow copies:
vssadmin create shadow /for=G:\Increase the Shadow Copy Storage Size:
If the shadow copy storage is too small or the server is running out of space, increase the shadow copy storage size with this command:
vssadmin resize shadowstorage /for=G: /On=G: /MaxSize=UNBOUNDEDThis command sets the maximum size of the shadow copy storage to "unbounded," ensuring that VSS has sufficient space to create the shadow copy without limitations.
3. Additional Steps to Verify VSS Configuration:
Run the VSSADMIN command to list the installed VSS providers:
vssadmin list providersReview the list to identify if any third-party providers are installed and conflicting with the VSS operations.
Check for VSS Service Issues:
If the Volume Shadow Copy service itself is not functioning correctly, ensure it is running by using the following command:
net start vssYou can also restart the service using:
net stop vss && net start vss
4. Verify Event Logs for Further Clues:
Keep an eye on the Event Viewer logs for VSS-related errors. Specific Event IDs, such as 12291 and 8193, can indicate underlying issues with VSS operations. Check these logs to gain more insights into the exact cause of the failure and troubleshoot accordingly.