1455 - Error: Could not add volume ... to VSS snapshot

Modified on Mon, 21 Jul at 12:57 PM

Symptom

When a backup is initiated while a second VSS writer is already running, you may encounter the following error:

Backup failed to complete: Could not add volume '\\?\Volume{xxxxxxx-xxx-xxx-xxx-xxxxxxxxx}\' 
to VSS snapshot (0x8004230f; unexpected provider error)

 

Solution

1. Run the command vssadmin list writers. Depending on the Windows roles and products installed, the number of writers that is displayed will vary. In a healthy system, all reports should read as [1] Stable with No error.

2. If any of the writers reports anything other than [1] Stable, you need to restart the VSS service. The list below shows which service you need to restart based on which VSS writer has failed.

VSS WriterProcess (.exe)Service
ASR WriterVSSVolume Shadow Copy
BITS WriterBITSBackground Intelligent Transfer Service
COM+ REGDB WriterVSSVolume Shadow Copy
DFS Replication Service WriterDFSRDFS Replication
DHCP Jet WriterDHCPServerDHCP Server
FRS WriterNtFrsFile Replication
FRSM WritersrmsvcFile Server Resource Manager
IIS Config WriterAppHostSvcApplication Host Helper Service
IIS Metabase WriterIISADMINIIS Admin Service
Microsoft Exchange Replica WriterMSExchangeReplMicrosoft Exchange Replication Service
Microsoft Exchange WriterMSExchangeISMicrosoft Exchange Information Store
Microsoft Hyper-V VSS WritervmmsHyper-V Virtual Machine Management
MSMQ WriterMSMQMessage Queuing
MSSearch Service WriterWSearchWindows Search
NTDSNTDSActive Directory Domain Services
O_Search VSS WriterOSearchOffice SharePoint Server Search
O_Search 14 VSS WriterOSearch14SharePoint Server Search 14
Registry WriterVSSVolume Shadow Copy
Shadow Copy Optimization WriterVSSVolume Shadow Copy
SMS WriterSMSSITEVSSWRITERSMS_SITE_VSS_WRITER
SPSearch VSS WriterSPSearchWindows SharePoint Services Search
SPSearch4 VSS WriterSPSearch4SharePoint Foundation Search V4
SqlServerWriterSQLWriterSQL Server VSS Writer
System WriterCryptSvcCryptographic Services
TermServLicensingTermServLicensingRemote Desktop Licensing
WIDWriterWIDWriterWindows Internal Database VSS Writer
WINS Jet WriterWINSWindows Internet Name Service (WINS)
WMI WriterWinmgmtWindows Management Instrumentation


3. After restarting the service, run the vssadmin command again to check whether the relevant writer is still in a failed state. If there is no improvement, a full reboot of the server is required.

4. In your ESE agent, go to Options > Advanced. Under VSS, set the VSS provider to Microsoft Software Shadow Copy provider 1.0.

5. If the issue persists, check the event logs against Microsoft's lists of VSS events. Also check the VSS service for errors.

6. If you need further assistance, please log a support ticket containing:

  • the Windows Application and System Event Logs in .evtx format
  • the device name
  • the output file of the following commands:

    • vssadmin list writers >C:\writers.txt
    • vssadmin list providers >C:\providers.txt
    • vssadmin list shadows >C:\shadows.txt
    • vssadmin list shadowstorage >C:\shadowstorage.txt

  • the number of disks that you have, plus the free disk space on each

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article