1-800-691-1991 | 9am - 8pm ET
EN

SQL Server Fails with error VSSControl: -2147024809 Backup job failed. Discovery phase failed.

KB ID: 1879
Product: Veeam Backup & Replication
Version: 6.x, 7.x
Published: 2014-04-21
Last Modified: 2020-08-13
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

This KB provides information when SQL fails with this error due to a logical file path. 

Cause

The volume mount point for the database does not exist on the server on which the file is mounted.
 
Job logs will present the following similar error:
 
Error    VSSControl: -2147024809 Backup job failed.
Error    Discovery phase failed.
Error    Cannot enumerate volumes that should be added to the snapshot set.
Error    Cannot enumerate volumes that contain components specified by the processed writer. Writer name: [SqlServerWriter], class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. instance ID: [{88a622b8-5d1c-4b23-bd59-934c18a7b68c}].
Error    Cannot obtain a volume mount point for the volume that contains the specified file. File path: [\\ServerName\folder path\SQLDB.mdf].
 
The VeeamVSSSupport log will show the below information. This can be found in the following location on the SQL guest:

  • Windows 7/8 Generations: C:\ProgramData\Veeam\Backup
  • Windows XP/2k3: %allusersprofile%\Application Data\Veeam\Backup
 
Enumerating volumes that should be added to the snapshot set.. Failed.
Performing discovery phase.. Failed.
Performing backup steps.. Failed.
ERR     Freeze job failed.
ERR         Backup job failed.
ERR         Discovery phase failed.
ERR         Cannot enumerate volumes that should be added to the snapshot set.
ERR         Cannot enumerate volumes that contain components specified by the processed writer. Writer name: [SqlServerWriter], class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. instance ID: [{88a622b8-5d1c-4b23-bd59-934c18a7b68c}].
ERR         Cannot obtain a volume mount point for the volume that contains the specified file. File path: [\\ServerName\folder path\SQLDB.mdf].
ERR         Cannot get an unique volume name that corresponds to the specified volume mount point: [\\ServerName\folder path \].
ERR         Win32 error:The parameter is incorrect.
ERR          Code: 87

Solution

The database is mounted utilizing a UNC path. These paths are not supported for VSS backup as there are no corresponding volume mount points for the path. Move the database to a local drive on the server. 

More information

This issue is typically caused by mounting databases through network paths or mapped network drives using SQL native utilities.

Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.